Core Web Vitals are three metrics defined by Google to measure the aspects of user experience that matter most: how fast the main content loads, how quickly the page responds to user input, and how stable the layout remains as assets arrive. Since 2021, they have been an official ranking factor in Google Search.
This article gives you a clear explanation of each metric, the thresholds that separate "good" from "poor," and the free tools you can use to measure and improve your scores starting today.
Why Google Created Core Web Vitals
Google has measured web speed for years, but traditional technical metrics — TTFB, total load time — don't always reflect what users actually experience. A site can "load" in one second according to server logs while still showing a blank screen to a real user for three seconds.
Core Web Vitals were designed to center measurement on human perception: Does the content appear quickly? Does the page respond when I click? Does the text jump around while I'm trying to read it?
By making them a ranking factor, Google aligns webmaster incentives with the experience of real users. A site that ranks well must also be a site that's pleasant to use.
The Three Metrics: LCP, INP, and CLS
LCP — Largest Contentful Paint
LCP measures the time from when the user initiates navigation to when the largest content element — typically a hero image or the main text block — is fully visible on screen.
It's the most representative metric for perceived load speed: if the LCP is fast, the user feels the page is already there.
| Rating | LCP Value |
|---|---|
| Good | ≤ 2.5 seconds |
| Needs improvement | 2.5 – 4.0 seconds |
| Poor | > 4.0 seconds |
Common causes of poor LCP: uncompressed or non-preloaded images, slow server (high TTFB), render-blocking CSS that delays painting.
INP — Interaction to Next Paint
INP — which in March 2024 permanently replaced the older FID metric — measures the overall responsiveness of a page. It logs every user interaction (clicks, taps, key presses) throughout the visit and reports the 98th percentile latency: the worst-case delay that most users experience.
| Rating | INP Value |
|---|---|
| Good | ≤ 200 milliseconds |
| Needs improvement | 200 – 500 milliseconds |
| Poor | > 500 milliseconds |
Common causes of poor INP: heavy JavaScript blocking the main thread, long tasks that prevent the browser from processing user events, frameworks with expensive hydration.
CLS — Cumulative Layout Shift
CLS measures how much visible elements unexpectedly shift while the page finishes loading. We've all been there: you're about to click a button, an ad loads above it, and you end up tapping the wrong thing. That's high CLS.
| Rating | CLS Value |
|---|---|
| Good | ≤ 0.1 |
| Needs improvement | 0.1 – 0.25 |
| Poor | > 0.25 |
Common causes of poor CLS: images without explicit width and height attributes, ads or embeds injected dynamically after page load, web fonts that swap and reflow text (FOUT/FOIT).
Lab Data vs. Field Data
This point trips up a lot of people: you might see different scores depending on which tool you use. That's because there are two distinct data types:
- Lab data: controlled simulations run by tools like Lighthouse or PageSpeed Insights from a standardized environment. Reproducible and useful during development, but they don't capture the diversity of real devices and connections.
- Field data (CrUX): real measurements from anonymous users who visited your site. Google collects these in the Chrome User Experience Report (CrUX) and surfaces them in PageSpeed Insights and Search Console. This is the data Google uses for ranking.
A brand-new site with no traffic won't have field data yet. In that case, lab data is the best available proxy.
How to Measure Your Core Web Vitals
These free tools provide actionable insight:
Google PageSpeed Insights
Enter any URL at pagespeed.web.dev and you'll receive field data (where available) plus lab data with specific recommendations ranked by impact. It's the recommended starting point.
Google Search Console — Page Experience Report
If your site is verified in Search Console, the Page Experience report groups your URLs by status (Good / Needs Improvement / Poor) and shows trends over time. This is the most strategic view: it tells you which pages to prioritize.
Chrome DevTools (Lighthouse)
Open DevTools (F12), go to the Lighthouse tab, and run an audit. Ideal during development so you can iterate without waiting for external data to refresh.
Web Vitals Chrome Extension
Google's official Chrome extension shows Core Web Vitals for any page in real time as you browse. Perfect for quick spot checks without running a full audit.
For a broader look at the performance metrics ecosystem and how they interconnect, browse our web performance article archive.
The Highest-Impact Fixes by Metric
To improve LCP
- Use
<link rel="preload">for the main hero image so the browser fetches it immediately. - Convert images to WebP and compress them without perceptible quality loss.
- Improve TTFB by choosing faster hosting or activating a CDN.
- Eliminate render-blocking CSS or load it asynchronously.
To improve INP
- Break up long JavaScript tasks into smaller chunks using
setTimeoutor thescheduler.yield()API. - Audit and remove unnecessary third-party scripts (live chat, tracking pixels, social widgets).
- Move heavy processing off the main thread using
web workers.
To improve CLS
- Always declare
widthandheighton every<img>and<video>tag. - Reserve space for ads and embeds before they load using CSS aspect-ratio boxes.
- Use
font-display: optionalorswapto prevent typographic layout shifts.
If you'd rather have a specialist team identify and fix your Core Web Vitals issues, elenlace.com offers technical audits with a detailed, prioritized action plan.
Key Takeaways
- Core Web Vitals are three official Google metrics: LCP (loading), INP (interactivity), and CLS (visual stability).
- They've been a Google Search ranking factor since 2021; INP replaced FID in March 2024.
- For ranking purposes, Google uses field data from real users — not lab simulations.
- PageSpeed Insights and Search Console are the reference tools for measuring and monitoring.
- LCP improves with optimized images and fast hosting; INP with less blocking JavaScript; CLS with declared media dimensions.
- Better Core Web Vitals help SEO and also reduce bounce rates and improve conversions.
Are your Core Web Vitals in the red? The team at elenlace.com can run a full audit of your site and deliver a prioritized improvement plan so you can reach "Good" as quickly as possible.
FAQ
Are Core Web Vitals the only page experience signal in Google?
No. Google's Page Experience update also includes mobile-friendliness, absence of intrusive interstitials, and safe browsing (HTTPS). That said, Core Web Vitals carry the most weight and are the most actionable through technical optimizations.
How often does Google update Core Web Vitals data?
The Chrome User Experience Report (CrUX) updates monthly. Google Search Console displays a rolling 28-day window. This means changes you make today won't be reflected in rankings immediately — expect 4 to 6 weeks before you can reliably evaluate the impact of an optimization.
Can a site with no field data (CrUX) be penalized in rankings?
If there isn't enough field data for a specific URL, Google falls back to data from the URL group or the whole domain. A site without CrUX data doesn't receive an explicit penalty, but it also doesn't benefit from positive signals. Generating real traffic is the only way to build a field data record.
Is INP harder to fix than the old FID metric?
Generally yes. FID only measured the latency of the very first interaction, which was relatively easy to optimize. INP evaluates every interaction throughout the entire visit, which requires a more thorough audit of client-side JavaScript and can demand architectural changes on sites with heavy front-end logic.
Further reading
Other providers and guides worth comparing:
