Most website problems announce themselves. A broken form, a typo on the homepage, a photo that stretches sideways — someone tells you. Slowness doesn't work like that. A visitor taps your link, waits a beat too long, and goes back to the search results. You never hear from them, and nothing on your end looks broken.
That's what makes speed worth paying attention to. It's one of the few things that costs you enquiries without leaving any evidence behind.
What "slow" actually means to someone on their phone
We're not talking about minutes. We're talking about the difference between one second and three.
A study commissioned by Google and carried out by Deloitte and 55 looked at 37 major retail and travel brands across more than 30 million user sessions. They found that a mobile speed improvement of just 0.1 seconds — a tenth of a second — lifted retail conversions by 8.4% and travel conversions by 10.1%. Not a rebuild. Not a redesign. A tenth of a second.
For a small business, that maths is more modest but it points the same direction. If your site takes four seconds to show anything useful on a phone with average reception in a Melbourne café, a meaningful slice of the people who clicked through never actually see your work.
It's also worth remembering how people arrive. Someone searching "roof repairs near me" on their phone isn't loyal to you yet. They have four other tabs open. There's very little holding them there while a hero image downloads.
The three numbers Google watches
Google measures real visits to your site using three metrics, collectively called Core Web Vitals. You don't need to memorise them, but knowing what they mean makes any conversation with a developer far less mystifying.
Largest Contentful Paint (LCP) — how long until the main thing on the page appears. Usually that's your header image or headline. Google considers under 2.5 seconds good.
Interaction to Next Paint (INP) — how quickly the page responds when someone taps or clicks. If a menu takes a moment to open after you tap it, that's INP. Under 200 milliseconds is good.
Cumulative Layout Shift (CLS) — how much the page jumps around while it loads. You've experienced this: you go to tap a link, an ad or image loads above it, and you tap the wrong thing. Under 0.1 is good.
Each is measured at the 75th percentile of real visits, which is a technical way of saying three out of four of your visitors need a good experience for you to pass.
These are a ranking signal in Google search, but a modest one. Google's own people have described page experience as closer to a tie-breaker than a heavyweight factor — better content on a slower site will still beat thin content on a fast one. So don't chase a perfect score at the expense of everything else. The stronger argument for fixing speed isn't rankings. It's that the visitor who already found you actually stays.
Where the slowness usually comes from
In our experience, small-business sites are rarely slow for exotic reasons. It's nearly always one of four things.
Enormous images. By far the most common culprit. A photo straight off a phone or a DSLR can be 4–8 MB. Displayed at 800 pixels wide on a page, it needs perhaps 150 KB. Uploading originals is the single easiest way to make a site crawl, and it's the easiest to fix.
Plugin sprawl. Every plugin, tracking pixel and embedded widget adds code the browser has to fetch and run. A site with 30 plugins, half of them left over from an idea that didn't go anywhere, is carrying weight for no return.
Cheap or overloaded hosting. If your host packs thousands of sites onto one server, your visitors wait in a queue they can't see. Hosting is one of the few areas where the cheapest option genuinely shows up in the customer experience.
Fonts, sliders and video backgrounds. Custom fonts and full-width autoplay video look wonderful in a design mockup. On a phone with three bars of reception, they're expensive. A homepage slider that nobody swipes past the first image is pure cost.
What's worth doing first
You can check where you stand in about a minute. Run your homepage through Google's PageSpeed Insights (pagespeed.web.dev). Look at the mobile results rather than desktop — that's where most of your visitors are, and where problems show up.
Then, roughly in order of effort versus payoff:
- Resize and compress your images. Export at the size they'll actually display and save as WebP where you can. This alone often halves page weight.
- Turn on caching. Most platforms have it built in or a plugin for it. It means returning visitors and repeat pages load from a stored copy rather than being rebuilt each time.
- Delete plugins you don't use. Not deactivate — delete. They're a security liability as well as a speed one.
- Set width and height on images. This stops the page jumping as things load, which fixes most layout shift problems.
- Look honestly at your hosting. If your site is slow when it's empty of traffic, no amount of image optimisation will save it.
Beyond that — reducing JavaScript, deferring scripts, tuning the server — you're into territory where a developer will get further in an hour than you will in a weekend. That's a reasonable place to stop and ask for help.
The short version
Speed isn't a vanity metric and it isn't about impressing Google. It's about the person who searched for what you do, found you, and decided in under three seconds whether you were worth the wait. Most of the fixes are unglamorous — smaller images, fewer plugins, better hosting — and most of them are one afternoon's work.
If you'd like a straight answer on how your site is performing and what's actually worth fixing, get in touch. We'll take a look and tell you plainly — no jargon, and no upsell for work you don't need.