TL;DR: Core Web Vitals are three measurements Google uses to judge how fast, responsive, and stable your website feels to a real visitor: LCP, INP, and CLS.
For a small business, passing them helps your Google ranking and, more importantly, stops visitors from leaving before they buy.
At QED web design we build for these thresholds as standard. As of 2026 the targets are LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1, each measured on your real visitors, not a lab test.
This guide explains each metric in plain English, what the numbers mean, how to check your own site for free, and which fixes are worth your time.
- Core Web Vitals are three metrics: LCP (loading), INP (responsiveness), and CLS (visual stability), all judged on real visitor data.
- The 2026 pass marks are LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1, at the 75th percentile of visits.
- Google measures your real visitors, not your fast office broadband, so a site that feels quick to you can still fail.
- According to the HTTP Archive Web Almanack, only around 43% of mobile websites passed all three Core Web Vitals in 2024.
- Passing is a commercial win, not just an SEO one: faster pages keep visitors who would otherwise leave for a competitor.
Core Web Vitals sound like something only a developer needs to worry about, but they quietly decide whether your website keeps the visitors you worked hard to attract.
This guide is the plain-English version: what the three metrics are, the numbers you need to hit as of 2026, how to check your own site without spending anything, and which fixes actually move the needle.
If a slow site is your wider worry, our guide to why your WordPress site is slow covers the ground around this one.
What are Core Web Vitals?
Core Web Vitals are three specific measurements Google uses to score the real-world experience of a web page: how quickly it loads, how fast it responds to a tap or click, and how stable it stays while loading. They are part of Google’s wider page experience signals, and they are measured on actual visitors rather than in a laboratory.
Each metric covers one dimension of experience.
- Largest Contentful Paint (LCP) measures loading, the time until the main content of the page appears.
- Interaction to Next Paint (INP) measures responsiveness, how quickly the page reacts when someone interacts with it.
- Cumulative Layout Shift (CLS) measures visual stability, how much the page jumps around as it loads.
One point that trips people up: INP is relatively new. It officially replaced the older First Input Delay (FID) metric on 12 March 2024, so any guide still talking about FID is out of date. INP is harder to pass because it looks at every interaction in a visit, not just the first one.
Knowing what the three metrics are is only useful once you know the numbers you are aiming for, which is the next section.
What are the Core Web Vitals thresholds in 2026?
As of 2026, the “good” thresholds are Largest Contentful Paint at or under 2.5 seconds, Interaction to Next Paint at or under 200 milliseconds, and Cumulative Layout Shift at or under 0.1. To pass, your page needs to hit all three at the 75th percentile of real visits, meaning at least three out of four of your visitors get that experience (Google web.dev, 2026).
Each metric also has a “needs improvement” middle band and a “poor” band.
- For LCP, needs improvement runs from 2.5 to 4 seconds, and poor is over 4 seconds.
- For INP, needs improvement is 200 to 500 milliseconds, and poor is over 500.
- For CLS, needs improvement is 0.1 to 0.25 and poor is above 0.25.
The thresholds are identical on mobile and desktop, but mobile is far harder to pass because phones have less processing power and patchier connections.
The 75th percentile rule is exactly why a site can look fast to its owner yet still fail, which is worth understanding on its own.
Why does my site pass on my laptop but fail for Google?
Your site can feel instant to you and still fail Core Web Vitals because Google does not measure your experience; it measures your real visitors on their own devices and connections. This is the single most common source of confusion for business owners checking their own sites.
Google scores Core Web Vitals using field data from the Chrome User Experience Report (CrUX), which is real, anonymised data from actual Chrome users visiting your site, gathered over a rolling 28-day window.
Your visitors are on mid-range phones, on mobile data, in places with weaker signal, with your site already cached on your own machine after dozens of visits. Their experience is slower than yours, and theirs is the one that counts.
This is also why a perfect score in a lab tool can be misleading. A tool like Lighthouse runs a single simulated test on one device, which is useful for finding problems but is not what Google grades you on. Field data decides whether you pass; lab data helps you work out why.
Since your own impression is unreliable, the practical question is how to check the real numbers, which you can do for free.
How do I check my Core Web Vitals for free?
You can check your Core Web Vitals for free using two Google tools: PageSpeed Insights for a quick per-page check, and the Core Web Vitals report in Google Search Console for a site-wide view over time. Both are free, and neither requires any technical skill to read.
PageSpeed Insights is the fastest way in. You enter a page URL and it shows your real-visitor field data at the top, where available, alongside a lab score and a list of specific issues to fix.
The field data is the part that matters for passing; the lab suggestions below it are your to-do list. Google Search Console’s Core Web Vitals report then groups all your pages by status, so you can see how many are good, need improvement, or are poor across the whole site.
A brand-new site or a very quiet one may have no field data at all, which is a genuine limitation of the CrUX system rather than a fault with your site. Once you can see your numbers, the useful question is which fixes are worth your time, because they are not all equal.
How do I improve my Core Web Vitals?
You improve Core Web Vitals by fixing whichever metric is in the “poor” band first, then working through the common causes: oversized images and slow hosting for LCP, heavy JavaScript for INP, and unreserved space for images and ads for CLS. Tackle the worst-scoring metric before polishing one that is already green.
For LCP, the usual wins are compressing and correctly sizing your main images, serving them in modern formats, and being on hosting that responds quickly. For INP, the culprit is normally too much JavaScript, often from a pile of plugins or third-party scripts, so trimming those helps.
For CLS, the fix is reserving space for anything that loads in late, such as images, adverts, and embedded content, so the page does not lurch as they arrive. Much of this overlaps with general performance work, which we cover for one popular page builder in our guide to fixing a slow WordPress site.
The table below sums up the three metrics, what each one measures, the number to beat, and the most common fix, so you can see the whole picture at a glance.
| Metric | What it measures | Good (2026) | Most common fix |
|---|---|---|---|
| LCP | Loading: time until the main content appears | Under 2.5s | Compress images, faster hosting |
| INP | Responsiveness: speed of reaction to a tap or click | Under 200ms | Cut heavy JavaScript and plugins |
| CLS | Visual stability: how much the page jumps while loading | Under 0.1 | Reserve space for images and ads |
Some of these fixes are do-it-yourself, particularly image compression. The deeper work, such as trimming JavaScript safely or diagnosing an INP problem, is quicker in experienced hands. Either way, the honest question is whether the effort pays off for a small business, which is worth answering plainly.
Are Core Web Vitals worth the effort for a small business?
For most small businesses, yes, Core Web Vitals are worth the effort, but the strongest reason is commercial rather than SEO. Faster pages keep visitors who would otherwise give up and leave, and that shows up in enquiries and sales, not just rankings.
It is worth being clear about the ranking side, because it is often overstated. Core Web Vitals are one input among many in Google’s page experience signals, and they tend to act as a tiebreaker between pages of similar quality rather than a magic lever that vaults a weak page to the top.
Anyone promising that passing Core Web Vitals alone will transform your rankings is overselling it.
The commercial case is better evidenced, though the headline numbers come from the platform itself and should be read as such. Google’s own web.dev case study repository reports that Vodafone, after improving its LCP by 31%, saw 8% more sales in an A/B test.
That is a vendor-published figure from Google rather than independent research, so treat it as illustrative of direction rather than a guaranteed return. What is independently measurable is how many sites fall short: according to the HTTP Archive Web Almanac, only around 43% of mobile sites passed all three Core Web Vitals in 2024, so getting yours right puts you ahead of more than half the web.
There is a real QED example here. When we migrated Morgan-Huntley Associates, a UK hospitality consultancy, to our eco-friendly hosting, that single change improved their website performance by 57.7% and, cut its carbon footprint by 95%, with further optimisation added afterwards purely for user experience. You can read the full Morgan-Huntley case study to see how a hosting decision alone moved the numbers that Core Web Vitals measure.
The honest bottom line is that Core Web Vitals are worth getting right, mostly because they keep the customers your marketing already paid to attract.
Keeping a site fast as it grows is also exactly what a WordPress care plan is built to do.
Sources
- Google, “Web Vitals” and Core Web Vitals thresholds documentation (LCP, INP, CLS definitions and 2026 good thresholds), web.dev, 2026 (vendor source)
- Google, “Vodafone: A 31% improvement in LCP increased sales by 8%” (A/B test business-impact case study), web.dev, 2021 (vendor source), HTTP Archive, “Web Almanac 2024: Performance” (share of mobile and desktop origins passing all three Core Web Vitals), 2024, https://almanac.httparchive.org/en/2024/performance
- Google, “Interaction to Next Paint (INP)” (INP replaced FID as a Core Web Vital on 12 March 2024), web.dev, 2024 (vendor source)
- Google Search Central, “Understanding page experience in Google Search results” (Core Web Vitals as part of page experience signals), 2025 (vendor source)
- QED Web Design, “Morgan-Huntley Associates case study” (first-party: 57.7% performance increase and 95% carbon reduction from eco-hosting migration), 2026
If your site is failing them and you would rather someone diagnosed and fixed it properly, get in touch with QED for a free speed check.
