Most small business owners never time their own website. They open it on the office Wi-Fi, it looks fine, and they move on. Your customers aren't sitting on your office Wi-Fi, though. They're standing at a bus stop in Pleven with one bar of 4G, tapping your link from a Google Maps listing, and deciding within a few seconds whether to wait or go back and tap the next result. In this guide I'll show you how to tell whether your site is too slow, what "fast enough" means in numbers Google actually uses, what usually causes the problem, and when fixing it is a quick job and when it's a sign you need a rebuild.
Why a slow website costs you clients, not just rankings
Speed is often sold as an SEO thing. It is, a little. But the bigger cost shows up before anyone thinks about rankings: people leave. A visitor who waits for a blank white screen doesn't read your prices, doesn't see your reviews and doesn't call.
The best-known evidence is the Milliseconds Make Millions study that Deloitte and 55 ran for Google. They monitored 37 brand sites and more than 30 million user sessions at the end of 2019. A 0.1-second improvement in mobile speed went with conversion rates 8.4% higher for retail sites and 10.1% higher for travel sites. Lead-generation sites saw more people get from the first step of a form to submitting it.
Those are large brands, and your figures will be different. The point holds anyway: tenths of a second change what people do. And according to the 2025 Web Almanac, which measured millions of sites in July 2025, more than half the web still fails Google's own speed bar on phones. For a small business, that's an opening. Simply being faster than the competitor down the road is a real advantage.
What "fast enough" means: the three numbers Google uses
Google measures real-world speed with three Core Web Vitals. The "good" thresholds come from web.dev, Google's developer site:
LCP — loading
Largest Contentful Paint: how long until the biggest thing on screen (usually the hero photo or headline) appears. Good is 2.5 seconds or less.
INP — responsiveness
Interaction to Next Paint: how quickly the page reacts when someone taps a button or opens a menu. Good is 200 milliseconds or less.
CLS — stability
Cumulative Layout Shift: how much the page jumps around while loading, the moment you tap "Call" and hit an ad instead. Good is 0.1 or less.
The detail people miss: Google judges the 75th percentile of real visits, measured separately on mobile and desktop. A page passes only when all three metrics are good. So your fast laptop doesn't count. Three out of four visits from real phones have to be fast.
Test your site in 10 minutes
You don't need a developer for a first diagnosis. Do this today:
- Open PageSpeed Insights (pagespeed.web.dev), paste your homepage address and run it. Look at the top section first, "Discover what your real users are experiencing". That's real visitor data. The score underneath is a lab simulation.
- Check the Mobile tab, not Desktop. Most local searches happen on phones, and mobile is where sites fail.
- Write down LCP, INP and CLS and compare them with the thresholds above. If it says there isn't enough real-user data (common for small sites), use the lab LCP as a rough guide.
- Test your most important page too, such as the service page or product page that brings in enquiries, not just the homepage.
- Do the bus-stop test. Turn Wi-Fi off on your phone, open your site from Google and count how many seconds pass before you could actually read and tap something.
- If you have Google Search Console, open the Core Web Vitals report. It groups your slow URLs so you can see whether it's one page or the whole site.
If you'd rather skip the jargon, run my free website check. It looks at speed alongside the basics (mobile layout, SEO, accessibility) and tells you in plain language what's worth fixing first.
The usual suspects behind a slow small business site
When I audit a slow site for a local business, it's almost never one mysterious bug. It's the same handful of things:
- Huge images. A 5 MB photo straight from a phone or camera, displayed at 600 pixels wide. This is the number one cause of a bad LCP.
- A heavy page builder or theme. Multipurpose WordPress themes and drag-and-drop builders load code for features you never use, on every page.
- Too many plugins and widgets. Chat bubbles, pop-ups, sliders, Instagram feeds, review widgets, each with its own scripts.
- Cheap or distant hosting. If the server takes a long time just to start answering, nothing else can be fast.
- No caching. The server rebuilds every page from scratch for every visitor.
- Fonts and embeds loaded the slow way. Five font weights, a full Google Map and a YouTube video on the homepage, all loading before anything else.
- Images and ads without reserved space, which is what makes the layout jump and ruins CLS.
Quick fixes vs a rebuild: how to decide
Not every slow site needs a new one. Here's how I explain the difference to clients:
The site is reasonably modern and the problem is mostly images, caching or one or two heavy plugins. Compressing and resizing images, converting them to WebP, turning on caching and removing unused add-ons can often take LCP from "poor" to "good" in a day or two of work.
The slowness comes from the foundation: a bloated builder, an outdated theme nobody can update, or a site that also fails on mobile layout, content and accessibility. Then you pay to patch something that will still be slow, and a lean new site is often the cheaper path over a few years.
If you're paying every year to make a heavy site slightly less heavy, you're renting speed instead of owning it.— a pattern I see in redesign projects
What I do differently when I build for speed
When I build a new site, speed is part of the design brief, not a plugin added at the end. In practice that means:
- Hand-built, lightweight pages instead of a multipurpose theme carrying hundreds of unused features
- Every image exported at the size it's shown, in a modern format like WebP, with lazy loading below the fold
- Width and height reserved for every image and embed, so nothing jumps
- One or two font files, not a whole family
- No third-party script unless it earns its place (and maps or videos load only when someone wants them)
- A real-phone test on a slow connection before launch, not just a desktop score
That's part of how I approach web design for small businesses. New websites start from €890, go live in 2–5 weeks and include 3 months of free care afterwards. If you only need a targeted speed fix on an existing site, small jobs start from €90. I'll tell you honestly which of the two you need.
Your speed checklist for this week
- Run PageSpeed Insights on your homepage and your top enquiry page (Mobile tab)
- Note LCP, INP and CLS and compare them with 2.5 s, 200 ms and 0.1
- Find the three largest images on your homepage and check their file size
- List every plugin, widget and pop-up and ask: does this bring me clients?
- Do the bus-stop test on mobile data
- Decide: tune-up or rebuild, using the comparison above
Next step: find out where your site stands
A slow website is one of the few marketing problems you can measure in an afternoon and often fix in a week. If you want a second pair of eyes, start with the free website check. You'll get a short, plain-language list of what's slowing you down. And if it turns out your site needs more than a tune-up, have a look at how I build fast, lightweight websites for small businesses in Bulgaria and across the EU.