
Key takeaways
- Core Web Vitals are three user-centred measures: Largest Contentful Paint for loading, Interaction to Next Paint for responsiveness and Cumulative Layout Shift for stability.
- Google’s published good thresholds are 2.5 seconds for LCP, 200 milliseconds for INP and 0.1 for CLS, assessed for most real visits.
- Measure with field data first, then use lab tools to find causes: heavy images, slow servers, blocking scripts and layout jumps.
- Fix the biggest cause on your most important pages first, and re-measure after each change.
What Core Web Vitals are
Core Web Vitals are a set of metrics designed to describe how a page feels to real people. Instead of a single vague idea of speed, they measure three things users notice: how quickly the main content appears, how fast the page reacts when they tap or type, and whether things jump around while loading. They matter for the people using your site first. They are also part of the page experience signals that search engines consider, though good content and relevance matter more than a perfect score.
The three metrics
| Metric | What it measures | Good threshold |
|---|---|---|
| LCP, Largest Contentful Paint | How long the largest visible element, often a hero image or heading, takes to render | 2.5 seconds or less |
| INP, Interaction to Next Paint | How quickly the page responds visually to taps, clicks and key presses across a visit | 200 milliseconds or less |
| CLS, Cumulative Layout Shift | How much visible content moves unexpectedly while the page loads | 0.1 or less |
These thresholds are published by Google and are assessed at the 75th percentile of real page loads, so most of your visitors, not just the best cases, should meet them. Check the current definitions on web.dev, because the metrics have evolved over time.
How to measure
- Field data shows what real users experience. Look at the Core Web Vitals report in Search Console and PageSpeed Insights, which reports real-user data when available.
- Lab data helps you debug. Lighthouse and the browser’s performance panel reproduce a page load and point to causes.
- Test on a mid-range phone and a throttled connection, not only on a fast laptop.
- Measure your most important pages separately: home, key landing pages, product and checkout pages.
Fixing LCP
- Serve images in modern formats at the right size, and do not lazy-load the main hero image.
- Reduce server response time with caching, efficient queries and a nearby host or CDN.
- Remove or defer scripts and styles that block rendering.
- Preload the key font and hero image, and avoid chains of redirects.
Fixing INP
- Break up long JavaScript tasks so the page can respond between them.
- Load third-party scripts, such as chat widgets and trackers, late or only where needed.
- Keep handlers for taps and clicks light, and move heavy work off the main thread.
- Avoid huge page structures and unnecessary re-rendering in interactive screens.
Fixing CLS
- Set width and height or an aspect ratio on images, videos and embeds so space is reserved.
- Reserve space for banners, ads and cookie notices instead of pushing content down late.
- Load fonts in a way that avoids large jumps, and match fallback font metrics.
- Do not insert content above existing content after the page has loaded.
A worked example
A service business finds that its home page passes on desktop but has a slow LCP on phones. The cause is a large unoptimised hero image and a render-blocking script from a chat widget. The team serves a properly sized image in a modern format, preloads it, loads the chat widget after the page is interactive and reserves space for the cookie banner, which had been shifting the layout. They re-test on a mid-range phone, then watch field data for a few weeks to confirm the improvement. This is an illustrative scenario, not a client story, but these three fixes cover many slow pages.
Keeping it fast
- Set a performance budget for page weight and script size, and check it before releases.
- Test new features, widgets and tracking scripts before adding them.
- Review the vitals report monthly and after big changes.
- Treat speed as part of design: the lightest page is the one that never loads what it does not need.
Next step
Speed supports search visibility, so pair this with our technical SEO checklist. Build performance in from the start with web development, see bilingual website SEO, or contact us for a performance review.
Frequently asked questions
What are good Core Web Vitals scores?
Google’s published good thresholds are an LCP of 2.5 seconds or less, an INP of 200 milliseconds or less and a CLS of 0.1 or less, measured for most real visits. Check web.dev for the current definitions.
Do Core Web Vitals affect rankings?
They are part of page experience signals, but content quality and relevance matter more. Good vitals help users and remove a possible disadvantage rather than guaranteeing rankings.
Why is my score different in different tools?
Field data reflects real users over time, while lab tools simulate one load under set conditions. Use field data to know whether there is a problem and lab data to find the cause.

