Speed is not a vanity metric — it is a ranking input and a conversion lever at once. Core Web Vitals are Google’s three user-experience signals that quantify how fast a page feels, how quickly it responds, and how stable it looks while loading. Since Interaction to Next Paint replaced First Input Delay in 2024, the responsiveness bar has risen. This guide explains each metric, the exact thresholds you need to pass, and the highest-leverage fixes for real sites.

What Core Web Vitals Measure
Core Web Vitals are three field metrics: Largest Contentful Paint measures loading speed, Interaction to Next Paint measures responsiveness, and Cumulative Layout Shift measures visual stability. Together they approximate how a real user experiences a page loading and reacting, based on data from actual Chrome visitors.
Google built these metrics to replace vague notions of speed with measurable, user-centred signals. They are reported from the Chrome User Experience Report — real visits, not lab simulations — which is why a page can look fast on your laptop yet fail the vitals your users actually feel. Each metric captures a distinct moment: how long until the main content paints, how quickly the page answers a tap or click, and whether elements jump around during load.
They matter because they feed Google’s page experience signals and because they map directly to bounce and conversion. A page that passes all three keeps users longer and gives crawlers a cleaner render. They sit alongside deeper technical SEO work — vitals are the user-facing tip of a larger performance stack. You can see your scores in PageSpeed Insights.
The Thresholds That Pass
To pass, the 75th percentile of your visits must hit: LCP of 2.5 seconds or less, INP of 200 milliseconds or less, and CLS of 0.1 or less. Meeting the median is not enough — Google grades the experience of your slower quarter of visits, so tail performance decides the result.
The 75th-percentile rule is the detail most teams miss. Your average LCP can look healthy while the slowest 25% of visits — often mobile users on weaker networks — fail the threshold and drag the whole page into the “needs improvement” band. Optimise for that tail, not the mean — mobile visits especially, as covered in the mobile SEO guide.
Each metric has three bands. LCP: good at or under 2.5s, poor above 4s. INP: good at or under 200ms, poor above 500ms. CLS: good at or under 0.1, poor above 0.25. You need all three in the good band on both mobile and desktop to earn the full passing signal. Google’s web.dev vitals reference documents each threshold and how the field data is collected.
Fixing Each Metric
Improve LCP by optimising the hero image, server response, and render-blocking resources. Improve INP by breaking up long JavaScript tasks and deferring non-critical scripts. Improve CLS by setting explicit dimensions on images and embeds and reserving space for dynamic content before it loads.
For LCP, the usual culprit is the largest image or a slow server. Compress and correctly size the hero, serve modern formats, preload the LCP element, and cut render-blocking CSS and fonts. Faster server response — helped by caching and a CDN — shortens the whole chain, which ties into how your pages render.
For INP, the enemy is main-thread work. Long JavaScript tasks block the page from responding to taps; split them, defer third-party scripts, and remove unused code. For CLS, always declare width and height on images and ad slots, avoid inserting content above existing content, and load fonts without layout jumps. Prioritise by impact: fix the metric that is failing on the templates that get the most traffic first, then re-measure. This is core to a full SEO audit.
Monitoring and Ranking Impact
Core Web Vitals are a real but modest ranking factor — a tie-breaker among relevant results, not an override for content quality. Monitor field data continuously through Search Console and CrUX, because scores drift as you ship code and as traffic patterns shift across devices and regions.
Do not expect vitals to rocket a thin page to the top; relevance and topical authority still decide most rankings. Vitals act as a differentiator when several pages are otherwise close, and as a floor — a genuinely slow, unstable page gets suppressed. The bigger prize is often conversion: faster, steadier pages simply earn more.
Watch the Core Web Vitals report in Search Console for field trends, and use lab tools for debugging before release. Set a performance budget so regressions get caught in development rather than in production. Vitals are not a one-time fix; they are a metric you defend release after release, much like you would guard crawl budget on a large site. Pair monitoring with your content roadmap and home dashboard so performance stays visible.
- Core Web Vitals are three field metrics: LCP (loading), INP (responsiveness), and CLS (visual stability).
- Pass thresholds at the 75th percentile: LCP ≤ 2.5s, INP ≤ 200ms, CLS ≤ 0.1 — the slow tail decides the grade.
- Fix LCP via images and server speed, INP via lighter JavaScript, CLS via reserved space for media.
- Vitals are a modest tie-breaker ranking factor, not a substitute for relevance and authority.
- Monitor field data continuously and set a performance budget so regressions are caught before release.
Frequently Asked Questions
What replaced First Input Delay in Core Web Vitals?
Interaction to Next Paint (INP) replaced First Input Delay in March 2024. INP is stricter: instead of measuring only the delay before the first interaction, it assesses the latency of all interactions across the visit and reports a representative worst case. A passing INP is 200 milliseconds or less at the 75th percentile.
Do Core Web Vitals really affect Google rankings?
Yes, but modestly. They are part of Google’s page experience signals and act mainly as a tie-breaker between pages of similar relevance, and as a floor that suppresses genuinely slow, unstable pages. Strong vitals will not outrank clearly better content, but among close competitors they can decide which page wins.
Why does my page pass in the lab but fail in Search Console?
Lab tools test one simulated load on your hardware, while Search Console reports real Chrome visits at the 75th percentile. Your slower mobile users on weaker networks pull the field score down even when a lab test looks perfect. Always trust field data for the pass or fail decision.
How long do Core Web Vitals take to update after a fix?
Field data in the Chrome User Experience Report is based on a rolling 28-day window, so improvements appear gradually rather than instantly. Expect a few weeks for a fix to fully reflect in Search Console, and monitor lab metrics in the meantime to confirm the change is working before it shows in field data.
What is a good Cumulative Layout Shift score?
A CLS of 0.1 or less at the 75th percentile is good; above 0.25 is poor. CLS measures how much visible content shifts unexpectedly during load. Set explicit dimensions on images and embeds, reserve space for ads and dynamic content, and avoid inserting elements above existing content to keep the score low.
The Bottom Line
Core Web Vitals turn “fast enough” into three numbers you can manage. Pass LCP, INP, and CLS at the 75th percentile on mobile and desktop, fix the failing metric on your highest-traffic templates first, and defend the scores with a performance budget. They will not replace great content, but a fast, stable, responsive page earns more rankings and more conversions from the traffic you already have. Fold vitals into your broader technical SEO routine.
See how your site actually shows up in AI search. An AI visibility audit maps where you’re cited, where you’re invisible, and what to fix first — in plain English.
Get your AI visibility auditTry the free SEO tools →
Prefer self-serve? The interactive checklists turn guides like this one into a working to-do list.
Keep reading in SEO Fundamentals
Get one email when something genuinely changes
AI search moves fast and most of it is noise. We send one short email when a real shift is worth your time. Unsubscribe anytime.
Published by Plain Intelligence — practical AI SEO, GEO, and technical SEO, documented in plain English. About Plain Intelligence →
↑ Back to SEO Fundamentals · Explore all articles · Free tools & resources · Glossary