
What Are Core Web Vitals? A Practical Guide to LCP, INP and CLS
Core Web Vitals are three metrics Google uses to measure real-world page experience: Largest Contentful Paint (LCP) for loading speed, Interaction to Next Paint (INP) for responsiveness and Cumulative Layout Shift (CLS) for visual stability. A good score is LCP within 2.5 seconds, INP of 200 milliseconds or less and CLS of 0.1 or less.
Everyone has landed on a page that loads slowly, freezes when you tap a button or jumps around just as you try to click something. Core Web Vitals turn those frustrations into numbers. This guide explains what each metric measures, what counts as a good score, how Google evaluates your site and how to fix the most common problems.
What are Core Web Vitals?
Core Web Vitals are a small set of metrics from Google’s wider Web Vitals initiative. They focus on three parts of the user experience: how fast the main content appears, how quickly the page responds to input and how stable the layout stays while it loads.
They’re also one part of Google’s broader page experience signals, which look at the overall experience of using a page. Google has said the set of metrics will evolve over time, so it’s worth checking the official documentation now and then.
The three Core Web Vitals explained
Largest Contentful Paint (LCP): how fast the main content loads
LCP measures how long it takes for the largest visible element, usually a hero image, a large heading or a block of text, to render after the page starts loading. It’s a good stand-in for “when does this page feel loaded?”
- Good: 2.5 seconds or less
- Needs improvement: 2.5 to 4 seconds
- Poor: over 4 seconds
Interaction to Next Paint (INP): how quickly the page responds
INP measures how fast a page visibly responds when someone clicks, taps or presses a key. It looks at interactions across the whole visit, not just the first one. It replaced First Input Delay (FID) in March 2024 and is often the hardest metric for modern, script-heavy sites to pass.
- Good: 200 milliseconds or less
- Needs improvement: 200 to 500 milliseconds
- Poor: over 500 milliseconds
Cumulative Layout Shift (CLS): how stable the layout is
CLS measures unexpected movement of page elements while the page loads, such as a button shifting down because an ad or image appeared above it. It has no unit. It’s a score based on how much of the screen moved and how far.
- Good: 0.1 or less
- Needs improvement: 0.1 to 0.25
- Poor: over 0.25
How does Google evaluate Core Web Vitals?
Two details matter here, First, Google uses the 75th percentile. A page passes when at least 75% of visits meet the “good” threshold for each metric, segmented by mobile and desktop. You can’t hide behind a fast average if a quarter of your visitors have a slow experience.
Second, it relies on field data. This is real-world data from Chrome users, collected in the Chrome User Experience Report (CrUX), not a one-off test on your own computer. That’s why your score in a lab tool can differ from what Google sees. Mobile results are also usually worse than desktop for the same page.
Do Core Web Vitals affect SEO rankings?
Yes, but modestly. Core Web Vitals are part of Google’s page experience signals. Content relevance and quality remain far more important, and a fast page with weak content won’t outrank a strong, relevant one. Think of Core Web Vitals as a quality bar to clear. When two pages are otherwise similar, a better experience can tip the balance.
The benefits go beyond rankings. Faster, steadier pages tend to keep visitors engaged and help conversions, so the business case holds up even if you ignore the ranking effect.
How to measure Core Web Vitals
Use both field and lab tools.
- Google Search Console: the Core Web Vitals report groups your URLs into good, needs improvement and poor using real-user data.
- PageSpeed Insights: shows field data from real users where available, plus a lab diagnosis with suggestions for each URL.
- Lighthouse (in Chrome DevTools): a lab test that’s useful for debugging changes before you publish them.
- Chrome User Experience Report: the underlying public dataset, useful for tracking trends.
- Real user monitoring: tools that collect performance data from your own visitors give the most detailed picture.
Field data tells you whether there’s a problem. Lab data helps you work out why.
How to improve LCP?
- Optimize the largest element. Compress images, use modern formats like WebP or AVIF and size them correctly.
- Don’t lazy-load your hero image. Load it early and consider giving it high fetch priority.
- Cut server response time. Use caching, a content delivery network (CDN) and good hosting.
- Remove render-blocking resources. Defer non-critical CSS and JavaScript.
- Preload key assets such as the main font or hero image.
How to improve INP
- Break up long tasks. Heavy JavaScript that blocks the main thread makes pages feel frozen.
- Reduce and defer third-party scripts like chat widgets, trackers and ad tags.
- Keep the page’s HTML (DOM) lean. Very large pages are slower to update.
- Make interactions lightweight. Do the minimum work needed to show a visual response, then handle the rest in the background.
- Test on real mid-range phones, not just fast laptops.
How to improve CLS
- Set width and height (or aspect ratio) on images, videos and embeds so the browser reserves space.
- Reserve space for ads and banners instead of inserting them above existing content.
- Avoid injecting content above what people are reading, unless it follows a user action.
- Load fonts carefully to prevent text from jumping when a custom font swaps in.
- Use transform animations instead of ones that change layout.
Common Core Web Vitals mistakes
- Testing only on a fast desktop. Most users, and most failures, are on mobile.
- Trusting one lab score. A perfect Lighthouse run doesn’t guarantee good field data.
- Piling on plugins and scripts. Each one adds weight and can hurt INP.
- Ignoring image sizes. Oversized images are one of the most common causes of slow LCP.
- Fixing once and forgetting. New features, ads and content can undo your gains.
- Chasing perfect scores. Aim to pass the thresholds, then prioritize content quality.
Frequently asked questions
What are Core Web Vitals?
They’re three Google metrics, LCP, INP and CLS, measuring loading speed, responsiveness and visual stability on real user visits.
What is a good LCP score?
A good LCP is 2.5 seconds or less, measured at the 75th percentile of real page loads.
What replaced First Input Delay?
Interaction to Next Paint, or INP, replaced First Input Delay as a Core Web Vital in March 2024.
What is a good INP score?
A good INP is 200 milliseconds or less, meaning the page responds quickly to clicks, taps and key presses.
What is a good CLS score?
A good CLS is 0.1 or less, which means the page layout stays stable while loading.
Are Core Web Vitals a ranking factor?
Yes, as part of page experience signals, but content relevance and quality usually matter more than speed alone.
How do I check my Core Web Vitals?
Use the Core Web Vitals report in Google Search Console and PageSpeed Insights, which show real-user field data.
Written by
Adit Jindal
Founder
Adit Jindal is the founder of Auzork and CEO of Callidora Technology. He specializes in enterprise software development and generative engine optimization.


