Quick answer
- LCP measures loading, INP measures responsiveness and CLS measures visual stability.
- Good thresholds are LCP at 2.5 seconds or less, INP at 200 milliseconds or less and CLS at 0.1 or less.
- Field data from real users matters more than a single lab score.
- Core Web Vitals are one ranking signal among many, but they strongly affect user experience and conversion.
What Core Web Vitals are
Google’s Core Web Vitals are a set of metrics that capture how real visitors experience a page. They are part of Google’s page experience signals, and they are measured from real Chrome users where enough data exists. If you are asking what are Core Web Vitals in practice, think of them as three questions: does the page load fast, does it respond when I tap, and does it stay still while I read?
They matter for two reasons. Google uses them as one of many ranking inputs, and slow or unstable pages simply convert less. Improving them is good for SEO and for business.
The three metrics and their thresholds
Each metric has a “good” threshold, measured at the 75th percentile of visits.
| Metric | Measures | Good | Poor |
|---|---|---|---|
| LCP, Largest Contentful Paint | Time for the largest visible element to load | 2.5 seconds or less | Over 4 seconds |
| INP, Interaction to Next Paint | Responsiveness to taps, clicks and key presses | 200 ms or less | Over 500 ms |
| CLS, Cumulative Layout Shift | Unexpected movement of page elements | 0.1 or less | Over 0.25 |
Field data vs lab data
Lab tools such as Lighthouse simulate a page load under controlled conditions and are ideal for debugging. Field data comes from real users and is what Google uses for assessment, shown in Search Console’s Core Web Vitals report and the Chrome UX Report. The two can differ because real devices, networks and behaviour vary.
Use lab tests to find and verify fixes, but judge success by field data over time. A core web vitals test using PageSpeed Insights shows both.
How to improve LCP
LCP is usually dominated by the hero image or main heading block.
- Serve properly sized, compressed images in modern formats such as WebP or AVIF
- Preload the LCP image and avoid lazy-loading it
- Reduce server response time and use caching
- Remove render-blocking CSS and JavaScript from the critical path
- Self-host and preload key fonts with sensible font-display settings
How to improve INP and CLS
INP problems usually come from heavy JavaScript that blocks the main thread. Reduce third-party scripts, split long tasks, defer non-essential code and avoid heavy event handlers. For CLS, always set width and height on images and embeds, reserve space for ads and banners, avoid inserting content above existing content and use font fallbacks with similar metrics.
Many fixes are template-level, which means a single change can improve thousands of pages.
Prioritising Core Web Vitals work for a business site
Do not chase a perfect score at the expense of other priorities. Start with templates that carry the most traffic and conversions, such as the homepage, service pages and category pages. Check whether pages already pass in field data, and focus on those that fail. A fast, simple site often needs far less work than a heavy one built with large page builders and many plugins. Our JavaScript SEO guide covers one of the usual causes.
Core Web Vitals for SEO: ranking, thresholds and audits
Is Core Web Vitals SEO a big lever? As a core web vitals ranking factor it is modest, because relevance and quality usually outweigh it, but Google Core Web Vitals data also affects user experience, which affects conversion. The Google Core Web Vitals LCP threshold for “good” is 2.5 seconds at the 75th percentile of visits, as in the table above.
To improve Core Web Vitals, start with a core web vitals audit of your top templates, then work through the fixes in order of effect. A core web vitals improvement plan should list each fix, owner and expected metric change. Core Web Vitals optimisation is often cheaper than expected, because a handful of heavy images and scripts cause most problems.
Tools and a practical testing routine
Use PageSpeed Insights for a quick view of field and lab data, the Core Web Vitals report in Search Console for groups of URLs, and Lighthouse in Chrome for debugging. Test your top five templates on mobile first. Record results before changes, make one fix at a time where possible and test again. Field data updates over a rolling 28-day window, so allow several weeks before judging whether an improvement has registered.
Treat the numbers as guides. A page that loads quickly and feels stable to real visitors is better than one that scores perfectly in a lab but frustrates users.
Core Web Vitals optimisation help
If your developers need clear instructions, our technical SEO consultant service turns test results into tickets with acceptance criteria. A Core Web Vitals review is also part of every SEO audit. For the whole picture of what we offer, read about our SEO consultant London consultancy, and for how we check fixes see our SEO consulting process.
Frequently asked questions
What are Core Web Vitals?
They are Google’s metrics for real-world page experience: LCP for loading, INP for responsiveness and CLS for visual stability.
What is a good LCP score?
An LCP of 2.5 seconds or less at the 75th percentile of visits is considered good.
Are Core Web Vitals a ranking factor?
They are part of Google’s page experience signals, but content relevance and quality remain more important. They also affect conversion.
Why does PageSpeed Insights show different numbers over time?
Lab results vary by conditions, and field data reflects a rolling 28-day window of real users.
Did INP replace FID?
Yes. Interaction to Next Paint replaced First Input Delay as a Core Web Vital in March 2024.
Talk to an SEO consultant
Questions about this topic or your own site? Send a few details and you will get a clear, practical reply.