Measuring Single-Page Application Performance in CrUX
For years, developers and site owners managing single-page applications have faced an invisible disadvantage in Google performance reports. Traditional measurement tools evaluated only the initial hard load of a page, grouping every subsequent in-app transition and background update together with the initial landing URL. This meant that layout shifts, responsiveness bottlenecks, and slow paint events triggered deep into a user session were unfairly penalized or entirely misattributed. That diagnostic blind spot is finally starting to clear.
Chrome has officially introduced experimental versions of all three Core Web Vitals into the Chrome User Experience Report (CrUX), specifically designed to capture in-app page changes that occur without a full browser reload. Available through BigQuery, the CrUX API, and the History API, these additions provide a dedicated lens for analyzing framework-driven architectures. Furthermore, the public CrUX Vis tool now features a direct toggle allowing developers to visualize these experimental updates side by side with stable metrics.
What the Experimental Fields Track
The latest update injects three new experimental fields into the database: experimental largest contentful paint with softnavs, alongside equivalents for Interaction to Next Paint and Cumulative Layout Shift. These fields monitor the exact same performance thresholds as their stable counterparts, but with one critical distinction: they capture both traditional hard loads and verified soft navigation events.
This data relies on the underlying Soft Navigations API, which has been active by default since Chrome Version 151. Under this framework, a soft navigation is recognized whenever a user interaction triggers a synchronized visual change to both the viewport content and the browser URL. By segregating these events, web performance analysts can isolate how dynamic routing behaves without letting a clean landing page mask subsequent friction points deeper in the user journey.
How Traffic Profiles Dictate Metric Shifts
Not every web property will experience a radical transformation in its reporting dashboard. Industry data shows that roughly seventy percent of origins in the CrUX dataset exhibit little to no soft navigation traffic. Traditional multi-page websites that execute full reloads on every hyperlink click will see virtually zero impact when toggling the new metrics on.
Conversely, domains built heavily on modern JavaScript frameworks stand to see substantial adjustments. Among the top one thousand domains tracked by Google, a significant percentage rely on soft navigations for more than half of their total page views. For these properties, the experimental scores typically skew higher. For instance, Android origins with heavy soft navigation usage see their good Largest Contentful Paint pass rates climb dramatically once follow-up clicks are measured independently rather than lumped into an overburdened session.
Refining Interaction and Layout Scores
Interaction to Next Paint benefits considerably from this architectural separation. Rather than calculating responsiveness based on the single slowest interaction across an entire extended user session, INP is evaluated on a per-page-view basis. This adjustment effectively halves the penalty for transient layout delays during routing transitions. Similarly, Cumulative Layout Shift scoring groups shift events by specific view rather than session, bringing JavaScript-heavy desktop implementations much closer in parity to traditional multi-page setups.
Timeline and Roadmap Toward Stability
While these experimental metrics are live in BigQuery and the API today, webmasters should exercise patience before adjusting enterprise optimization roadmaps. Google has scheduled the experimental phase to run through May 2027, subject to community feedback collected via GitHub and the web-vitals feedback groups. Search Console will not adopt the experimental metrics until they graduate to stable status, meaning current search visibility reports remain unaffected.
As Chrome continues rolling out additional telemetry—such as upcoming First Contentful Paint additions in subsequent monthly updates—technical teams should utilize CrUX Vis to audit how their dynamic routing impacts user experience today. Preparing for these metrics early ensures that framework-heavy web properties maintain a competitive edge when these scores eventually transition into official ranking and reporting signals.