Core Web Vitals: What They Measure and How to Fix Them

Three metrics that decide whether your site feels fast — what each one measures, what usually breaks it, and the order to fix them in.

Core Web Vitals: What They Measure and How to Fix Them — Troiana insight cover

In short

Core Web Vitals are three metrics Google uses to quantify user experience: Largest Contentful Paint (LCP) for loading, Interaction to Next Paint (INP) for responsiveness, and Cumulative Layout Shift (CLS) for visual stability. Good scores are LCP within 2.5 seconds, INP within 200 milliseconds and CLS of 0.1 or less, measured for at least 75% of real visits. Most failures come from a heavy hero image, long JavaScript tasks, or content that loads without reserved space.

What Core Web Vitals measure

Core Web Vitals turn three vague feelings — is it loading, does it respond, does it hold still — into measurable numbers, gathered from real users. They are part of how Google assesses page experience, but their real value is that they describe whether a visit feels fast enough to continue. Google assesses each metric at the 75th percentile of page loads, so a page passes only when three in four visits meet the target. The thresholds are published on web.dev.

MetricMeasuresGoodNeeds improvementPoor
Largest Contentful Paint (LCP)Loading: when the largest visible element has rendered2.5 s or lessUp to 4 sOver 4 s
Interaction to Next Paint (INP)Responsiveness to taps, clicks and key presses across the visit200 ms or lessUp to 500 msOver 500 ms
Cumulative Layout Shift (CLS)Visual stability: how much the layout jumps0.1 or lessUp to 0.25Over 0.25

INP replaced First Input Delay as a Core Web Vital in March 2024. It is stricter, because it looks at every interaction in a visit rather than only the first.

LCP: loading
2.5 s or lessUp to 4 sOver 4 s
INP: responsiveness
200 ms or lessUp to 500 msOver 500 ms
CLS: visual stability
0.1 or lessUp to 0.25Over 0.25
Google's published bands, shown side by side. The widths aren't to scale. Search Console's field data is what these are judged on.

Start with field data, not a single lab test

Search Console's Core Web Vitals report shows real-user field data, grouped by URL pattern. Start there to see which templates actually fail for real visitors, rather than testing one page in a lab tool and assuming it represents the whole site. Use lab tools such as Lighthouse afterwards, to iterate quickly on a specific fix. If you have not set up the property yet, follow how to set up Google Search Console the right way.

How to fix Largest Contentful Paint (LCP)

The usual causes are an oversized hero image, render-blocking CSS or JavaScript that delays the first paint, and a slow server response. In order of typical impact:

  • Serve the hero image at the right size and in a modern format such as WebP or AVIF, and preload it. See how to optimise images for speed and search.
  • Never lazy-load the LCP image. Lazy-load what sits below the fold instead; how to lazy-load images the right way explains the split.
  • Remove render-blocking resources by inlining critical CSS and deferring non-critical scripts.
  • Speed up the server response with caching or a faster hosting tier.

Image weight is usually the biggest single lever. On our Catering Prishtina build, the image work cut the site's photographic payload by 96.2%.

How to fix Interaction to Next Paint (INP)

Poor INP is usually caused by long JavaScript tasks blocking the main thread at the moment someone interacts. Break long tasks into smaller chunks, do less work on the main thread, and defer JavaScript that is not needed for the first interaction. Give immediate visual feedback (a pressed state, a spinner) before any heavy work starts, so the page responds even while it is busy.

How to fix Cumulative Layout Shift (CLS)

The common causes are images and embeds without explicit dimensions, ads or banners injected without reserved space, and web fonts that swap in with different metrics from the fallback. Set width and height on every image and video, reserve space for anything that loads late, and avoid inserting content above what the reader is already looking at. For fonts, pair font-display: swap with a fallback whose metrics are adjusted to match; how to optimise a web font for speed shows the technique.

Third-party scripts deserve special attention

Analytics tags, chat widgets, ad scripts and social embeds are collectively one of the most common causes of poor INP and CLS, because they sit outside your direct control and often load more aggressively than they need to. Audit what actually runs, remove anything that is not earning its cost, and load the rest asynchronously or after the first interaction.

Which to fix first

If all three metrics fail, fix LCP first: it is usually the highest-impact problem and the one visitors notice most. Then CLS, because the fixes, such as adding dimensions, are often quick relative to their effect. INP usually takes longest, since it can mean restructuring how JavaScript runs, but it matters most on interaction-heavy pages such as forms, filters and checkouts.

Confirm each fix in a lab tool, then wait for the field data. Search Console's report is based on a rolling 28-day window of real visits, so a fix takes up to four weeks to show fully.

Do Core Web Vitals affect rankings?

Yes, as part of Google's page experience signals, but relevance and content quality matter far more; a fast page that does not answer the query will not outrank a slower one that does. The stronger reason to care is the people using the site. A fast LCP, a responsive INP and a stable CLS are what a considered product feels like, which is why our performance and infrastructure work treats speed as a design constraint from the first screen, not a clean-up task before launch. For the broader build choices behind these scores, see what makes a website fast, or book a call if you would like us to look at your field data.

Common questions

What are the three Core Web Vitals?

Largest Contentful Paint (LCP), which measures loading; Interaction to Next Paint (INP), which measures responsiveness; and Cumulative Layout Shift (CLS), which measures visual stability.

What are good Core Web Vitals scores?

LCP of 2.5 seconds or less, INP of 200 milliseconds or less, and CLS of 0.1 or less, met by at least 75% of real page loads.

Do Core Web Vitals affect SEO?

Yes, they are part of how Google evaluates page experience, but relevance and content quality matter more. Their bigger effect is on visitors: faster, more stable pages keep more people on the site.

Should I fix Core Web Vitals based on lab data or field data?

Use field data from Search Console or real-user monitoring to decide which pages and metrics need fixing, and lab tools such as Lighthouse to check quickly that a specific fix worked.

How long until fixes show in Search Console?

Up to about four weeks. The Core Web Vitals report uses a rolling 28-day window of real-user data, so improvements appear gradually as older visits drop out.

Have something worth building right?