Core Web Vitals thresholds: the three numbers
Core Web Vitals are three measures of how a page feels to real visitors. A page passes when 75% of visits are "good" on all three (web.dev).
| Metric | What it measures | Good | Poor |
|---|---|---|---|
| LCP (Largest Contentful Paint) | How fast the main image or text shows | 2.5 seconds or less | Over 4 seconds |
| INP (Interaction to Next Paint) | How fast the page reacts to a tap or click | 200 milliseconds or less | Over 500 milliseconds |
| CLS (Cumulative Layout Shift) | How much the layout jumps while loading | 0.1 or less | Over 0.25 |
Thresholds: PageSpeed Insights. Anything between good and poor is "needs improvement."
INP replaced FID (First Input Delay) on March 12, 2024 (web.dev). Advice that still names FID is out of date.
Does website speed affect Google ranking?
Yes, but it rarely decides it. Google's own answer:
"Core Web Vitals are used by our ranking systems." (Google Search Central)
"Google Search always seeks to show the most relevant content, even if the page experience is sub-par. But for many queries, there is lots of helpful content available. Having a great page experience can contribute to success in Search, in such cases." (same page)
So speed helps when you and a rival are otherwise close. It won't lift a thin page over a better answer. Google also warns that good scores don't "guarantee that your pages will rank at the top," and that chasing "a perfect score just for SEO reasons may not be the best use of your time" (same page).
Google ranks the mobile version of your site: it "uses the mobile version of a site's content, crawled with the smartphone agent, for indexing and ranking" (Google Search Central). Check mobile results first.
"Core Web Vitals assessment failed": what it means
PageSpeed Insights runs this test on data from real Chrome users over the past 28 days. It fails if any of the three metrics misses "good" at the 75th percentile, meaning more than a quarter of visits missed the target (PageSpeed Insights).
Two cases confuse owners:
- No data. A small site often has too few Chrome visitors to measure. PSI then falls back to your whole site, and sometimes shows no real-user data at all (same page). Google's free tool that shows which searches bring people to your site and flags pages Google can't index. More's report shows "No data available" for the same reason (Search Console Help).
- Only INP missing. If there's too little INP data, the page passes on LCP and CLS alone (PageSpeed Insights).
PageSpeed score vs the Core Web Vitals report
They measure different things, so they often disagree.
| PageSpeed score (0–100) | Core Web Vitals (field data) | |
|---|---|---|
| Where | PageSpeed Insights, lab diagnostics | PageSpeed Insights, real-user data; Search Console's Core Web Vitals report |
| Based on | One simulated load on a mid-tier phone | Real Chrome visitors, last 28 days |
| Good means | 90 or more | All three metrics good |
| Use it for | Finding what to fix | Knowing what visitors actually get |
Sources: PageSpeed Insights, Search Console Help.
Google explains the gap: field data covers "a variety of devices and network conditions," while lab data is "a simulated load of a page on a single device" (PageSpeed Insights). Google's ranking guidance names Core Web Vitals, which "measure real-world user experience," and doesn't mention the 0–100 score (Google Search Central). A score of 55 with passing field data is not a ranking problem.
In Search Console, pages are grouped with similar pages, and a group takes the status of its worst metric (Search Console Help).
What makes a small business site slow
| Failing metric | Usual causes | Fix |
|---|---|---|
| LCP | Large hero photo; slow server or several redirects before the page loads | Resize and compress the top image; better hosting; remove redirect chains |
| CLS | Images, ads or embeds without set sizes; web fonts swapping in | Give images and embeds fixed dimensions; reserve space for banners |
| INP | Heavy scripts: chat widgets, trackers, booking embeds | Remove scripts you don't use; load the rest after the page |
Causes: web.dev on CLS, LCP and INP.
On a hosted builder the platform runs the server, but you still control images, embeds and add-ons. More on builders: Wix, Squarespace or WordPress for SEO.
Does a slow site cost you leads?
Probably. In a study of 37 large brand sites in late 2019, commissioned by Google and run by Deloitte and 55, a 0.1-second gain on four speed measures came with up to 21.6% more lead generation site users reaching the form page (web.dev). These were big brands, not local businesses, and every page in the journey had to get faster (same page).
For a service business, test the page someone books from on mobile data: where visitors drop off before booking.
Example
Illustrative cases, not measured results.
A plumber with a PageSpeed score of 48
His real-user data passes all three metrics. His rankings won't move by chasing 90. He spends the time on a missing water-heater page instead.
A dental office failing CLS
Its "book now" banner loads late and pushes the page down, so patients tap the wrong thing. Reserving space for the banner fixes CLS and the mis-taps together.
A law firm with "No data available"
Too few Chrome visitors for field data. The firm runs PageSpeed's lab test on its two main pages, fixes a 4 MB header photo, and rechecks on a phone over mobile data.
Different for you?
- Fast site, still no calls: website not getting leads.
- Traffic fell after a redesign, not a slowdown: traffic dropped after a website redesign.
- Choosing or leaving a site builder: Wix, Squarespace or WordPress for SEO.
- Learning the rest of Search Console: Google Search Console for a small business.
- Building a trade site that loads fast on a phone: HVAC and plumber website design.
- Want a fast site built and kept fast: Website Agent.