Site Speed for Small Websites: What Core Web Vitals Measure and What's Worth Fixing

Someone finds you in search, taps the link, and waits. The screen stays white. A box appears, then the text jumps down when an image finally loads, and they tap the wrong button. Most people won't tell you what happened. They'll just go back and pick the next result.

The short answer: Google's Core Web Vitals measure three things about real visitors' experience: how fast the main content appears, how quickly the page responds when someone taps or clicks, and whether the layout jumps around while it loads. Fewer than half of websites pass all three on phones. For a small business or municipal site, a few fixes do most of the work: properly sized images, good hosting with caching, and fewer heavy add-ons like pop-ups and third-party widgets. Chasing a perfect score usually isn't worth it. Getting out of the red is.

The three Core Web Vitals, in plain English

Google evaluates these using data from real Chrome users visiting your site, mostly on phones, not just a lab test. A page passes when at least 75% of visits meet the "good" threshold for each metric.

How most sites are doing

The HTTP Archive's 2025 Web Almanac, which analyzes millions of websites, found that only 48% of websites passed all three Core Web Vitals on mobile in July 2025, compared with 56% on desktop. Home pages did worse than other pages. Loading speed was the hardest metric to pass: only 62% of mobile sites had a good LCP, compared with 77% for responsiveness and 81% for layout stability.

In other words, if your site is slow on phones, you're in large company. That's also an opportunity: in a local market, being the fast site among slow competitors is a real advantage.

Does site speed affect Google rankings?

Some, but less than many people are told. Google says it "highly recommends" good Core Web Vitals and that page experience aligns with what its ranking systems reward. But Google also says plainly that it "always seeks to show the most relevant content, even if the page experience is sub-par."

In practice, speed works more like a tiebreaker than a trump card. A fast page that doesn't answer the searcher's question won't outrank a slower one that does. Where speed matters most is with your visitors: a slow page loses people before they ever see what you offer. Relevance, your Google Business Profile and reviews still do the heavy lifting for local search, as we explain in who gets seen online.

How to check your own site

1. Google PageSpeed Insights. Enter your web address. The top section, labeled with real-user data, shows how actual visitors experienced your site over the past 28 days. The section below is a lab test, useful for diagnosing problems. Check the mobile results first.
2. Google Search Console. If your site is verified, the Core Web Vitals report groups your pages into good, needs improvement and poor.
3. Your own phone. Open your site on a phone over cellular data, not your office Wi-Fi. If it feels slow to you, it feels slow to your customers.

Small sites sometimes see "no data" in the real-user section, because Google only shows it when a site gets enough Chrome traffic. In that case, rely on the lab test and your own phone.

What's actually worth fixing

These are the fixes that make the biggest difference on typical small business and municipal websites, roughly in order of payoff:

1. Resize and compress your images. A photo straight off a modern phone can be several megabytes. A web page image rarely needs to be more than a few hundred kilobytes. Use modern formats like WebP where your site supports them.
2. Don't lazy-load the main image. Lazy loading, which delays images until you scroll to them, is great for images further down the page. On the main photo at the top, it slows down LCP.
3. Set image dimensions. When the site knows an image's width and height in advance, it reserves the space, and the page stops jumping when the image arrives.
4. Use good hosting with caching. Cheap shared hosting is often the single biggest cause of slow loading. Page caching and a content delivery network, which serves your site from servers close to each visitor, make a large difference.
5. Cut heavy extras. Every chat widget, social feed, tracking script and pop-up adds weight. Keep the ones that earn their place and remove the rest.
6. If you use a slider, build it right. A well-built slider loads only the first image up front, reserves its space so the page doesn't jump, and uses compressed images. Built that way, it has little effect on speed. The ones that cause trouble load every full-size slide at once and rely on heavy scripts.
7. Keep plugins and themes updated, and few. Outdated or overlapping plugins load extra code on every page. Our guide to what managed WordPress care covers explains why fewer, maintained plugins matter for security too.
8. Limit web fonts. Two font families in a couple of weights is plenty. Each extra weight is another file to download.

Speed is an accessibility issue too

Core Web Vitals aren't part of the accessibility guidelines, but slow, jumpy pages hit some visitors much harder than others. People on older phones, limited data plans or rural connections wait the longest. People with motor or cognitive disabilities are the most likely to tap the wrong thing when a layout shifts under their finger. A fast, stable page is easier for everyone, and essential for some. We cover who those visitors are in the digital divide in 2026 and designing websites for older adults.

For municipal sites, the same logic applies to documents: a 10 MB scanned PDF is a speed problem as well as an accessibility one, which we explain in accessible PDFs, or why you should stop posting so many of them.

How we handle it

We host client sites on managed cloud servers with page caching, and use Cloudflare for content delivery and security. When we build a site, we size and compress images, build features like sliders so they load only what's needed up front, avoid heavy page effects, and keep plugins to what the site actually needs. For sites on our care plans, speed is part of the routine check after updates, because a single new plugin or oversized photo can undo the work.

Sources

• Google Search Central, Understanding Core Web Vitals and Google search results
• Google Search Central, Understanding page experience in Google Search results
• HTTP Archive, Web Almanac 2025: Performance
• web.dev, Web Vitals

The illustrations in this article are AI-generated.