What Are the Core Web Vitals? LCP, INP & CLS Explained (2026)

Everything you need to know about the Core Web Vitals: metrics, thresholds, measurement tools, and how to pass them.

Arjen Karel
Updated · 10 min read
Share

The Core Web Vitals in short

The Core Web Vitals are three Google metrics: Largest Contentful Paint (LCP, loading) is good at 2.5 seconds or less, Interaction to Next Paint (INP, responsiveness) at 200 milliseconds or less and Cumulative Layout Shift (CLS, visual stability) at 0.1 or less. Google checks each at the 75th percentile of real Chrome visits over the last 28 days, for phones and desktop separately.

What are the Core Web Vitals?

Google's Core Web Vitals (CWV) cover three types of experience, with one metric each:

  • Loading: Largest Contentful Paint (LCP), how long before the main content is on screen.
  • Responsiveness: Interaction to Next Paint (INP), how long the page takes to react to a click, tap or key press.
  • Visual stability: Cumulative Layout Shift (CLS), how much the content moves on its own.

Time to First Byte (TTFB) and First Contentful Paint (FCP) are diagnostic metrics. Both come before LCP, so a slow one holds LCP back.

What was the last Core Web Vitals update, and what is next?

On 12 March 2024, INP replaced First Input Delay (FID): the last Core Web Vitals update so far. FID timed only the wait before the browser started on the first interaction; INP times every interaction up to the next frame, and more sites fail it. Google changes the stable Core Web Vitals at most once a year.

Since October 2026, Chrome's field data (CrUX) also has experimental versions of the three metrics that count soft navigations: the pages a single-page app shows without loading a new document. Google aims to end the experiment in May 2027, and then Search Console switches to the new data. Most WordPress and Shopify sites load a new page on every click, so for them the switch changes nothing.

When do you pass the Core Web Vitals?

A page passes the Core Web Vitals when LCP, INP and CLS are each good for at least 75% of its visits in CrUX (Google's Chrome User Experience Report): PageSpeed Insights then shows "Core Web Vitals Assessment: Passed".

  • Largest Contentful Paint: good at 2.5 s or less, needs improvement up to 4 s, poor over 4 s.
  • Interaction to Next Paint: good at 200 ms or less, needs improvement up to 500 ms, poor over 500 ms.
  • Cumulative Layout Shift: good at 0.1 or less, needs improvement up to 0.25, poor over 0.25.

Google looks at the URL first. When the URL has too few Chrome visits, Google falls back to a group of similar URLs, then to the whole site (the origin). The steps to a pass are in how to pass the Core Web Vitals.

Why the 75th percentile?

The median only tells you about the faster half of your visitors. A stricter percentile would let a few visits from a train with one bar of signal fail the whole page. p75 sits in between: three out of four visits need to be good.

Your own laptop on office wifi tells you very little. The visits that decide p75 are the slower phones on mobile networks.

Is there a Core Web Vitals score?

No, there is no single Core Web Vitals score. Each metric is good, needs improvement or poor, and a URL passes when all three are good. The 0 to 100 score in PageSpeed Insights is the Lighthouse Performance score, a lab score from one simulated load; Google ranks on the field data above it.

Are the Core Web Vitals rated separately on mobile and desktop?

Yes. Google rates the Core Web Vitals for mobile and desktop separately, so a page can pass on one and fail on the other. Phones fail LCP and INP more often: a slower CPU, less memory, a slower network. Desktop fails CLS more often, because the wider screen shows more elements that can shift. Even the LCP element can differ: on a phone it is often a heading, on desktop an image further down.

PageSpeed Insights opens on the mobile tab. Stay there: the desktop tab is often green and makes people think they pass.

The three Core Web Vitals metrics

LCP (loading), INP (responsiveness) and CLS (visual stability) each have two thresholds: up to the first the metric is good, past the second it is poor, and in between it needs improvement.

Diagram of the three Core Web Vitals: LCP, Largest Contentful Paint (loading), good up to 2.5 s and poor above 4.0 s; INP, Interaction to Next Paint (interactivity), good up to 200 ms and poor above 500 ms; CLS, Cumulative Layout Shift (visual stability), good up to 0.1 and poor above 0.25

Largest Contentful Paint (LCP): loading

Largest Contentful Paint (LCP) is the time from the start of the page load until the largest image or block of text in the first screen is painted. Good is 2.5 seconds or less at the 75th percentile, poor is over 4 seconds. On most pages the LCP element is the hero image or the main heading.

When the LCP element is late, the reason is usually boring: loading="lazy" on the hero image, a hero set as a CSS background that the browser only finds after the stylesheet is in, or a slider script that has to run before the first slide shows. Most WordPress plugins that lazy load images have a setting to leave the hero out. In the code, put the hero in the HTML as an image without lazy loading, with fetchpriority="high" (LCP request discovery). The Largest Contentful Paint guide goes through the four parts of LCP.

Interaction to Next Paint (INP): responsiveness

Interaction to Next Paint (INP) is the time from a click, tap or key press until the browser paints the next frame, for the slowest interaction of a visit or close to it. Good is 200 milliseconds or less at the 75th percentile, poor is over 500 milliseconds.

Often the click handler itself is fast, but the main thread is busy with something else when the tap comes in: a tag manager, a chat widget, a framework still hydrating. Most of that JavaScript can be deferred or scheduled. Delaying all JavaScript until the first interaction moves that work onto the first click, which is exactly what INP measures. In a lab test, Total Blocking Time (TBT) is the closest number to INP. More in the Interaction to Next Paint guide.

Cumulative Layout Shift (CLS): visual stability

Cumulative Layout Shift (CLS) is a score for how much visible content moves on its own while a visitor uses the page. Good is 0.1 or less at the 75th percentile, poor is over 0.25. You go to tap a link and the page jumps.

Each shift scores the impact fraction (how much of the viewport moved) times the distance fraction (how far it moved). Shifts less than a second apart add up to one burst of at most 5 seconds, and the worst burst is the page's CLS.

The usual causes: images without width and height; ads, cookie banners and embeds that push content down; a web font that swaps in at another size than its fallback. font-display: swap alone keeps that shift; a fallback font sized like the web font stops it (Font display). Aim for a CLS of 0: a shift inside the good range still moves the line someone is reading. More in the Cumulative Layout Shift guide.

Why do the Core Web Vitals matter?

The Core Web Vitals are a small ranking factor for Google, and your visitors notice a slow page long before Google does. A button that does nothing for half a second gets clicked twice, then abandoned.

Google uses each metric on its own: a metric helps a little as it moves from needs improvement to good, and the gain stops at good. A slow page with the best answer still outranks a fast page with a weak one. How much they weigh is in Core Web Vitals and SEO.

What is the difference between field data and lab data?

Field data comes from real visitors, on their own devices and networks; the Core Web Vitals are field data, from Chrome users in CrUX (Google's Chrome User Experience Report). Lab data comes from one test load on a test device, in Lighthouse or WebPageTest. A lab test gives roughly the same result every run: good for debugging, but it says little about your visitors.

Lighthouse says 100, so why do I fail?

Because Google ranks on CrUX, and Lighthouse tests one simulated visit. Your visitors are on cheap Android phones and bad hotel wifi, and they click on things Lighthouse never touches. INP does not even exist in a Lighthouse run.

In PageSpeed Insights the field data is the top section, "Discover what your real users are experiencing". Why Lighthouse and the field data disagree is in lab against field data.

PageSpeed Insights for bbc.com, mobile, field data: Core Web Vitals Assessment Passed, LCP 1.2 s, INP 109 ms, CLS 0.03, latest 28-day period, various mobile devices and network connections

PageSpeed Insights for bbc.com on mobile, the field data section.

How do you measure and track the Core Web Vitals?

Google's own measurement of the Core Web Vitals is in PageSpeed Insights, Search Console and CrUX Vis: all three show CrUX, the 75th percentile of the last 28 days. A real user monitoring (RUM) tool on your own site tracks them every day.

Core Web Vitals tools compared

  • CrUX (Chrome User Experience Report): field data, the numbers Google uses; CrUX Vis shows a site over months.
  • PageSpeed Insights: field data from CrUX and a lab test, for a quick check of one URL.
  • Google Search Console: field data from CrUX, for which URL groups fail.
  • CoreDash (RUM): field data from every visit, per day, page, device and element.
  • Lighthouse: lab only, no Core Web Vitals, for finding issues on one page.
  • Chrome DevTools: your own visit, with CrUX field data beside it, for reading a trace.

CrUX data

The CrUX dataset holds the Core Web Vitals of every site and page with enough Chrome traffic. CrUX Vis shows a site or URL over the past months; it replaced the CrUX Dashboard, retired after November 2025. The CrUX API gives the numbers for your own tools, CrUX on BigQuery every origin month by month, and the CrUX History report a site or URL week by week.

A site or page with too few Chrome visits has no CrUX data at all: new sites, small sites and pages behind a login often show nothing.

CrUX History report, Largest Contentful Paint on phones: from May to mid August about 58% of page loads are good, then four weekly bars climb to 93% and stay there

CrUX History report, LCP on phones week by week: green is the share of page loads with a good LCP.

Which tracking tool shows the Core Web Vitals every day?

Real user monitoring (RUM) measures the Core Web Vitals on every visit with a small script on your site and shows them day by day.

To find out which page, device and element is behind a fail, I use real user monitoring: CoreDash, which I built for exactly this. Every release can break something again, so keep watching your field data after the fix goes live. CoreDash checks the metrics every day and sends an alert by email or Slack when one gets worse.

CoreDash LCP timeline, 75th percentile per day: about 4.2 seconds in late January, then about 2 seconds from 1 February on

CoreDash, LCP at the 75th percentile per day: a fix or a regression shows the next day.

Lighthouse

Lighthouse is a lab test. It loads one page, once, on a simulated phone with a throttled connection and an empty cache, and never clicks. It is still the fastest way to see what blocks rendering, which image is the LCP element and which scripts keep the main thread busy. Ignore half of the list, though. Minifying CSS saves a few kilobytes and none of your visitors will notice.

How many sites pass the Core Web Vitals?

According to the State of Web Vitals, a study of 241,447 sites, 69.7% pass all three Core Web Vitals on phones. LCP is the metric sites miss most often: 81.9% have a good LCP on phones, against 88.9% for CLS and 91.8% for INP.

How do you improve the Core Web Vitals?

Fix only the Core Web Vitals that fail, phones first: LCP, starting with the server's time to first byte (TTFB), then INP, then CLS. According to the State of Web Vitals, TTFB is the largest of the four parts of LCP on phones for 67.6% of sites with an image as the LCP element, so caching the HTML at your CDN is usually the quickest win.

Where I start: p75 per metric on mobile, then the URL group Search Console flags, then the trend. A sudden drop usually points at a deploy. A slow slide is third-party scripts piling up, one tag at a time.

A plugin fixes images that aren't lazy loaded and scripts that aren't deferred. A slider that rebuilds the layout with JavaScript, or a very large DOM, stays as it is.

A Core Web Vitals guide per metric

The fixes in order are in How to pass the Core Web Vitals; after a large change, go through the Core Web Vitals checklist.

What should you learn to become a Core Web Vitals expert?

A Core Web Vitals expert knows how browsers work, well enough to tell parsing, style, layout and paint apart in a trace without the labels. Then JavaScript, because slow code hurts INP and usually LCP too. After that, HTML and CSS, where the same component often has a fast and a slow build. And networks and servers: caching headers, compression, HTTP/2 and HTTP/3. For a team that wants to fix its own site, there is the Core Web Vitals training.

Where do you find the Core Web Vitals report in Search Console?

Search Console has the Core Web Vitals report under Experience, one per device. It groups similar URLs, usually one template per group, and rates each group by its worst metric. An issue names the metric, the threshold and the device: "LCP issue: longer than 2.5s (mobile)".

Search Console Core Web Vitals report, mobile: 0 poor, 14 need improvement and 729 good URLs, with INP issue: longer than 200ms (mobile) and CLS issue: more than 0.1 (mobile) under Why URLs aren't considered good

Search Console, Core Web Vitals on mobile: the issues are listed under "Why URLs aren't considered good".

The report covers the last 28 days, and its data is about two days old. So two weeks after a fix goes live, half of what it shows is still the old site (the 28-day window, day by day).

Search Console flags a group of pages and you can't tell which template, element or script to start with? In a Core Web Vitals power hour we open your field data together, and you leave with the fixes in the order to do them.

About the author

Arjen Karel is a web performance consultant and the creator of CoreDash, a Real User Monitoring platform that tracks Core Web Vitals data across hundreds of sites. He also built the Core Web Vitals Visualizer Chrome extension. He has helped clients achieve passing Core Web Vitals scores on over 925,000 mobile URLs.

Arjen Karel

Need a faster site?

I'm Arjen, and I've been fixing slow sites for 17 years. If you're running into issues you can't fix yourself, send me your URL and let's have a chat.

Send me your URL
Arjen Karel
Arjen Karel, Web performance consultant since 2009

Why isn't our fix working?

Sometimes the CDN still serves the old HTML, or the fix went into the desktop template and mobile uses another one. Send me your URL and the problem, and I reply with a few times. I check your field data first, then we spend one hour on your site, and within a day you have my notes in writing. €350 excl. VAT.

Send me your URL

No developer to build the fix? I do the work myself, on a copy of your site.

Arjen KarelCore Web Vitals still red on mobile?Send me your URL