Core Web Vitals after INP: what the three metrics measure and what usually needs fixing

The three metrics

Core Web Vitals are a set of user experience metrics defined by Google. Each describes something visitors notice: how quickly the main content appears, how quickly the page responds when they interact, and whether content jumps around while it loads.

Google assesses them at the 75th percentile of page loads, separately for mobile and desktop. That means a page is considered good only if at least three quarters of real visits meet the threshold, so a fast result on a developer’s laptop proves very little.

Largest Contentful Paint (LCP)

Time until the largest image or text block in the viewport is rendered. Good is 2.5 seconds or less; poor is more than 4 seconds.

Interaction to Next Paint (INP)

How long the page takes to visually respond to clicks, taps and key presses across the visit. Good is 200 milliseconds or less; poor is more than 500 milliseconds.

Cumulative Layout Shift (CLS)

How much visible content moves unexpectedly. Good is 0.1 or less; poor is more than 0.25.

Why INP replaced First Input Delay

First Input Delay measured only the delay before the browser could start handling the first interaction on a page. It ignored the time spent processing that interaction and painting the result, and it ignored every interaction after the first. Most sites passed it easily, even when they felt sluggish.

Interaction to Next Paint became a Core Web Vital on 12 March 2024. It observes interactions throughout the visit and reports a value close to the slowest, covering input delay, the time event handlers run and the time until the next frame is painted. Pages heavy with JavaScript, tag managers, chat widgets and complex menus often score worse under INP than they did under FID.

Field data versus lab data

Field data comes from real users. The Chrome User Experience Report collects anonymised measurements from eligible Chrome users and reports them over a rolling 28-day window. It powers the Core Web Vitals report in Search Console and the field section of PageSpeed Insights. Low-traffic pages may not have enough data of their own, in which case results are grouped at site or origin level.

Lab data comes from tools such as Lighthouse, which load a page in a simulated environment. It is useful for diagnosing problems and testing changes before release, but it cannot measure INP directly because there is no real user interacting. Total Blocking Time in the lab is a helpful proxy for responsiveness problems.

Because field data is averaged over 28 days, a fix released today takes weeks to show fully in reports. Teams that add their own real-user monitoring can see the effect sooner and break results down by template, device and country.

Common causes of poor LCP

The largest element on business websites is usually a hero image, a slider or a large headline. Poor LCP typically comes from images that are too large, served without modern formats or responsive sizes, loaded lazily even though they are visible immediately, or discovered late because they are set in CSS or injected by JavaScript.

Slow server response is the other major cause. Uncached pages generated on every request, distant hosting without a content delivery network, and redirects before the page loads all add delay before the browser can even start rendering. Web fonts that block text rendering can delay LCP when the largest element is text.

Effective fixes include serving properly sized images in modern formats, prioritising the hero image rather than lazy-loading it, caching pages at the edge, preloading critical fonts and removing sliders that load several large images at once.

Common causes of poor INP

INP problems are almost always about the main thread being busy. Large JavaScript bundles, many third-party tags, analytics and advertising scripts, consent tools, chat widgets and heatmap tools all compete for the same thread that must respond to user input.

Heavy event handlers are the next cause: a filter that re-renders a whole product list, a menu that recalculates layout for every item, or a form that validates everything on each key press. Large DOM sizes make every update slower.

Fixes include removing unused scripts and tags, loading non-essential third parties later, splitting long tasks so the browser can respond between them, giving immediate visual feedback before doing expensive work, and simplifying pages with very large numbers of elements.

Common causes of poor CLS

Layout shifts happen when content appears without reserved space. Images and videos without dimensions, cookie banners and promotional bars inserted at the top of the page, embedded content such as maps or social posts, and web fonts that change text size when they load are the usual culprits.

Setting width and height or aspect ratios for media, reserving space for banners and embeds, placing consent notices so they overlay rather than push content, and choosing font loading strategies with matched fallback metrics prevent most shifts.

How much Core Web Vitals matter for search

Google includes Core Web Vitals in its page experience signals, and it has said that good results support ranking but do not guarantee top positions, because relevance and helpful content matter more. A slow page with the best answer can still outrank a fast page with a weak one.

The stronger business case is usually conversion. Visitors abandon slow pages, misclick when layouts shift and lose patience with forms that respond late. Treat Core Web Vitals as a measure of whether the site works well for real people on real devices, and search benefits follow as a side effect.

Where this sits in what we do

This article covers one decision inside a wider engagement. The solution page sets out how that engagement runs, what it includes and what it costs to find out.

• Digital Growth — The ongoing programme — strategy, content, paid, organic and reporting — run as one thing that answers to pipeline rather than to channel dashboards.
• Quote to cash without re-keying: where the handoffs break
• Product data is the e-commerce growth lever nobody budgets for
• Customer care for logistics companies: proactive delay communication beats a bigger call centre
• Customer data platform or CRM: what each is for, and when a business needs both
• All insight articles