Quick answer: Core Web Vitals are three Google metrics for real-user page experience: Largest Contentful Paint (LCP) for loading, Interaction to Next Paint (INP) for responsiveness, and Cumulative Layout Shift (CLS) for visual stability. A page passes when at least 75% of visits meet these thresholds: LCP of 2.5 seconds or less, INP of 200 milliseconds or less, and CLS of 0.1 or less. INP replaced First Input Delay in March 2024.
Core Web Vitals get more attention than almost any other technical SEO topic, and more confusion. Some site owners chase a perfect PageSpeed score that has little to do with rankings. Others ignore speed completely while their mobile visitors leave before the page appears. The truth sits in between.
The three Core Web Vitals and their thresholds
| Metric | Measures | Good | Needs improvement | Poor |
|---|---|---|---|---|
| Largest Contentful Paint (LCP) | When the main content becomes visible | 2.5 s or less | 2.5 to 4 s | Over 4 s |
| Interaction to Next Paint (INP) | How quickly the page responds to taps, clicks and key presses | 200 ms or less | 200 to 500 ms | Over 500 ms |
| Cumulative Layout Shift (CLS) | How much content jumps around while loading | 0.1 or less | 0.1 to 0.25 | Over 0.25 |
Google assesses each metric at the 75th percentile of real visits, split by mobile and desktop. That means one fast test on your office Wi-Fi proves very little. What counts is how the page performs for your actual visitors on their actual devices.
Do Core Web Vitals affect rankings?
Yes, but modestly. Google says Core Web Vitals are used by its ranking systems, and it also says that good page experience does not override relevance: great content on a slower page can still outrank a fast page with weaker content. In my experience, fixing Core Web Vitals rarely produces a ranking jump on its own. It does reduce bounce rates, increase conversions and remove a tiebreaker against you in competitive results.
Lab data vs field data
- Field data comes from real Chrome users through the Chrome UX Report. This is what Google uses for assessment. You see it in Search Console’s Core Web Vitals report and at the top of PageSpeed Insights.
- Lab data comes from a simulated test, such as Lighthouse. It is useful for debugging but is not what Google uses to assess your pages.
Low-traffic pages may not have enough field data. In that case Search Console groups similar URLs, and lab tests become your main guide.
How to improve LCP
- Find the LCP element. PageSpeed Insights tells you which element it is, often a hero image or heading.
- Do not lazy-load the hero image. Load it immediately and give it high fetch priority.
- Compress and resize images and serve modern formats such as WebP or AVIF.
- Reduce server response time with page caching and good hosting.
- Remove render-blocking CSS and JavaScript that delays the first paint.
How to improve INP
- Cut heavy JavaScript, especially third-party scripts such as chat widgets, tag managers loaded with unused tags, and multiple analytics tools.
- Break up long tasks so the browser can respond to input between them.
- Delay non-essential scripts until after the page is interactive.
- Watch page builders and sliders, which often add large scripts to every page.
How to improve CLS
- Set width and height on images and videos so the browser reserves space.
- Reserve space for ads, embeds and cookie banners.
- Load web fonts carefully to avoid text jumping when the font swaps.
- Avoid inserting content above existing content after the page loads.
Where to check your Core Web Vitals
- Search Console Core Web Vitals report: groups of URLs that pass or fail, by device.
- PageSpeed Insights: field data for a URL or origin, plus lab diagnostics.
- Chrome DevTools Performance panel: for deeper debugging of INP problems.
Prioritize by template, not by page
Most problems come from templates: the product template, the blog template, the location page template. Fixing one template fixes hundreds of URLs. This is how I approach it in a technical SEO audit, and it is why product page SEO on large catalogs often starts with performance.
If Core Web Vitals are failing across your site and you are not sure where to start, my technical SEO service covers diagnosis and working with your developers on fixes.
Frequently asked questions
Is a PageSpeed score of 100 necessary?
No. The score is a lab measure. Passing Core Web Vitals in field data is what matters for Google’s assessment.
What replaced First Input Delay?
Interaction to Next Paint replaced First Input Delay as a Core Web Vital in March 2024. INP measures responsiveness across all interactions, not just the first one.
How long until Search Console shows improvements?
Field data is based on a rolling 28-day window, so expect around four weeks before fixes show fully in the report.
Do Core Web Vitals matter for AI Overviews?
Google says AI features rely on its core ranking and quality systems, so the same page experience signals apply. Fast, stable pages also keep the visitors who click through from AI answers.
Sources: Google Search Central: Understanding Core Web Vitals and Google search results; web.dev: Web Vitals; web.dev: INP becomes a Core Web Vital.
