Core Web Vitals explained: what LCP, INP and CLS mean

LCP measures loading, INP responsiveness and CLS layout stability. The thresholds, how Google measures them from real visits, and what to fix first.

By Sohail Hussain21 November 20265 min read

Core Web Vitals are three measurements Google uses to judge how a page feels to real visitors. Largest Contentful Paint (LCP) measures loading: how long until the main content appears. Interaction to Next Paint (INP) measures responsiveness: how long the page takes to visibly react to a tap, click or key press. Cumulative Layout Shift (CLS) measures visual stability: how much the content jumps around. A page passes when, for at least 75% of visits, LCP is 2.5 seconds or less, INP is 200 milliseconds or less and CLS is 0.1 or less.

Those thresholds, and the definitions below, come from Google's Web Vitals documentation on web.dev.

What are the thresholds for each metric?

MetricWhat it measuresGoodNeeds improvementPoor
LCPLoading of the main content2.5 s or less2.5 s to 4 sOver 4 s
INPResponse to interactions200 ms or less200 ms to 500 msOver 500 ms
CLSUnexpected layout movement0.1 or less0.1 to 0.25Over 0.25

Each metric is assessed at the 75th percentile of page loads, separately for mobile and desktop. In plain terms: sort all visits from fastest to slowest, and the visit three-quarters of the way along must be within the "good" limit. Three out of four visitors having a good experience is the bar, not the average visitor.

Enter your own numbers in our Core Web Vitals checker to see which band each falls in. If any of them fail, finding and fixing the cause is a core part of our technical SEO and performance work.

What does Largest Contentful Paint measure?

LCP is the time from the start of navigation until the largest image or text block in the viewport is rendered. On most pages that is the hero image, a large heading or the first paragraph. Elements that are invisible, such as those at zero opacity, do not count until they are shown.

The browser keeps updating its LCP candidate as larger elements render, and stops when the visitor first taps, scrolls or presses a key. A slow LCP usually comes from one of four places: a slow server response, an image the browser discovers late, an image that is too large, or rendering held up by CSS, fonts or JavaScript. How to fix a poor LCP score works through each.

What does Interaction to Next Paint measure?

INP looks at every click, tap and key press during a visit and measures how long each took to produce the next frame on screen. Scrolling and hovering are not counted. The reported value is the slowest interaction, ignoring a few outliers on pages with many interactions, so one heavy menu or filter can set the score for the whole page.

Each interaction's time has three parts: the input delay before the browser can start handling it (often because other JavaScript is running), the processing time in the event handlers, and the presentation delay to calculate layout and paint. INP replaced First Input Delay as a Core Web Vital in March 2024. How to fix INP covers the causes, which are almost always too much JavaScript on the main thread.

What does Cumulative Layout Shift measure?

CLS adds up how far visible elements move unexpectedly, weighted by how much of the screen moved. Shifts are grouped into windows of activity, and the score is the worst window, so a page that is open for an hour is not penalised for its length.

Movement within half a second of a tap or key press is excluded, because the visitor caused it. The usual culprits are images without dimensions, web fonts that change text size when they load, and banners, embeds or ads injected above existing content. How to fix layout shift goes through them.

Where do the numbers come from?

There are two kinds of data, and only one of them counts for Google.

Field data comes from real Chrome users who opt in to sharing usage statistics, collected in the Chrome User Experience Report (CrUX). It is a rolling 28-day window. Search Console's Core Web Vitals report and the top section of PageSpeed Insights both show it. This is the data Google's assessment uses.

Lab data comes from a single simulated page load, such as Lighthouse in Chrome DevTools or the lower part of PageSpeed Insights. It is repeatable and good for debugging, but it runs on one simulated device and network. Lighthouse cannot measure INP because nobody interacts with the page; it reports Total Blocking Time as a rough stand-in.

Two consequences follow. A fix takes up to 28 days to show fully in field data. And pages with little traffic may have no field data of their own, in which case Search Console groups them with similar URLs or shows nothing, and PageSpeed Insights may fall back to data for the whole origin. Page speed vs Core Web Vitals explains the difference between the scores in more detail.

If you want field data for every page, add real-user monitoring. Next.js provides a useReportWebVitals hook that sends each visitor's LCP, INP and CLS to any analytics endpoint, and hosts such as Vercel offer the same as a built-in feature.

Do Core Web Vitals affect Google rankings?

Yes, but less than many audits imply. Google's guidance on Core Web Vitals says they are used by its ranking systems and recommends achieving good scores, while also saying that Search always aims to show the most relevant content even if its page experience is weaker. A fast page with a poor answer does not outrank a slower page with a great one.

In practice, treat Core Web Vitals as a threshold to clear rather than a score to maximise. Moving from "Poor" to "Good" is worth real effort, for visitors as much as for rankings: a page that takes six seconds to show its content loses people before they read a word. Shaving LCP from 1.8 to 1.2 seconds is rarely worth a sprint if the content and structure have problems.

Where should you start?

  1. Open Search Console's Core Web Vitals report and note which metric fails, on mobile or desktop, and for which group of URLs.
  2. Run one example URL from that group through PageSpeed Insights and read the field data at the top.
  3. Use the diagnostics in the Lighthouse section, or the Performance panel in Chrome DevTools, to find the cause for that metric.
  4. Fix the template, not the single page, because URLs in a group usually share one.
  5. Check the field data again after four weeks.

Framework choice makes this easier or harder. Pre-rendered pages with optimised images and little client JavaScript pass by default much more often, which is one of the reasons in why we build company websites with Next.js, and Next.js image optimisation covers the biggest single contributor to LCP.

Was this guide useful?

Questions

Frequently asked.

Why does PageSpeed Insights show different numbers from Lighthouse?

The top of a PageSpeed Insights report is field data: real Chrome users over the last 28 days. The Lighthouse section below it is a single simulated load on a throttled phone. Google's assessment uses the field data. Use Lighthouse to find causes and the field data to judge whether you pass.

What happened to First Input Delay?

Interaction to Next Paint replaced First Input Delay as a Core Web Vital in March 2024. FID measured only the delay before the first interaction started being handled. INP measures the full time to a visible response for interactions throughout the visit, so it catches slow pages that FID missed.

Does a Lighthouse score of 100 mean I pass Core Web Vitals?

No. Lighthouse runs one simulated load and cannot measure INP at all; it reports Total Blocking Time as a stand-in. A page can score 100 in the lab and fail in the field on real phones and networks, or the reverse. Only field data decides.

Sohail Hussain

Founder, MSH Technologies

Sohail has designed and built websites, web apps and AI products for over 12 years, for clients from Singapore-based industrial groups to early-stage SaaS startups. He writes about what actually worked.

Keep reading

Related guides.

All posts

Your next move

Like what you see? Tell us about it.

A process that takes too long, a website that undersells you, or an idea ready to take shape. Tell us where you are and we will suggest a useful next step.

India · Working with clients worldwide

Sohail, Founder, replies within 1 working day (Mon–Sat, IST). Free and no obligation.