Key takeaways
- Good Core Web Vitals mean LCP under 2.5 seconds, INP under 200 milliseconds and CLS under 0.1.
- Measure field data at the 75th percentile with PageSpeed Insights and Search Console.
- Compressing images, better hosting, smarter font loading and layout stability fix most failures.
The short answer
The answer to what is a good Core Web Vitals score is a set of three thresholds met at once: Largest Contentful Paint under 2.5 seconds, Interaction to Next Paint under 200 milliseconds and Cumulative Layout Shift under 0.1, each measured at the 75th percentile of real mobile visits. Pass two metrics and fail one, and the page still rates as needing improvement rather than good, both in Search Console and in PageSpeed Insights. Meeting the bars matters because they describe the experience of real users, and pages that fail them tend to lose conversions first and visibility soon after. Think of them as a set: a page that loads fast but jumps around, or responds slowly once loaded, still fails.
The three Core Web Vitals and their thresholds
Largest Contentful Paint, or LCP, measures loading: how quickly the largest visible element, usually a hero image or headline, appears. Good is 2.5 seconds or better; over 4 seconds is poor. Interaction to Next Paint, INP, measures responsiveness: how quickly the page reacts to clicks, taps and key presses across the whole visit. Good is 200 milliseconds or better; over 500 is poor. Cumulative Layout Shift, CLS, measures visual stability: how much the page moves while loading and while you read it. Good is 0.1 or less.
Two practical notes. INP replaced First Input Delay as the third metric in March 2024, so older articles describing FID are out of date. And the assessment is based on field data from real Chrome users, grouped at the 75th percentile, so your own fast office connection does not get a vote. A score is never finished; it only holds until the next release. Poor, incidentally, is a rating rather than a punishment: plenty of excellent sites sit in the middle band while they work through their backlog.
How to measure your Core Web Vitals score
PageSpeed Insights is the fastest starting point: enter a URL and it returns both lab results from Lighthouse and real user field data from the Chrome User Experience Report, with the Core Web Vitals assessment shown clearly. Search Console adds the site wide view, grouping pages into good, needs improvement and poor per metric, which tells you whether the problem is one template or the whole site. Both views matter; neither alone is enough.
Read field data as the truth and lab data as the diagnostic. Field data says what real visitors experienced over the past 28 days; lab data reproduces one visit so you can debug it. Before you start tuning, work through a technical SEO checklist so performance fixes land alongside indexing, crawl and structured data basics rather than in isolation, and retest after each change rather than at the end. If traffic is low, field data may be thin for some pages, so lean on lab tests and on the templates that carry the most sessions. Save each report so progress stays provable.
Fixing LCP: images, hosting and font loading
Most failing LCP scores trace back to images and hosting. Compress every hero image, serve it in WebP at the size it is actually displayed and preload the one the page opens with; lazy loading the main hero, a common default, delays exactly the element LCP watches. Beyond images, look at time to first byte: cheap shared hosting and no caching push every metric down. Better hosting, server level caching and a content delivery network usually improve LCP more than any plugin tweak.
Fonts are the third frequent culprit. Self hosting one or two weights, preloading them and using a swap display strategy avoids invisible text without late layout jumps. Finally, audit third party scripts: chat widgets, tag containers and old plugins each add work before the page can paint, and outdated components drag security down at the same time, which our guide to website security Spain covers in depth. Remove what you do not use; every script you delete is free speed. Measure before and after; unplanned speed work always feels faster than it is.
Layout stability and responsiveness: CLS and INP
CLS failures come from elements that arrive late without reserved space: images without width and height attributes, banners injected above content, web fonts swapping in a different size. Set explicit dimensions on every image and video, reserve space for ads and embeds, and avoid inserting content into the middle of an existing page. A page that never jumps feels trustworthy, which is exactly the impression shifting pages destroy. Small, stable layouts also read as professional, and that impression shows up in every metric that follows.
INP failures come from the main thread being busy. Break up long JavaScript tasks, defer scripts that are not needed for the first interaction, and test on a mid range phone, because that is where the 75th percentile of your visitors probably sits. Responsiveness work overlaps heavily with inclusive design: generous tap targets, visible focus states and keyboard support all help, and our guide to website accessibility Spain explains that side properly. Both metrics reward simplicity more than cleverness.
Keeping scores green through redesigns and migrations
Scores drift. A new tag manager rule, a seasonal banner or an upgraded theme can quietly push a good page into needs improvement within weeks, so put Core Web Vitals on the same monthly review as analytics and rankings, and retest after every significant release. Schedule the review; good intentions do not retest themselves.
Big changes are where scores are won or lost. When replatforming, carry performance budgets into the new build and test templates on staging before the domain switch; our guide to website migration Spain covers the SEO side of that move. And if a rebuild is on the table, start from performance rather than patching it afterwards: our guide to SEO website development Spain treats speed as a requirement from the first sprint, which is far cheaper than rescuing a finished site one metric at a time. Between releases, a lightweight alert on the field data report catches regressions within days instead of months. The goal is not a perfect number; it is a site that stays comfortably inside the thresholds.
Frequently asked questions
What is a good Core Web Vitals score for mobile?
The thresholds are the same on mobile and desktop: LCP under 2.5 seconds, INP under 200 milliseconds and CLS under 0.1, all at the 75th percentile of real visits. In practice mobile is harder, because slower processors and networks expose heavy images, long scripts and unstable layouts that desktop hides. Optimise for mobile field data and desktop usually follows.
Do Core Web Vitals affect Google rankings?
They are a confirmed ranking signal, used as part of the page experience systems, and they matter most between pages of similar relevance. Treat them as a tiebreaker plus a conversion lever: faster, stabler pages convert better regardless of rankings. Fix them because users benefit first, and the ranking effect follows from real behaviour.
How long does it take to improve a failing score?
Small sites often see field data move within two to four weeks of a fix, because the score rolls over a 28 day window. Larger sites with many templates can take a couple of months, since each template needs its own pass. Expect quick wins from images, caching and font handling first, then slower work on JavaScript and layout stability.
Why did my Core Web Vitals score drop suddenly?
Common causes include a new tag or chat widget, a heavier theme update, larger hero images, a hosting change or traffic mix shifting toward slower devices. Check what changed in the weeks before the drop, compare templates in Search Console and run lab tests on the affected pages. Roll back what you can, fix the rest, and the 28 day window will wash the damage out.








