Skip to content
Wladimir Ming
Web performance

Core Web Vitals explained: LCP, INP and CLS without the jargon

What the three Core Web Vitals measure, the official thresholds, how field and lab data differ and where to start improving them.

Published 3 min read
Minimal landscape at dawn: a speed gauge with the needle in the fast zone, a lightning bolt and a dashed path climbing to a small tower.

Core Web Vitals are three metrics Google uses to describe the real-world experience of loading, responding to and viewing a page. They are part of Google's page experience signals, but they are also simply a good proxy for whether a site feels fast.

The three metrics

MetricMeasuresGoodPoor
LCP (Largest Contentful Paint)When the main content becomes visible≤ 2.5 s> 4 s
INP (Interaction to Next Paint)How quickly the page responds to interactions≤ 200 ms> 500 ms
CLS (Cumulative Layout Shift)How much the layout moves unexpectedly≤ 0.1> 0.25

Values between "good" and "poor" are rated needs improvement. A page passes when the 75th percentile of real visits meets the "good" threshold for all three, evaluated separately for mobile and desktop.

INP replaced First Input Delay (FID) as a Core Web Vital in March 2024. It is stricter: it considers interactions throughout the visit, not just the first one.

Field data vs lab data

  • Field data comes from real users, for example the Chrome UX Report (CrUX), shown in PageSpeed Insights and Search Console. This is what the assessment is based on.
  • Lab data comes from a simulated load in a controlled environment, such as Lighthouse. It is ideal for debugging, but it cannot fully reproduce real devices and networks, and it can't measure INP directly (Total Blocking Time is used as a proxy).

A perfect Lighthouse score with poor field data usually means real users have slower devices, worse networks or different journeys than the test.

Where to start

LCP

  • Reduce server response time (caching, edge rendering, fewer redirects).
  • Make the LCP element discoverable early: don't lazy-load the hero image, and consider fetchpriority="high".
  • Serve modern image formats at the right size.

INP

  • Ship less JavaScript and avoid long tasks on the main thread.
  • Break up heavy work and yield to the browser so it can paint.
  • Audit third-party scripts: they are a frequent cause of slow interactions.

CLS

  • Always reserve space for images, embeds and ads (width/height or aspect-ratio).
  • Avoid inserting content above existing content after load.
  • Load web fonts in a way that minimises layout changes.

How much do they matter for rankings?

Google has said that great page experience does not override relevance: a highly relevant page can still rank with average vitals. In practice, Core Web Vitals matter most when competing pages are similarly relevant, and they always matter for users, conversions and bounce rates.

See it live

The case study of this website shows LCP, CLS, FCP and TTFB measured in your own browser during your visit, using the standard PerformanceObserver API. It's a small demonstration of the idea behind field data: the numbers that count are the ones real visitors experience.

Share on LinkedIn(opens in a new tab)

Need this applied to your site?