Core Web Vitals

CrUX adds experimental Core Web Vitals for soft navigations in SPAs

The October release brings route-aware field data to CrUX, with graduation targeted for May 2027 subject to feedback.

Minimal illustration of browser route panels connected to an abstract chart and data table.

CrUX has introduced experimental Core Web Vitals that include soft navigations, extending its field data to route changes inside single-page applications. Announced on October 13, 2026, the metrics are available alongside the stable measurements, which remain unchanged. The update matters most for SPAs whose visitors continue through several views without loading a new document.

For site owners, the immediate task is comparison. The experimental results can be inspected now, but they do not replace the stable scores during evaluation. Google is targeting May 2027 for graduation, subject to feedback; Search Console will switch to the new data once that graduation happens.

The route after the landing page becomes visible

A traditional navigation loads another HTML document. An SPA can instead use JavaScript to replace content and update the URL within the document already open. The visitor reaches another view, but the browser has not performed the same kind of page load.

The announcement describes this as a measurement gap. Previously, CrUX recorded the initial hard navigation while subsequent in-app transitions were not treated as separate loads. Interactions and layout shifts across the SPA session were grouped under that arrival page. The experimental approach measures qualifying changes of content and URL as individual navigations.

That changes the unit being examined. Loading, responsiveness and visual stability remain the concerns, but the measurement can now follow the views a visitor actually opens. Our guide to Core Web Vitals in SPAs provides related background on route performance.

What is available in the October release

What changed Where Status
Core Web Vitals including soft navigations CrUX BigQuery, CrUX API and CrUX History API Experimental from October 2026
Viewing the new measurements CrUX Vis Available for URLs and origins in CrUX
Existing Core Web Vitals scores Stable measurements Unchanged during evaluation

The official announcement of experimental CrUX soft navigation metrics identifies the new fields and their availability. CrUX Vis also exposes the measurements, giving owners a way to inspect their own origin or an eligible URL without starting with a dataset query.

The experimental fields sit alongside the familiar metrics. Keeping that distinction visible is essential when reviewing results: a value from the new approach and a value from the stable approach describe differently grouped navigation activity.

What each experimental metric measures

Loading across hard and soft navigations

experimental_largest_contentful_paint_with_softnavs measures Largest Contentful Paint across full document loads and soft navigations. It brings subsequent views into the loading picture instead of leaving the initial page load as the only navigation represented.

The source explains that follow-up views can reuse code and assets already downloaded. This is part of its explanation of the different results for SPA journeys. A changed experimental value therefore needs to be read in the context of which navigations are now included, rather than being presented as proof that a new optimization was deployed.

Responsiveness attributed to individual views

experimental_interaction_to_next_paint_with_softnavs segments Interaction to Next Paint by individual soft navigations as well as hard navigations. It no longer assigns every interaction across the entire SPA session to the first load.

That attribution change does not remove the underlying JavaScript work. The announcement specifically notes that heavy work on the main thread during route transitions can still cause INP problems. Teams reviewing responsiveness should keep the actual route transition in view when interpreting the new grouping.

Visual stability within each navigation

experimental_cumulative_layout_shift_with_softnavs segments Cumulative Layout Shift across hard and soft navigations. Visual stability is evaluated for the individual view and URL instead of combining shifts across a longer SPA session.

The CrUX API can also attribute soft navigation measurements to the destination URL rather than the initial landing URL, subject to the usual eligibility requirements. That qualification matters: the announcement does not promise a URL record for every route on every site.

Which sites should examine the difference

Google says most websites, including many SPAs, will see identical or nearly identical experimental values. The changes are concentrated on SPAs with substantial follow-up navigation. Sites that do not dynamically change page content and the URL without a full reload should not expect their metrics to change for this reason.

For an owner, the useful distinction is how visitors navigate, not simply whether a framework appears in the technology stack. Check the origin's experimental values, compare the matching stable metrics, and then review the SPA routes involved. Keep the difference between field data and lab data clear when moving from CrUX results to a local investigation.

What to do while the measurements remain experimental

Begin with the available CrUX view of your origin. Compare loading, responsiveness and visual stability separately, and preserve the experimental label when sharing the results. Where URL data is available, use the destination attribution to focus the route review.

Do not assume every month-to-month difference reflects a change to the website. Google says the measurement is still being validated and refined, so values can shift as that work progresses. May 2027 is the stated goal for leaving the experimental phase, not an unconditional switch date. Until graduation, the new data is available for investigation while stable Core Web Vitals continue unchanged.

Related guides