In a landmark update for developers of Single-Page Applications (SPAs), Google has officially introduced experimental versions of all three Core Web Vitals within the Chrome User Experience Report (CrUX). This development marks a significant shift in how the web’s primary performance metrics are calculated, finally accounting for the nuanced, dynamic nature of modern JavaScript-heavy websites.

As of the October 13 release, developers can now access data for experimental_largest_contentful_paint_with_softnavs, as well as corresponding experimental versions for Interaction to Next Paint (INP) and Cumulative Layout Shift (CLS). Available via BigQuery, the CrUX API, and the History API, these metrics represent the most comprehensive attempt yet to bridge the gap between traditional Multi-Page Application (MPA) performance measurement and the fluid, reload-free experience provided by modern frameworks like React, Vue, and Angular.

The Chronology of a Performance Shift

The journey toward this release began with the evolution of how browsers handle user navigation. Historically, CrUX measured the performance of the initial page load—the "hard load." However, as SPAs grew in popularity, the "page view" became a fluid concept. An SPA could change its content and its URL multiple times without the browser ever performing a full refresh.

Prior to this update, CrUX lumped all subsequent in-app interactions and layout shifts back onto the landing URL. This created an inaccurate representation of performance, often penalizing sites for "late-game" interactions that weren’t part of the initial load, while simultaneously masking performance bottlenecks occurring during deep-link navigations.

The groundwork for the current release was laid by the Soft Navigations API, which has been enabled by default since the release of Chrome 151 on July 28. A "soft navigation" is defined as a user-initiated action that results in both a visible change to the URL and a meaningful paint on the screen. By integrating this API into CrUX, Google has enabled the granular tracking of every distinct "page" within an SPA, effectively leveling the playing field between static sites and complex web applications.

Deconstructing the Technical Implementation

The experimental metrics in the latest CrUX release track the exact same phenomena as their stable counterparts, but they expand the scope of the data collection. Whereas stable metrics focus on the entry point, the experimental fields count both hard loads and detected soft navigation events.

How the Data Works

When a user clicks a link in an SPA, the browser now treats that event as a distinct navigation. If the action triggers a content update and a URL change, the associated Core Web Vital metrics are recorded under that destination URL. This is a departure from the previous model where the "session" was the unit of measurement. By shifting the focus to the "view," developers can now pinpoint exactly which sub-pages are suffering from poor Largest Contentful Paint (LCP) or excessive layout shifts.

Integration Across Tools

Google has made this data immediately actionable for developers through several channels:

  • BigQuery: Large-scale analysis of site performance across millions of origins.
  • CrUX API: Real-time programmatic access to performance data.
  • CrUX Vis: A dedicated visual toggle now allows developers to compare stable versus experimental metrics side-by-side, providing an immediate diagnostic tool for identifying performance gaps in SPA architecture.

Supporting Data: Who Is Impacted?

One of the most frequent concerns regarding this update is whether it will cause widespread volatility in search rankings or performance reporting. According to Google’s analysis, the impact will be highly localized to specific architectural patterns.

The Distribution of Impact

Google analyzed the share of page views that qualify as "soft navigations" across the web. The findings suggest that the vast majority of the web will remain largely unaffected:

  • Low-Impact Origins: Approximately 66% to 75% of origins in CrUX (depending on the platform) have fewer than 5% of their total page views categorized as soft navigations. For these sites, the experimental metrics will likely mirror their existing stable scores.
  • High-Impact Origins: The change is most pronounced for the top 1,000 sites, where 35% on Android and 42% on desktop rely on soft navigations for more than half of their traffic.

Performance Improvement Trends

For sites that are heavy on soft navigations, the results of the experimental data are striking. Among Android origins where 75% to 100% of traffic consists of soft navigations, the share of sites meeting the "Good" threshold for LCP jumps from 26% (stable) to 87% (experimental).

This does not necessarily mean that SPAs have suddenly become faster than MPAs. Rather, it reflects the reality of the user experience: follow-up clicks are inherently faster than initial cold loads. By measuring these as distinct events, the metrics finally reflect the user’s perception of speed during a browsing session.

Official Responses and Strategic Vision

Annie Sullivan, a lead advocate for these changes at Google, emphasizes that this update is a reflection of how the web is used today, rather than a forced change in development standards. "If your site doesn’t use JavaScript to dynamically swap out page content and update the URL without a full browser reload, you shouldn’t expect to see any changes in your metrics," she stated.

The Path to Stability

Chrome has set a target date of May 2027 to move these metrics out of their experimental phase. However, this timeline is subject to community feedback and the evolution of the Soft Navigations API.

The strategy follows the established Web Vitals lifecycle:

  1. Experimental: The current phase, where metrics are available for testing and feedback.
  2. Pending: Metrics will undergo a minimum six-month period of evaluation.
  3. Stable: Once the metrics are deemed reliable, they will be incorporated into Google Search Console.

Google has been clear that it will not switch its search performance reporting until these metrics have proven their stability and accuracy over time.

Implications for Developers and SEOs

For developers and SEO professionals, this update necessitates a shift in how they interpret performance data.

A More Accurate Performance Profile

Previously, SPA developers often found themselves at a disadvantage because their "first load" metrics were burdened by the weight of the entire application bundle. By measuring each soft navigation, developers can now demonstrate the true performance of their application during the user’s journey. This is particularly beneficial for INP, which is now measured per page view rather than across an entire session, effectively doubling the pass rates for many SPA-heavy sites.

Strategic Caution

While the experimental data is highly useful for debugging, Google advises caution. Because the measurement methodology is still being refined, developers should expect some month-to-month variability. The data should be used as a diagnostic tool rather than a final benchmark for search performance at this stage.

Looking Ahead

The roadmap for these metrics is already expanding. The November CrUX release is slated to include soft-navigation versions of First Contentful Paint (FCP) and detailed navigation types. As the ecosystem matures, developers are encouraged to contribute to the discussion via the web-vitals feedback group or the soft navigations specification repository on GitHub.

Conclusion

The introduction of experimental soft navigation metrics in CrUX represents a maturation of the web performance landscape. By acknowledging that a "page load" is no longer the sole unit of interaction for modern web users, Google is providing the industry with the tools to build faster, more responsive applications.

For the average site owner, the impact may be negligible. But for the developers of complex, interactive applications, this update is a transformative step forward. It allows for a granular, accurate assessment of user experience that was previously impossible, setting the stage for a new era of web performance where the metrics finally catch up to the reality of the modern web. As we move toward the May 2027 goal of stability, the collaboration between the browser vendors and the developer community will be crucial in ensuring that these metrics provide a fair, accurate, and meaningful reflection of the web experience.