Your competitor two blocks away shows up above you on Google. Their reviews are worse, their menu is uglier, their photos look like they were taken on a flip phone. And still, they're on top. There's a good chance the reason is something you've never thought to check: their website loads in under two seconds and yours takes six.
Page speed isn't a technical vanity metric. Since 2021, Google has used it as an official ranking factor for every search — local ones included. And most small business websites, especially the ones built on drag-and-drop template platforms, are quietly bleeding rankings every single day because of it.
Why does Google care so much about a slow website?
Because users do. Google's whole business is sending people to results they'll be happy with. If half the visitors to your page bounce back to search results within three seconds because your homepage is still loading, Google reads that as "this result is bad" and hands your traffic to the next business in the list. Do that for a few months and you're on page two.
The numbers behind this are brutal. Google's own research on mobile load time found...
- Loading time from 1 to 3 seconds increases bounce rate by 32%.
- 1 to 5 seconds increases it by 90%.
- 1 to 10 seconds increases it by 123%.
Every extra second is another chunk of visitors who never see your phone number, never book, never call. For a plumber or a restaurant, that's literal money walking out the door before you knew it arrived.
What are Core Web Vitals, in plain English?
Core Web Vitals are the three specific speed scores Google uses to grade your site. You don't need to memorize them, but you should know roughly what they mean.
- Largest Contentful Paint (LCP): how long until the biggest thing on the screen — usually your hero image or headline — actually appears. Target: under 2.5 seconds.
- Interaction to Next Paint (INP): how long after a tap before the page reacts. Target: under 200 milliseconds.
- Cumulative Layout Shift (CLS): how much the page jumps around while loading — the annoying thing where you go to tap a button and something shoves it aside. Target: near zero.
Fail any of these on mobile and Google treats your site as a lower-quality result. Roughly 80% of local searches happen on phones, so mobile is the whole game.
How do I check if my own website is too slow?
Go to pagespeed.web.dev, paste in your URL, and hit analyze. It's free, it's Google's own tool, and it gives you the exact numbers Google uses to rank you. Two things to focus on...
- The mobile score (not desktop). Anything under 50 is bad. Under 30 is a crisis.
- The Core Web Vitals Assessment at the top. If it says "Failed," that's an active ranking problem, not a hypothetical one.
If you'd rather trust your gut, open your site on your phone using cellular data from a cold start — close the browser, then reopen it. Count out loud. If you're at four seconds and the hero image still isn't there, your customers are already leaving.
Why are DIY builder websites so slow by default?
Because they're built to make the person building the site happy, not the person visiting it. Drag-and-drop editors work by loading a giant, do-everything template that has to be flexible enough to render whatever layout a user might drag together. That flexibility comes with a heavy price tag in code weight.
- Bloated theme frameworks that ship with hundreds of features you'll never use, loaded on every page.
- Plugins for basic things like a contact form or a photo gallery, each adding its own scripts and stylesheets.
- Uncompressed images uploaded straight from the owner's phone at 4000×3000 pixels, then displayed at 400×300.
- Trackers stacked on trackers — analytics, chat widgets, ad pixels, cookie banners — all racing to load before your content does.
- Cheap shared hosting where your site competes with a few thousand strangers for the same server's attention.
You didn't ask for any of this. But it's what you got the second you signed up for the "free" plan.
What actually makes a website fast?
The short version, without the jargon...
- Ship only the code the page needs — not the whole framework, just the parts this page actually uses.
- Compress and correctly size every image so a hero photo is 100KB, not 5MB.
- Serve files from a CDN so visitors download from a server geographically close to them.
- Cut third-party junk to the bare minimum: one analytics tool, no chat widget you never answer, no cookie banner running a hundred trackers.
- Load fonts smartly so text doesn't invisibly wait for a decorative font before appearing.
None of this is exotic. It's just discipline that gets thrown out the window the moment someone clicks "install" on the next shiny widget.
How much traffic does a slow site actually cost you?
The real-world numbers are consistent across every major study.
- Deloitte found that a 0.1 second improvement in mobile load time increased retail conversions by 8.4%.
- Walmart found that every 1 second faster meant a 2% jump in conversions.
- The BBC reported losing 10% of their users for every additional second a page took to load.
Scale that to a local business: if your site gets 500 Google visits a month and converts 3% into calls or bookings, shaving three seconds off your load time can realistically push you to 4–4.5%. That's a handful of new customers every month, from a fix you make once.
The honest bottom line
Nobody rewards you for having a fast website — you just quietly stop being punished for a slow one. Speed is the least glamorous SEO work there is, which is exactly why so few local competitors ever bother with it. The businesses pulling ahead on Google in their town usually aren't the ones with the fanciest design or the biggest ad budget. They're the ones whose site loads in 1.8 seconds while everyone else's crawls at six. Google notices. Customers notice. And the phone rings a little more often for reasons the owner can't quite explain.