What Are Core Web Vitals? Why They Matter for Your Business
Summary
Core Web Vitals are three metrics: loading speed (LCP, 2.5 seconds or less is considered good), interaction responsiveness (INP, 200 milliseconds or less), and visual stability (CLS, 0.1 or less), per web.dev's official documentation. Google says it uses these in its ranking systems, but also states plainly that it always prioritizes relevant content, so a perfect score doesn't rescue weak content. Per Google's own case studies, a 31% LCP improvement raised Vodafone's total sales by 8%, and a 1-second LCP improvement raised Renault's conversion rate by 13%. We measured our own site: 96/100 on mobile, LCP 2.8s, but since the site is new there's no real-user field data yet, which is itself a good illustration of the gap between lab and field data.
We measured our own site with PageSpeed Insights: 96/100 on mobile, LCP 2.8 seconds, CLS 0. This article explains what those numbers mean and why they matter for your business; the last section shows how to test your own site.
What exactly are Core Web Vitals?
Per Google's official web.dev documentation, Core Web Vitals consist of three metrics, and the "good" threshold for each is set at the 75th percentile of field data, meaning the experience 75% of users actually get:
| Metric | What it measures | "Good" threshold |
|---|---|---|
| LCP (Largest Contentful Paint) | How long it takes the largest content on the page to render | 2.5 seconds or less |
| INP (Interaction to Next Paint) | How fast the screen responds to a click or tap | 200 milliseconds or less |
| CLS (Cumulative Layout Shift) | How much page elements shift around while loading | 0.1 or less |
INP is relatively new: per web.dev, it was promoted from experimental to "pending" status in 2023 with the intent of retiring FID (First Input Delay), and became a stable Core Web Vital in 2024. So an up-to-date guide should reference INP, not FID.
In practical terms, these three metrics map to: LCP is the answer to a visitor's "did the page load?" question; if it's slow, they may leave before ever seeing the page. INP is what happens when you tap a button and the screen responds late; a high INP makes a site feel "stuck." CLS is content or a button shifting position while the page loads, sometimes causing a misclick; on a form or checkout page this is especially frustrating.
How much does this affect Google ranking?
Google Search Central's page experience page (last updated September 22, 2026) states plainly: "Core Web Vitals are used by our ranking systems." But it immediately balances that: "Google Search always seeks to show the most relevant content, even if the page experience is sub-par." The practical upshot: a perfect Core Web Vitals score doesn't rescue weak or irrelevant content, but a speed advantage can matter between two pieces of content of similar quality.
Why it matters for business: three verified case studies
Independent of ranking, speed has a direct effect on user behavior. Three of Google's own published case studies, across different industries, point the same direction. This data is from 2020-2022; it isn't current research, but the methodology (A/B testing) and results are still published in Google's official case study archive.
| Company | What was done | Result |
|---|---|---|
| Vodafone (2021) | 31% LCP improvement, A/B test at ~100K clicks/day | +8% total sales, +15% lead-to-visit rate |
| Renault (2020-2021, 10M visits) | Measured the effect of a 1-second LCP improvement | +13% conversion rate, -14ppt bounce rate |
| Rakuten 24 (2022) | Optimized one landing page for Core Web Vitals, ran a month-long A/B test | +33% conversion rate, +53% revenue per visitor |
To make this concrete: per Renault's data, shaving just 1 second off your site's load time could mean roughly 13 more conversions (a purchase, a form fill, a booking) out of every 100 visitors. That's the result of three separate A/B tests at three different companies, not a guarantee for your specific site, but the direction is consistent.
How it's measured: lab data vs. field data
Per web.dev's official explanation, PageSpeed Insights combines two data sources: lab data (a one-time measurement Lighthouse runs in a controlled environment) and field data, when available (from the Chrome User Experience Report, based on real users' experience over the last 28 days). The Search Console Core Web Vitals report uses field data only.
Our own site is a concrete example of this gap: running groopyagency.com through PageSpeed Insights gives a lab score of 96/100 on mobile and 99/100 on desktop (LCP 2.8s, CLS 0). But because the site doesn't yet have enough visitor traffic, no field data shows up at all. That's not a bug; Chrome requires a minimum traffic threshold to report field data. If your own site is new or low-traffic, seeing only lab data with an empty field-data section in PageSpeed Insights is normal.
In practice, this distinction matters: lab data is repeatable because it's measured on one device/connection speed in a controlled setting, but it doesn't map one-to-one onto what your actual visitors experience. Field data is more realistic because it's gathered from real users across different devices, connections, and locations, but it stays invisible until enough traffic accumulates. The data used in Search Console's report and in ranking is field data; so for a new, low-traffic site, a good lab score is necessary but not, on its own, a guarantee.
Two common misconceptions
"If my score is 100, I'll rank first." The Google quote above says the opposite: if the content isn't relevant, a perfect speed score won't save the ranking. Core Web Vitals is a potential tiebreaker between two pages of similar quality, not a ranking strategy on its own.
"I measured it once, it was good, done." A lab score can change the moment you add a new image, a third-party script (a live chat widget, an ad tag), or a design change. Field data is also a rolling 28-day window that shifts over time. So Core Web Vitals isn't a one-time check, it's an ongoing signal worth revisiting whenever a meaningful change goes onto the site.
Test your own site in 30 seconds
Concretely:
- Go to pagespeed.web.dev and enter your site's address.
- Check the mobile result first (Google's mobile-first indexing makes it more decisive than desktop).
- Check the green/yellow/red color for LCP, INP, and CLS; if anything is red, make that metric your priority.
- If the field data section is empty, that means low traffic; rely on the lab data to assess the score in the meantime.
If you'd like to see this alongside core SEO checks, you can use our free SEO checker tool, which shows PageSpeed data together with SEO and GEO criteria in one report.
Conclusion
Core Web Vitals alone isn't a ranking guarantee, but Google states plainly that it uses these in its ranking systems, and Google's own case studies show speed has a direct effect on sales, conversion, and bounce rate. If you're building a new site, a technology choice that targets these metrics from the start (see WordPress vs. Next.js) costs less than optimizing after the fact; we covered the phases of that process separately in how long does a website take to build.
If you'd like to review your site's Core Web Vitals as part of a website built on fast technology from the start, you can book a call.
Frequently asked questions
How many metrics make up Core Web Vitals?
Three: LCP (Largest Contentful Paint, loading speed), INP (Interaction to Next Paint, interaction responsiveness), and CLS (Cumulative Layout Shift, visual stability). INP is the current metric that replaced FID (First Input Delay) in 2024.
Does a bad Core Web Vitals score directly hurt Google ranking?
Google says it uses these metrics in its ranking systems, but also says "Search always seeks to show the most relevant content, even if the page experience is sub-par." So a weak score alone isn't decisive; it's weighed together with content quality.
Why does the PageSpeed Insights score differ from the Search Console report?
PageSpeed Insights shows both lab data (a one-time, controlled measurement) and, when available, field data (real experience gathered from Chrome users). The Search Console Core Web Vitals report uses field data only. Sites without enough traffic may show no field data at all — that's a data-availability gap, not an error.
How can I test my own site?
Enter your site's address at pagespeed.web.dev; within 30 seconds you'll see a green/yellow/red result for LCP, INP, and CLS. If you'd like to see this alongside core SEO checks, you can also use our free SEO checker tool.
Related services:
Website & Software Development →