Most small business websites fail Google's Core Web Vitals test. Only 48% of mobile pages passed all three metrics in 2025, according to HTTP Archive's own crawl of the web. That number blends every site on the internet into one figure, and it turns out the mid-size, script-heavy sites in the middle of the pack drag the average down further than small ones do. Suvysoft builds every site to clear the bar regardless of which tier it lands in.
What percentage of small business websites actually pass Core Web Vitals?
The 2025 Web Almanac, HTTP Archive's annual report built on real Chrome user data, found that 48% of mobile origins and 56% of desktop origins passed all three Core Web Vitals (HTTP Archive, 2025 Web Almanac). That is genuinely progress. Mobile pass rates climbed from 36% in 2023 to 44% in 2024 to 48% in 2025, and desktop moved from 48% to 55% to 56% over the same three years.
Progress is not the same as passing. A near-even coin flip is still the honest description of whether a random small business site meets the bar today, and the number that decides most failures is the same one that decided them three years ago.
Which metric actually fails, and why does it matter more than the others?
Broken down by individual metric on mobile, 62% of pages have a good Largest Contentful Paint (LCP), against 77% for Interaction to Next Paint (INP) and 81% for Cumulative Layout Shift (CLS) (HTTP Archive, 2025 Web Almanac). LCP is the laggard by a wide margin, and it is also the metric small business sites are most likely to get wrong on purpose without realizing it.
LCP measures how long it takes the biggest visible element (usually a hero image, sometimes a headline) to render. The two most common causes on a small business site are a hero image that was never compressed or resized for the container it renders in, and a web font loaded from a third-party CDN that blocks text from painting until the font file arrives. Both are fixable in an afternoon by someone who knows to look for them, and both sit untouched on most sites because nobody ever pointed a diagnostic tool at the home page.
Why do bigger websites often score worse than smaller ones?
This is the part most speed advice skips, and it is the actual news in the 2025 data. Pass rates do not decline in a straight line as sites get bigger. They form a U-shape.
| Site popularity tier (mobile) | Core Web Vitals pass rate | What is typically running on the page |
|---|---|---|
| Top 1,000 sites | 51% | Dedicated performance teams, custom infrastructure |
| Top 10,000 to 100,000 sites | 37% to 42% | Ad networks, tag managers, consent banners, chat widgets |
| Top 1,000,000 sites | 42% | Larger CMS installs, more plugins, more marketing scripts |
| Top 10,000,000 sites | 48% | Smaller, simpler sites, closer to where most small businesses sit |
The worst-scoring tier is the top 100,000, not the smallest sites measured (HTTP Archive, 2025 Web Almanac). That tier is where mid-market publishers and growing e-commerce brands live, and it is the tier that has accumulated the most third-party weight: ad exchanges, A/B testing scripts, chat widgets, consent management platforms, and analytics pixels stacked on top of each other, each one added independently by a different vendor with no one owning the total page weight. A five-page brochure site for a plumbing company or a dental practice usually has none of that. It is not fast because it was engineered carefully. It is fast because there is less on the page to slow it down.
That is a real advantage small business owners rarely get credit for, and it is also not something to rely on. The same simplicity that keeps a small site out of the worst-performing tier does nothing to fix a bloated hero image or an unoptimized page builder theme, which is exactly why the sub-50% pass rate persists at every tier including the smallest one measured.
Why does your site show no Core Web Vitals data at all?
A number of small business owners who run their own site through Google's PageSpeed Insights tool see no field data section at all, just a lab score with a note that real-user data is unavailable. That is not a bug and it does not mean the tool is broken.
Core Web Vitals field data comes from the Chrome UX Report (CrUX), which only includes an origin once enough real Chrome users have visited it to produce a statistically reliable measurement. Google does not publish the exact threshold. Its own documentation states plainly that "an exact number is not disclosed, but it has been chosen to ensure that we have enough samples to be confident in the statistical distributions for included pages" (Chrome for Developers, CrUX methodology). A new site, a low-traffic site, or a site that gets most of its visits from a handful of repeat local customers can sit below that line indefinitely.
Practically, this means Search Console's own Core Web Vitals report will show nothing for a real slice of small business sites, not because they are fast or slow, but because Google has not collected enough real visits to say either way. Lab data from PageSpeed Insights or Lighthouse still works in that situation, since it runs a synthetic test rather than waiting on real traffic, and it is the only signal available until field data accumulates.
Does a Core Web Vitals score actually change your Google ranking?
Yes, but not the way most advice implies. Google's own Search Central documentation is direct about it: "Core Web Vitals are used by our ranking systems," but "Google Search always seeks to show the most relevant content, even if the page experience is sub-par" (Google Search Central, Understanding page experience). The same page adds that "getting good results in reports like Search Console's Core Web Vitals report or third-party tools doesn't guarantee that your pages will rank at the top of Google Search results."
In practice, Core Web Vitals behave as a tiebreaker, not a gate. A page with better content and stronger topical relevance will usually outrank a faster page with weaker content. Where speed decides the outcome is between two pages that are otherwise close: similar content, similar backlink profile, similar relevance to the query. That is a common situation for small business sites competing against near-identical competitors in the same city, which is exactly where a real speed advantage tends to show up in rankings.
What should a small business website builder actually be doing about this?
The fixes that move the needle are not exotic. In order of typical impact:
- Compress and correctly size every hero image, and set explicit width and height so nothing shifts as the page loads.
- Load fonts locally or through a modern font-loading strategy instead of a third-party CDN that blocks the initial paint.
- Cap third-party scripts to the ones actually earning their keep. Every analytics pixel, chat widget, and marketing tag is a network request and a chunk of JavaScript the browser has to run before the page settles.
- Keep JavaScript framework choices lean. A marketing site with a handful of interactive pieces does not need the same client-side weight as a full web application.
- Re-test after every redesign or plugin install, since a single new marketing script can undo months of prior optimization in one deploy.
This is the same list Suvysoft runs on every build, in more detail, in our Lighthouse performance breakdown. Our web development engagements start with a Lighthouse and PageSpeed Insights audit before a single design decision gets made, because a fast foundation is cheaper to build in from day one than to retrofit after launch.
Frequently asked questions
What counts as a good Core Web Vitals score?
Google scores three metrics: Largest Contentful Paint under 2.5 seconds, Interaction to Next Paint under 200 milliseconds, and Cumulative Layout Shift under 0.1. An origin needs a "good" rating on all three, for at least 75% of real visits, to count as passing overall. Missing the bar on even one metric fails the whole assessment for that page.
Why does my site show no data in Google Search Console's Core Web Vitals report?
Google only publishes Core Web Vitals field data for an origin once it has collected enough real Chrome visits to be statistically confident in the result, and it does not disclose the exact traffic threshold. Lower-traffic sites, new sites, and sites with a small, repeat local audience often stay below that line indefinitely. Lab data from Lighthouse or PageSpeed Insights still works in that case, since it does not depend on real visitor volume.
Is a small, simple website automatically fast?
Not automatically, but it starts with an advantage. HTTP Archive's 2025 data shows the worst-performing tier of the web is mid-size sites, roughly the top 10,000 to 100,000 by traffic, loaded down with ad tech and marketing scripts. Small sites tend to carry less of that weight by default, but an unoptimized hero image or a bloated page builder theme can still fail the same test a small site would otherwise pass.
How much does Core Web Vitals actually affect my Google ranking?
Google states directly that Core Web Vitals are used by its ranking systems, but that relevant content will still outrank a faster page with weaker content. In practice, speed acts as a tiebreaker between pages that are otherwise close on relevance and authority, which is a common scenario for small businesses competing against similar competitors in the same market.
What is the single most common reason small business sites fail Core Web Vitals?
Largest Contentful Paint, which only 62% of mobile pages pass compared to 77% for Interaction to Next Paint and 81% for Cumulative Layout Shift. An uncompressed hero image and a web font loaded from a third-party CDN are the two most common causes, and both are typically fixable within a day once identified.
How often should I re-check my site's Core Web Vitals?
After every redesign, theme update, or new marketing script, at minimum. A single new chat widget or analytics tag can add enough JavaScript to undo a previously passing score, and the change often goes unnoticed until someone runs a diagnostic tool. A quarterly check is a reasonable baseline for a site that is not actively changing.
Want an actual audit instead of a guess? Get in touch and we will run your site through the same PageSpeed Insights and Lighthouse checks referenced here, and tell you exactly which of the fixes above would move your score the most. Recent builds are in our case studies.