Core Web Vitals are Google's three metrics for real-world user 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, for at least 75% of visits, LCP is within 2.5 seconds, INP within 200 milliseconds and CLS under 0.1. Here's what each metric means, how to measure it and how to fix common problems.
The three metrics
| Metric | Measures | Good | Needs improvement | Poor |
|---|---|---|---|---|
| LCP (Largest Contentful Paint) | When the main content appears | ≤ 2.5 s | 2.5–4 s | > 4 s |
| INP (Interaction to Next Paint) | How quickly the page responds to clicks, taps and typing | ≤ 200 ms | 200–500 ms | > 500 ms |
| CLS (Cumulative Layout Shift) | How much content jumps around while loading | ≤ 0.1 | 0.1–0.25 | > 0.25 |
INP replaced First Input Delay (FID) as a Core Web Vital in March 2024, because it measures responsiveness across the whole visit, not just the first interaction.
Field data vs lab data
- Field data comes from real Chrome users (the Chrome User Experience Report). This is what Google uses for Core Web Vitals assessments.
- Lab data comes from a simulated test (Lighthouse). Useful for debugging, but it can differ from real-world results.
Where to look:
| Tool | Data | Best for |
|---|---|---|
| Search Console Core Web Vitals report | Field | Site-wide status by URL group. See Search Console guide |
| PageSpeed Insights | Field + lab | Diagnosing individual URLs |
| Chrome DevTools (Performance panel) | Lab | Finding the exact cause |
How to fix LCP (slow loading)
The LCP element is usually a hero image, a large heading or a video poster.
- Speed up the server: caching, a CDN, and fast hosting reduce time to first byte.
- Optimise the LCP image: compress it, use WebP/AVIF, serve the right size with
srcset. - Load it early: don't lazy-load the hero image; add
fetchpriority="high"or preload it. - Remove render-blocking resources: defer non-critical JavaScript, inline critical CSS.
- Render on the server: content that depends on client-side JavaScript appears later. See JavaScript rendering.
How to fix INP (slow interactions)
INP suffers when the main thread is busy running JavaScript.
- Reduce JavaScript: remove unused code and heavy third-party scripts (chat widgets, trackers, A/B tools).
- Break up long tasks so the browser can respond between them.
- Defer non-urgent work until after the interaction updates the screen.
- Avoid large DOM updates in response to clicks.
- Load third-party scripts after the page becomes interactive.
How to fix CLS (layout shifts)
- Set width and height (or aspect-ratio) on images, videos and iframes.
- Reserve space for ads, embeds and banners.
- Avoid inserting content above existing content after load (cookie banners, promos).
- Use
font-displaywisely and preload key fonts to reduce text reflow. - Animate with transforms, not properties that change layout.
Prioritising fixes
- Open the Core Web Vitals report in Search Console and start with mobile.
- Fix issues affecting URL groups (templates) rather than single pages; one template fix can improve thousands of URLs.
- Start with the metric marked Poor on the most important templates (product, category, blog).
- Validate the fix in Search Console; field data updates over about 28 days.
Do Core Web Vitals affect SEO?
They're part of Google's page experience signals. Google has been clear that great content relevant to the query matters more, but page experience can help when results are otherwise similar. The bigger impact is on users: faster, stable pages keep visitors and convert better.
Core Web Vitals and AI search
AI assistants often fetch pages live while a user waits for an answer. Slow, script-heavy pages risk timing out or being skipped, and content that only appears after JavaScript runs may not be read at all. Fast, server-rendered pages help both Google rankings and AI citations. See page speed for AI fetchers.
Quick checklist
- Search Console shows Good for most mobile URLs
- Hero images compressed, correctly sized and not lazy-loaded
- Caching and CDN in place
- Unused and third-party JavaScript reduced or deferred
- Images, embeds and ads have reserved space
- Fonts preloaded with a sensible
font-display - Re-check after every major release
For the full technical list, see the SEO checklist.
The bottom line
Core Web Vitals measure what users feel: how fast the page loads, how quickly it responds and whether it stays still. Hit LCP ≤ 2.5 s, INP ≤ 200 ms and CLS ≤ 0.1 for most visits, fix templates rather than single pages, and you'll improve rankings potential, conversions and how reliably AI systems can read your site.
