1. Home
  2. Guides
  3. Core Web Vitals
Performance guide

Core Web Vitals: what they are and how to improve them

Three user-experience metrics that Google measures for real visitors: how fast the main content appears, how quickly the page reacts, and whether it stays still while you read. Here is what each one means and what to fix first.

Key points

  • Core Web Vitals are LCP (loading), INP (responsiveness) and CLS (visual stability).
  • A page passes when the 75th percentile of real visits is in the “good” range for all three metrics.
  • Lab tools like Lighthouse are for debugging. They cannot measure INP directly, so they report Total Blocking Time as a stand-in.

What are Core Web Vitals?

Core Web Vitals are a small set of metrics that describe how a page feels to a real person: how quickly the main content shows up, how fast the page reacts when you tap or type, and whether things jump around while you read. Google publishes a threshold for each one and measures them from real Chrome users.

They are worth caring about for a simple reason. A page that loads slowly, lags on a tap or shifts under your finger is frustrating, and frustrated visitors leave. They are also part of Google's page experience signals, although relevance and content quality still count for much more. Treat good Core Web Vitals as a way to keep visitors happy rather than a shortcut to rankings.

The three metrics and their thresholds

Each metric is judged at the 75th percentile of page loads, separately for mobile and desktop. In practice that means three out of four visits need to be at least as good as the threshold.

MetricWhat it measuresGoodNeeds improvementPoor
LCPLoading≤ 2.5 s2.5–4 s> 4 s
INPResponsiveness≤ 200 ms200–500 ms> 500 ms
CLSVisual stability≤ 0.10.1–0.25> 0.25

Each metric has its own guide with causes and fixes: Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift.

Lab data vs field data

Field data comes from real users. Google collects it in the Chrome User Experience Report (CrUX) and aggregates it over a rolling 28-day period. It is what Google uses to assess a site, and it is what tools like PageSpeed Insights and Search Console show as “real user” results.

Lab data comes from a single controlled test, for example Lighthouse on an emulated phone with a throttled network. It is repeatable, which makes it ideal for debugging, but it is not what your visitors experience. Two consequences follow:

  • Lab and field numbers will differ. Neither is wrong; they answer different questions.
  • INP needs real interactions, so a lab run cannot produce it. Lighthouse reports Total Blocking Time (TBT), which measures how long the main thread was blocked during loading. High TBT is a good warning sign for INP problems, but it is a proxy.

WebsiteHealthLabs reports lab metrics from Lighthouse and labels them as lab data. We do not show field data. To see field data for your site, use PageSpeed Insights or the Core Web Vitals report in Google Search Console.

A sensible order of fixes

  1. Fix the LCP element. It is usually a hero image or a large heading. Right size, right format, discovered early, high priority.
  2. Remove render-blocking resources. Inline critical CSS and defer scripts that are not needed for the first paint.
  3. Reserve space for images, ads and embeds to settle layout shifts.
  4. Cut JavaScript. Remove unused libraries and review third-party scripts. This helps INP and TBT the most.
  5. Re-test in the lab, then watch the field data over the next weeks to confirm real visitors benefit.

Quick check. In a WebsiteHealthLabs report, the Performance section shows LCP, TBT and CLS with the threshold bands, plus the specific opportunities Lighthouse found for your page.

See also: Mobile-friendly checklist, Page weight explained.

FAQ

Are Core Web Vitals a Google ranking factor?

They are part of Google's page experience signals, but they are one of many. Relevance and content quality matter far more. Good Core Web Vitals remove a possible disadvantage and make the site nicer to use; they do not replace good content.

What replaced First Input Delay (FID)?

Interaction to Next Paint (INP) replaced First Input Delay as a Core Web Vital on March 12, 2024. FID only looked at the delay before the first interaction was handled. INP considers the responsiveness of the interactions throughout a visit.

Why is my lab score different from my field data?

A lab tool such as Lighthouse runs one controlled test on a simulated device and network. Field data aggregates many real visits on different devices and connections over 28 days. They measure different things, so use lab data to find and fix problems and field data to judge the real-world result.

Do I need to pass all three metrics?

To be assessed as passing, a page needs good results for all three at the 75th percentile. If one is poor, start there: improving the weakest metric usually brings the most benefit to visitors.

WebsiteHealthLabs Editorial
Guides explain audit results in plain English. Facts are checked against public documentation from Google, W3C and the browser vendors, and we update them when guidance changes.

↑ ↓ to moveEnter to openEsc to closeAll results