Core Web Vitals simply explained: LCP, INP, CLS
Core Web Vitals are Google’s metrics for loading experience, interactivity, and visual stability of your website. What LCP, INP, and CLS mean, which thresholds apply, how you measure and improve them, and how important they really are for ranking.
Core Web Vitals are three metrics Google uses to judge the user experience of your website: how fast it loads, how fast it reacts to clicks, and how stable the layout stays while doing so. Since 2021 they feed into ranking, measured on real user data from Chrome.
This article explains the three metrics LCP, INP, and CLS with their current thresholds, shows you the tools to measure, the levers to improve, and honestly places how much ranking really depends on them. One thing up front: INP replaced the old FID in March 2024. If a guide still talks about FID, it is out of date.
Key takeaways
- Core Web Vitals are Google’s three metrics for loading experience (LCP), interactivity (INP), and visual stability (CLS) of a page.
- Good values: LCP under 2.5 seconds, INP under 200 milliseconds, CLS under 0.1. Measured at the 75th percentile of real users.
- INP replaced FID (First Input Delay) as the metric in March 2024. FID is obsolete.
- What counts for ranking is field data from real Chrome users (CrUX), not lab data from a single test.
- Core Web Vitals are one factor among many, often a tiebreaker between equally strong pages, not a magic bullet. The real gain is the better user experience.
What are Core Web Vitals?
Core Web Vitals are a set of three metrics Google uses to make the user experience of loading a web page measurable. They cover three areas: loading experience (how fast the main content becomes visible), interactivity (how fast the page reacts to an action), and visual stability (does the layout jump while loading). Google introduced them in 2021 and folded them into the Page Experience ranking factor.
The key point: these values are not guessed in a lab, they are collected from the behavior of real Chrome users. A page counts as good on a metric when 75 percent of all page loads fall under the threshold. So Google does not measure the ideal case but the experience of the broad mass of your visitors.
The three metrics: LCP, INP, CLS
Behind the abbreviations sit three clearly separated questions. LCP measures when the largest visible element has loaded, usually a hero image or a text block. INP measures how fast the page reacts to interactions like clicks and keyboard input, and it replaced the old FID in March 2024. CLS measures how much the layout shifts while loading, meaning whether a button jumps away as you try to click it.
Each metric has three zones: good, needs improvement, and poor. These thresholds apply currently:
Core Web Vitals and their thresholds
| Metric | Measures | Good | Needs improvement | Poor |
|---|---|---|---|---|
| LCP (Largest Contentful Paint) | Loading experience | ≤ 2.5 s | 2.5 s to 4 s | > 4 s |
| INP (Interaction to Next Paint) | Interactivity | ≤ 200 ms | 200 ms to 500 ms | > 500 ms |
| CLS (Cumulative Layout Shift) | Visual stability | ≤ 0.1 | 0.1 to 0.25 | > 0.25 |
How you measure them
When measuring there are two kinds of data, and the difference decides whether your result counts for ranking. Lab data comes from a simulated test under controlled conditions. It is ideal for debugging because it is reproducible. Field data comes from real Chrome users and is collected in the Chrome User Experience Report (CrUX). Only the field data feeds into ranking.
Three tools cover daily work. PageSpeed Insights is the best starting point: it shows field and lab data side by side, separated for mobile and desktop, plus concrete optimization suggestions. The Core Web Vitals report in Google Search Console groups all URLs of your site into good, needs improvement, and poor, and shows trends over time. Lighthouse in the Chrome DevTools delivers a deep technical audit for single pages.
A common mistake: looking only at the green lab score. PageSpeed Insights often shows 90+ in the lab while the field data is red. What counts is the experience of your real visitors, mostly on a smartphone.
How you improve them
The causes of poor values are known, and so are the levers. One point up front that most guides hide: the biggest lever is not a plugin but clean code and good infrastructure from the start. Every plugin, every third-party script, and every bloated page builder costs performance you then have to claw back the hard way.
For LCP the loading experience of the main image matters most. Optimize images and video (WebP or AVIF instead of JPEG, correct size, compression), deliberately skip lazy loading on the hero image, ensure fast server response times through good hosting and a CDN, and eliminate render-blocking CSS and JavaScript.
For INP it is about reaction time. Reduce heavy JavaScript that blocks the main thread, break up long tasks, and load third-party scripts like analytics and chat widgets with a delay. For CLS you reserve space: fixed dimensions for images, containers with fixed height for dynamic content, font-display swap for web fonts, and animations via transform instead of via layout properties.
Lazy loading belongs on everything below the viewport, but never on the LCP element itself. Exactly these details decide between green and yellow.
Measure the current state
Check your most important pages in PageSpeed Insights and read the field data in Search Console. That is your baseline.
Optimize images and video
WebP or AVIF, correct size, compression. Biggest lever for LCP and usually doable with little effort.
Slim down JavaScript
Remove unnecessary scripts and plugins, load third-party with a delay. That improves INP directly.
Stabilize the layout
Fixed image dimensions, reserved space for dynamic content, font-display swap. Brings CLS down.
Verify after 28 days
After a fix Search Console starts a 28-day window to validate the field data of real users.
How important are Core Web Vitals for ranking really?
Honesty pays off here, because the topic is often overblown. Core Web Vitals are a ranking factor, but one among more than two hundred. Google ranking depends first on relevance and authority. A perfectly fast page without matching content will not rank, and strong content with mediocre values can still sit at the top.
Where Core Web Vitals really count is the tiebreaker. In competitive niches, when two pages are level on content, the technically better one wins. And there is a second, often underrated effect: poor values hurt you through user signals. Slow, jittery pages lose visitors, and higher bounce rates push your position down further.
Bottom line: Core Web Vitals are no magic bullet for the top spot, but a technical entry ticket you should not give away. The real gain is not in the ranking signal but in the better experience that turns more visitors into customers.
Core Web Vitals in B2B
In B2B, user experience meets a demanding audience: decision-makers with little patience who subconsciously transfer the technical impression of a site onto the company. A jittery, slow website undermines trust before anyone has even read what you offer. This is exactly where it is decided whether your site feels professional.
Our approach starts one step earlier. We do not claw green values back through rework and plugin stacks, we build from the start so they are green: lean code, a clean image pipeline, no bloated page builder, good hosting, and a CDN as standard. One result of this approach is our enterprise website for FRAMEN, which sits in the green zone of the Core Web Vitals without us having to rescue anything afterward.
How that comes about technically and what makes a clean foundation is shown in our web development service.
Frequently asked questions
Core Web Vitals are Google’s three metrics for the user experience of a website: LCP for loading experience, INP for interactivity, and CLS for visual stability. They are measured on real Chrome users and have fed into ranking since 2021.
Good is an LCP under 2.5 seconds, an INP under 200 milliseconds, and a CLS under 0.1. These values must be reached for 75 percent of real users’ page loads for a metric to count as good.
INP (Interaction to Next Paint) replaced the old FID (First Input Delay) in March 2024. FID measured only the delay on the first interaction, INP judges the reaction time across all interactions during the whole visit. FID is therefore obsolete.
Easiest with PageSpeed Insights, which shows field and lab data separated for mobile and desktop. For an overview of all pages use the Core Web Vitals report in Google Search Console, for deep analysis of single pages Lighthouse in the Chrome DevTools.
Lab data comes from a simulated test under controlled conditions and is good for debugging. Field data comes from real Chrome users and is collected in the Chrome User Experience Report (CrUX). Only the field data feeds into ranking.
They are one factor among more than two hundred and mostly act as a tiebreaker: between pages equal on content, the technically better one wins. They do not replace relevance and authority but prevent losses from poor user signals and higher bounce rates.
More Articles
Let's talk about your project.
20-minute call, no sales pressure. You describe what you have in mind, we tell you if and how we can help.