Your Speed Report Stops At Route One

Chrome 151 ships soft navigations so SPA route changes get their own Core Web Vitals. If your RUM still only scores the first load, you are optimizing the lobby while buyers stall on pricing.

Published
Updated
Version
v1.0
Read
3 min
By

Version

v1.0 / current

A green first-load score is not a conversion path. It is a lobby reading while the buyer is already on the next floor.

Your speed report stops at route one.

Chrome 151 began shipping soft-navigation and interaction-contentful-paint entries on the Performance Timeline so same-document route changes can carry their own timing origin (Chrome for Developers, Measuring soft navigations). CSS Wizardry's August field note is blunt about what that means for dashboards: one document can now produce several metric lifecycles, and a migration that replaces the old series in place can invent regressions and wins that never happened in the product (CSS Wizardry).

This is not a framework lecture. It is a CMO measurement problem on modern marketing sites that already behave like apps on pricing, configure, and checkout paths.

The Lobby Score Hides The Money Route

Largest Contentful Paint on the first hard load still matters. Soft navigations do not replace it.

They expose the gap. A catalogue-to-pricing transition that never triggers a full navigation used to keep recycling the lobby LCP while Interaction to Next Paint and layout shift accrued against the wrong URL. Chrome can now emit a soft-navigation entry after a user-initiated URL change with a visible paint, and web-vitals v6 can report per-route Core Web Vitals when reportSoftNavs is on.

The CMO question is simple. Which of your money routes still borrow the homepage score because nobody instrumented the route change?

Parallel Series, Not A Silent Cutover

Do not upgrade the library and overwrite the production chart.

Ask your RUM vendor whether proprietary virtual pages and Chrome's native soft navigations will dual-report. Run the old series and the soft-nav series side by side. Compare reporting rate, route detection, and the distribution of interactions before you trust a new percentile. Keep browser version, web-vitals version, and navigation classification on every beacon so next month's "regression" can be explained.

If soft navigations are unsupported for a share of visits, say so in the weekly readout. A thinner sample is still better than a blended score that pretends every buyer path was measured.

Own The Routes That Close Revenue

Pull the three templates that change revenue this quarter: pricing, demo request, and the post-login or configure step if you have one.

For each, write the owner, whether the transition is a hard load or a soft route, and whether RUM currently attributes LCP and INP to that URL. Then pick one honest move this week:

  1. Enable soft-navigation reporting in parallel and annotate the dashboard cutover date.
  2. Fix the route that stalls after the lobby looks fast, usually a chat widget, consent burst, or heavy hydrate on the money click.
  3. Stop celebrating a sitewide green Core Web Vitals badge that never sliced by template.

Waiting is also a choice. It just leaves the blind spot in place while paid traffic keeps landing on an unmeasured floor.

Measurement Is Part Of Conversion Architecture

Speed work fails when the report cannot see the page the buyer reached.

Chrome finally gave SPA-style marketing sites a standard way to slice that journey. Use it as a control, not as a vanity upgrade. Name the routes. Name the dual series. Name the owner who will not ship a redesign off a lobby score alone.

websitescore-web-vitalsmeasurementspacro
Delivered every weekday

A daily read on AI and marketing. Unsubscribe anytime.

The Briefing

A daily read on AI and marketing.

Ranked signals. Clear implications. Original sources.

Five to eight developments that matter to marketing leaders, with the context to act on each one.

All postsv1.0 / your-speed-report-stops-at-route-one