Your Single-Page Application Just Got a New Measurement Layer, and It Changes How You'll Report Core Web Vitals to the Board
Chrome announced on October 13 that experimental versions of all three Core Web Vitals are now available in the Chrome User Experience Report. These new fields track soft navigations: the in-app page changes that SPAs make without a full reload. The data is live in BigQuery, the CrUX API, and the History API. CrUX Vis already has a toggle to display them.
For marketing leaders who've spent years explaining why their React or Vue-based properties show different performance characteristics than traditional sites, this is the measurement parity we've been waiting for. It's also a forecast change you need to model before May 2027.
The Measurement Gap That Finally Closes
Until now, CrUX only measured an SPA's initial page load. Every subsequent interaction, every route change, every dynamically rendered product page got lumped back into that first URL. If a visitor landed on your homepage and then browsed through twelve product detail pages, all of those layout shifts and interaction delays were attributed to the homepage. The metrics described a session, not a page.
Chrome 151, released in August 2026, changed the underlying capability. The browser can now detect when a user action causes both a visible URL change and a visible paint, and it treats that moment as a distinct navigation event. The new CrUX fields, named things like experimental_largest_contentful_paint_with_softnavs, apply the same LCP, INP, and CLS calculations to each of those detected navigations.
The practical effect: your SPA's performance story becomes granular. Instead of one blended score for an entire session, you get per-page metrics that match how users actually experience your application.
Who Sees a Change, and Which Direction
Google's data shows that 66% to 75% of CrUX origins have fewer than 5% of their page views classified as soft navigations, depending on platform. If your site is a traditional multi-page architecture, or if your SPA usage is light, the experimental metrics will look nearly identical to your stable scores.
The sites that will see meaningful movement are the ones built heavily on client-side routing: product catalogs, dashboards, configurators, media properties with infinite scroll. For these properties, the experimental scores tend to be higher than the stable ones. That's not a gift; it's a correction. When you stop attributing every layout shift from a ten-page session to the landing URL, the landing URL's CLS improves. When you measure LCP for a route change that renders in 400ms instead of blending it with an initial load that took 2.1 seconds, the numbers look different.
Model this before you celebrate. Higher pass rates on experimental metrics don't mean your site got faster. They mean the measurement now reflects what users actually see on each page. If your stable scores are borderline, the experimental view might push you into "good" territory. If your stable scores are already strong, the change is noise.
The Timeline That Matters for Planning
Chrome's target is to conclude the experimental period in May 2027, subject to feedback. Search Console will adopt the new data once that happens. That's roughly seven months from now.
For anyone who reports Core Web Vitals to a board or uses them in executive dashboards, this creates a forecast discontinuity. Your Q2 2027 numbers will be calculated differently than your Q1 2027 numbers. If you're tracking quarter-over-quarter improvement, you need a plan to explain the methodology change, or you need to start tracking both stable and experimental metrics now so you can show the delta.
The CFO-safe move: pull experimental data from BigQuery or the CrUX API starting this month. Build a parallel view. Understand the gap between your stable and experimental scores before the switch happens, not after.
What This Doesn't Change
Stable scores remain unchanged. Your current Search Console reports, your current CrUX dashboards, your current ranking signals: all of them still use the original methodology. Nothing shifts until Chrome graduates the experimental metrics and Search Console follows.
Chrome's documentation is also clear about the heuristics. A soft navigation requires three conditions: user-initiated action, visible URL change, and visible paint. Some edge cases will produce false positives (the browser detects a navigation that users wouldn't perceive as one) or false negatives (users perceive a navigation that the browser misses). If your SPA does unusual things with history state or partial renders, test your specific flows in DevTools before trusting the aggregate data.
The Operational Checklist
First, identify your SPA exposure. Pull your current CrUX data and look at the share of page views that are soft navigations. If you're in the 70% of origins with minimal soft navigation traffic, this is a monitoring item, not an action item.
Second, if you're SPA-heavy, pull the experimental fields from BigQuery or the API. Compare them to your stable scores. Document the delta. If the experimental scores are materially better, understand why: is it because your soft navigations are genuinely fast, or because the measurement change redistributes blame away from your landing pages?
Third, update your reporting templates. Add a footnote explaining that Chrome plans to change the methodology in mid-2027. If your dashboards show quarter-over-quarter trends, flag the expected discontinuity now so it doesn't look like a performance regression or a miraculous improvement when the switch happens.
Fourth, if you're using Core Web Vitals as a vendor SLA or an internal performance target, decide whether your contracts and goals should reference stable metrics, experimental metrics, or both during the transition period.
The Larger Signal
This release is part of a broader pattern. CrUX added experimental ad metrics in September 2026, measuring ad count, density, and resource weight. Those aren't ranking factors either, but they're signals that Chrome is building a richer picture of real-user experience. The soft navigation metrics follow the same logic: more granular data, more accurate attribution, more ways to understand what users actually encounter.
For marketing leaders, the takeaway isn't about SEO tactics. It's about measurement maturity. The gap between "what our analytics say" and "what users experience" is shrinking. That's good for teams who've invested in actual performance. It's uncomfortable for teams who've been hiding behind blended metrics that obscured slow secondary pages.
Model the change. Document the delta. Update your forecasts. The math is about to get more honest.
