Core Web Vitals in 2026: what changed and what to fix first

Core Web Vitals in 2026: current LCP, INP and CLS targets, the new soft navigation metrics in CrUX, and the fixes that usually matter most.

Crest Design
Speed gauge with three performance metric dials

Core Web Vitals in 2026 are still the same three metrics: Largest Contentful Paint (LCP) for loading, Interaction to Next Paint (INP) for responsiveness and Cumulative Layout Shift (CLS) for visual stability. The "good" thresholds have not changed either: LCP within 2.5 seconds, INP under 200 milliseconds and CLS under 0.1, measured at the 75th percentile of real visits.

What is new is how single-page apps will be measured. In October 2026 Google started publishing experimental Core Web Vitals that include "soft navigations" in its Chrome UX Report, with a target of making them official in May 2027. This guide explains what that means, clears up some confusion about this year's changes, and sets out the fixes that usually matter most, at the time of writing (November 2026).

The current targets

Metric Measures Good
Largest Contentful Paint (LCP) How quickly the main content appears 2.5 seconds or less
Interaction to Next Paint (INP) How quickly the page responds to taps, clicks and key presses 200 milliseconds or less
Cumulative Layout Shift (CLS) How much the layout jumps while loading 0.1 or less

A page passes when it meets all three at the 75th percentile of page loads, with mobile and desktop assessed separately (web.dev). INP replaced First Input Delay in 2024, and Google says stable Core Web Vitals will not change more than once a year.

You may have read that Google tightened the INP threshold or raised the weight of Core Web Vitals in a 2026 core update. We could not find any Google source for those claims. Google Search Central's Core Web Vitals page still lists the thresholds above. What has changed this year are small refinements in how Chrome calculates INP, listed in the Chromium INP changelog, which can nudge scores slightly but do not move the goalposts.

Google's wording is measured. It says good Core Web Vitals, along with other page experience aspects, align with what its core ranking systems seek to reward, and it highly recommends that site owners achieve them. It does not say they outweigh relevance or content quality, and in practice they rarely do.

The stronger case is commercial. A slow or jumpy page frustrates visitors whatever it does for rankings, and checkout, enquiry and booking pages are where that costs you most. Treat the targets as a quality bar for real users, with search as a secondary benefit.

What changed in October: soft navigations

A soft navigation is when JavaScript swaps the page content and updates the URL without loading a new page. Sites built as single-page apps, including many React, Next.js and headless storefronts, do this on most clicks. Until now, Chrome only measured LCP on full page loads, so those later "pages" were largely invisible to Core Web Vitals.

That is changing. Chrome shipped the Soft Navigations API in Chrome 151, and on 13 October 2026 Google added experimental versions of LCP, INP and CLS that include soft navigations to the Chrome UX Report (CrUX). Key points from the announcement:

  • The new metrics are available in the CrUX BigQuery dataset, the CrUX API, the CrUX History API and the CrUX Vis dashboard.
  • Google's stable Core Web Vitals scores are unchanged while the experimental versions are evaluated.
  • Graduation from experimental is targeted for May 2027, subject to feedback. Once they graduate, Search Console will switch to the new data.
  • About 70% of origins have little or no soft navigation traffic, so most traditional sites should see little or no change.
  • For sites where almost all page views are soft navigations, the results generally improve: the share with good LCP on Android rose from 26% to 87% in Google's analysis, although single-page apps still trail traditional sites on INP.

If your site is a traditional multi-page build on WordPress, Shopify themes, Webflow or HubSpot, this is mostly background news. If you run a single-page app, look up your origin in CrUX Vis now and compare the standard and soft navigation numbers, so the 2027 switch holds no surprises.

How to measure your own site

  1. 1 Start with field data. The Core Web Vitals report in Search Console groups URLs by status, and PageSpeed Insights shows CrUX data for a page and its origin when there is enough traffic.
  2. 2 Use lab tools to diagnose, not to judge. Lighthouse and the Chrome DevTools Performance panel show what is slow on your device. Real users on mid-range phones and mobile networks are what the scores reflect.
  3. 3 Check templates, not single URLs. Problems usually sit in a template: product page, blog post, landing page. Fix the template and every page using it improves.
  4. 4 Allow time. CrUX reports a rolling 28-day window, so improvements take weeks to show in field data.

The fixes that usually matter most

LCP: get the main image or heading on screen faster

  • Make sure the hero image is not lazy-loaded, is properly sized and uses a modern format such as WebP or AVIF.
  • Cut render-blocking CSS and JavaScript in the head, and self-host or preload key fonts.
  • Reduce server response time with caching and a CDN. Slow hosting is a common cause on WordPress and Magento sites.

INP: keep the main thread free

  • Audit third-party scripts: chat widgets, tag managers, heatmaps, review and personalisation apps. Each adds work on every interaction.
  • Break up long JavaScript tasks and defer anything not needed for the first interaction.
  • Watch heavy menus, filters and sliders. On ecommerce sites, collection filters and variant pickers are frequent offenders.

CLS: reserve space

  • Set width and height (or aspect ratio) on images, videos and embeds.
  • Reserve space for banners, cookie notices and ad slots instead of pushing content down.
  • Use font loading settings that avoid large text reflows.
Remove before you optimise: the fastest script is the one you no longer load.

Frequently asked questions

Is INP still 200 milliseconds?

Yes. At the time of writing, Google's documentation lists 200 milliseconds or less as good for INP.

Will passing Core Web Vitals improve my rankings?

It can help at the margin, but Google treats it as one part of page experience alongside relevance and content quality. Faster pages often convert better regardless.

Do the soft navigation metrics affect my site today?

Not in Search. They are experimental, and stable Core Web Vitals scores are unchanged. Google is targeting May 2027 for them to graduate.

Need help with site speed?

We audit and fix Core Web Vitals across Shopify, WordPress, Webflow, HubSpot and Next.js sites, starting with field data and the templates that matter most. See our Next.js development services if you run a single-page app, or read our guide to speeding up a slow WordPress site. To get started, send us your site.

Sources: web.dev: Web Vitals, Google Search Central: Core Web Vitals and Google search results, web.dev: Experimental soft navigation metrics now available in CrUX, Chrome for Developers: Final Soft Navigations origin trial, Chromium INP metric changelog

(over to you)

Planning a build like this?

Tell us what you're building and we'll come back with ideas and next steps.