Executive Overview: A New Era for Single-Page Applications
In a landmark development for web developers and SEO professionals, Google’s Chrome team has officially introduced experimental versions of all three Core Web Vitals (CWV) within the Chrome User Experience Report (CrUX). This update addresses a long-standing technical oversight: the inability of traditional performance metrics to accurately account for "soft navigations"—the dynamic, in-app page transitions common in modern Single-Page Applications (SPAs).
For years, the performance of SPAs was unfairly penalized. Because these applications update content and URLs without triggering a full browser reload, performance data was often aggregated, conflating the initial load with subsequent user interactions. This led to skewed, often pessimistic performance scores. By introducing dedicated metrics that track these transitions as distinct events, Google is finally aligning its performance benchmarks with the reality of modern JavaScript-driven web architecture.
As of the October 13 release, these experimental metrics are available across BigQuery, the CrUX API, and the History API. Furthermore, CrUX Vis—the visualization tool for these datasets—now features a toggle allowing developers to compare "stable" metrics against the new "experimental" soft-navigation-enabled figures. While Google stresses that these metrics remain in an experimental phase until at least May 2027, the implications for the future of web performance optimization are profound.
Detailed Chronology: From API Trial to Data Integration
The journey toward this integration began in earnest with the release of Chrome Version 151 on July 28, which enabled the Soft Navigations API by default. This API provides the underlying logic required for the browser to recognize when a user’s interaction results in both a visible URL change and a significant paint event—the two pillars that define a "soft navigation."
Following the successful origin trial conducted in August 2025, Google began the process of piping this data into the broader CrUX ecosystem. The transition can be viewed as a three-phase rollout:
- The API Foundation: Establishing the browser-level tracking of soft navigations to ensure consistent detection across diverse frameworks (React, Vue, Angular, etc.).
- Dataset Enrichment: The October release, which introduced three specific experimental fields:
experimental_largest_contentful_paint_with_softnavs,experimental_interaction_to_next_paint, andexperimental_cumulative_layout_shift. - Visual and Analytical Tools: The integration of these fields into BigQuery and CrUX Vis, empowering developers to perform granular audits of their site’s performance.
This phased approach demonstrates Google’s cautious, data-driven methodology. By keeping the metrics in an experimental state for several years, the team intends to gather feedback from the developer community, iterate on the measurement logic, and ensure that the eventual transition to Search Console—the final authority for SEO impact—is seamless and well-understood.
Supporting Context & Metrics: Why SPAs Were Being Misrepresented
To understand the significance of this update, one must consider how CrUX operated previously. Before this release, a user navigating through an SPA would have their first "hard" load recorded, but all subsequent actions—even if they felt like entirely new page views to the user—were grouped into that initial session. Consequently, layout shifts and interaction delays from the entire user journey were often unfairly attributed to the landing URL.
The Impact on Performance Scores
The data provided by Chrome reveals that for a vast majority of the web—roughly 70% of origins—there is little to no impact, as these sites rely on traditional, multi-page architectures. However, for SPA-heavy sites, the change is transformative.
- Largest Contentful Paint (LCP): Sites with 75% to 100% soft navigations saw their "good" LCP pass rates jump from 26% on the stable metric to 87% on the experimental one. This underscores that SPAs were not inherently "slow"; rather, they were being measured by a standard that didn’t account for their rapid, incremental content updates.
- Interaction to Next Paint (INP): By measuring responsiveness per page view rather than across an entire session, INP metrics have roughly doubled for many SPA-dependent sites. This gives developers a much clearer picture of which specific interactions are causing friction.
- Cumulative Layout Shift (CLS): Previously, layout shifts were cumulative across a session. By grouping them by view, SPA-heavy desktop sites are finally performing on par with traditional multi-page applications.
These figures illustrate that the "performance gap" between SPAs and traditional sites was, in many ways, an artifact of the measurement methodology. By moving toward a "per-view" model, Google is effectively leveling the playing field.
Official Statements and Technical Nuance
Annie Sullivan, a key voice in the Chrome performance team, has been instrumental in framing these changes. Her analysis provides critical context for developers who might be confused by the sudden shift in their scores.
"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," Sullivan noted. She also clarified the philosophical shift: "This isn’t because SPAs are faster than multi-page websites overall, but because follow-up clicks are faster on any site, bringing SPAs with many follow-up visits in line with MPAs with many follow-up visits."
This statement is a critical admission that the goal of these metrics is not to favor one architecture over another, but to provide a consistent, accurate representation of the user experience. By measuring the "follow-up clicks" correctly, Google is validating the user’s perception of speed, which is ultimately what the Core Web Vitals are intended to protect.
The Path to 2027: Future Outlook and Strategic Planning
The road ahead is one of cautious refinement. Google has set a target of May 2027 for concluding the experimental status of these metrics, but this date is subject to change based on community feedback.
What to Expect in the Coming Months
- November 2024 Checkpoint: The CrUX release for November is expected to introduce soft-navigation-enabled versions of First Contentful Paint (FCP) and refined navigation types.
- Lifecycle Progression: Following the standard Web Vitals lifecycle, these metrics will move from "experimental" to "pending" for a minimum of six months before becoming "stable."
- Search Console Integration: Once the status moves to stable, these metrics will be integrated into Google Search Console. For site owners, this is the most critical milestone, as it will determine whether these scores begin to influence search rankings directly.
Strategic Recommendations for Developers
For teams currently maintaining high-traffic SPAs, the strategy should be one of observation and proactive audit:
- Enable the Toggle: Utilize the "Include soft navigations" toggle in CrUX Vis immediately. Identify which of your pages see the most significant shift in scores.
- Analyze the Delta: If your metrics improve significantly, document the difference. If they worsen, investigate whether the Soft Navigations API is correctly identifying your page transitions, or if your site has underlying performance issues that were previously "masked" by the aggregation of data.
- Engage the Community: Google is actively soliciting feedback through the
web-vitalsfeedback group and the GitHub repository for the soft navigations specification. Reporting bugs or edge cases now can help shape the final standard.
Conclusion: A More Accurate Web
The introduction of soft navigation metrics into CrUX is a victory for technical accuracy. By acknowledging the specific way modern JavaScript frameworks interact with the browser, Google is providing the industry with the tools necessary to build faster, more responsive applications. While the transition will take time, and the metrics will undoubtedly fluctuate as they are refined, the ultimate result will be a more representative understanding of what constitutes a "good" user experience on the modern web.
As the web continues to evolve toward more dynamic, app-like experiences, the metrics we use to judge that web must evolve in lockstep. With this latest release, Chrome has taken a necessary and decisive step toward that future.
