返回资讯中心
外部精选
软件工程
#开发者实时流

Google's Core Web Vitals with Soft Navigations, Reflecting SPA Performance

Since its launch, the Core Web Vitals initiative has sought to measure the real-world user experience of websites, focusing on user-perceived loading speed, interactivity, and visual stability, rather than implementatio…

Hacker News 最新powdercloud2026/10/16 · 2026/10/1611 分钟阅读

以下正文同步自 Hacker News 最新,版权归原站所有,已转换为易读排版。

Annie Sullivan

X

GitHub

LinkedIn

Bluesky

Since its launch, the Core Web Vitals initiative has sought to measure the real-world user experience of websites, focusing on user-perceived loading speed, interactivity, and visual stability, rather than implementation details. However, Single-Page Applications (SPAs) have been a gap for the initiative.

Instead of loading distinct HTML documents as a user navigates, SPAs dynamically update page content and the URL using JavaScript—a transition known as a "soft navigation." Since these are handled differently in each implementation, they have required bespoke custom measurement, making it hard to compare directly across sites.

Today, following the launch of the Soft Navigations web platform API in Chrome 151, Chrome is publishing experimental versions of the Core Web Vitals metrics in the Chrome User Experience Report (CrUX) dataset that include soft navigations.

These new experimental CrUX metrics provide a more complete picture of a user's experience on Single-Page Applications. They expand the aggregate data already publicly available in CrUX by reporting experimental versions of the three Core Web Vitals that blend soft navigations with hard navigations:

While these metrics measure the same speed, responsiveness, and visual stability dimensions as Core Web Vitals, Google's stable Core Web Vitals scores remain unchanged while these experimental versions are evaluated alongside them.

We anticipate adding experimental soft-navigation metrics for navigation types and First Contentful Paint (FCP) in the next CrUX release in November.

Most websites, such as many blogs, news sites, and standard multi-page websites, load a new HTML page from the server each time a visitor clicks a link. Across all origins in CrUX, around 70% have little to no soft navigation traffic (fewer than 5% of page views are "soft"), and only about 7–11% of origins use soft navigations for more than half of their page views. 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.

Changes are concentrated on sites that are both built as Single-Page Applications (SPAs) and have a high volume of follow-up navigations, which represent a small share of the overall web, but account for 35–42% of the top 1,000 websites on both Android and Desktop (see Figure 1).

Previously, when a user browsed an SPA, CrUX only recorded the initial "hard" page load when the user first arrived on the site, while ignoring subsequent in-app page transitions as separate loads and grouping all interactions and layout shifts from the entire session into that initial landing page. With soft navigations included, each in-app view change that updates both the page content and the URL is measured as its own navigation. In the CrUX API, metrics for each soft navigation are also reported under the specific URL the user navigated to rather than the initial landing page (subject to meeting the usual eligibility criteria), making it much easier to pinpoint and debug issues on individual pages.

For the small group of sites with a high share of soft navigations (the shaded >50% region on the right of Figure 2), here is how each metric changes:

You can access these soft navigation metrics in the CrUX BigQuery dataset, CrUX API, and CrUX History API starting with the October 2026 release.

Tip: CrUX Vis has also been updated allowing you to quickly view the new metrics for any URL or origin in the CrUX dataset.

Try it to see how your own metrics change!

Each of the metrics is labeled "experimental" to make clear we're open to community feedback and issues filed in the soft navigations specification repository as we validate and evolve how soft navigations are measured across the web. We're actively working on addressing feedback, so expect some shifts from month to month as the measurement improves.

We aim to graduate from experimental in May of 2027, subject to feedback. Once graduated, Search Console will switch to use the new data.

For more information about how Chrome detects soft navigations and how to measure them in your own Real User Monitoring (RUM), see our documentation on Measuring soft navigations.

正文由 探How 从来源站点 RSS 同步,内容未经改写;遇到排版缺失或需要图片、视频时请以原文为准。

打开原文
去社区讨论 →