Skip to content

Core Web Vitals

Core Web Vitals are Google's three metrics for page experience: LCP, INP and CLS. What each measures, the thresholds, and how much they affect ranking.

Definition

Core Web Vitals are three metrics Google uses to measure page experience: Largest Contentful Paint for loading, Interaction to Next Paint for responsiveness, and Cumulative Layout Shift for visual stability. They are measured from real visits rather than from a laboratory test.

Illustration representing core web vitals

Why it matters

Core Web Vitals are the clearest example of a ranking signal that is also just a good idea. A page that loads slowly, responds late to taps and moves under the reader's thumb loses people regardless of where it ranks.

Their weight in ranking is modest and Google has been consistent about that: they are a tie-breaker between pages of comparable relevance, not a substitute for being the better answer. Treating them as the main lever is the most common way to spend a quarter and move nothing.

How it works

The three metrics are defined on web.dev, with thresholds measured at the 75th percentile of real visits:

MetricMeasuresGoodNeeds work
LCPWhen the largest element finishes rendering2.5s or lessover 4.0s
INPDelay between an interaction and the next frame200ms or lessover 500ms
CLSHow much visible content shifts unexpectedly0.1 or lessover 0.25

Interaction to Next Paint replaced First Input Delay as the responsiveness metric in March 2024. FID measured only the delay before the first interaction was processed; INP measures the full path from interaction to the visible update, across all interactions on the page, which is much closer to what a user experiences.

The distinction between field and lab data matters. The scores that count come from the Chrome User Experience Report, which is real Chrome users on real connections and devices. A laboratory tool such as Lighthouse estimates them on a simulated device, which is useful for diagnosis and is not what gets reported.

Worked example

The usual cause differs by metric, and so does the fix:

LCPThe hero image or a web fontServe the right size, use modern formats, preload the element that is actually largest
INPJavaScript occupying the main threadBreak up long tasks, defer what is not needed to paint
CLSImages and embeds without dimensions, fonts swappingReserve the space before the asset arrives
A stack of crates where one low crate has swollen to twice its height, knocking the crates above it askew
An element that arrives without reserved space pushes everything above it down. Setting the dimensions fixes it at the source.

CLS is the one most often caused by something small. An image without width and height attributes collapses to zero height until it loads, then pushes everything down. Setting the dimensions, which is also good alt text hygiene territory, fixes it at the source.

Common mistakes

  • Optimising for Lighthouse instead of field data.
    The lab score is a diagnosis aid. The field data is what Google reports.
  • Chasing 100.
    The thresholds are pass or fail bands. Going from a passing LCP to a faster passing LCP changes no ranking.
  • Treating it as the main SEO lever.
    It is a tie-breaker. A faster page that answers the question worse still loses.
  • Measuring only the home page.
    The scores are per page and grouped by URL pattern. Templates matter more than any single URL.
  • Ignoring mobile.
    The thresholds are the same, the hardware is not, and mobile-first indexing means the mobile experience is the one assessed.

Where to see yours

The Core Web Vitals report in Search Console uses field data and groups URLs by similarity, which tells you which templates are failing rather than which single pages. That grouping is what makes it actionable, and it is where a technical SEO engagement should start on performance rather than with a lab score.

Let's build

Got something to build?

Tell us what you're making. We'll tell you - honestly - if we're the right team, and how we'd do it.