A slow website doesn’t just frustrate visitors. It quietly costs you rankings, enquiries, and sales, often before you even know there’s a problem.
Google has used site speed as a ranking factor since 2010, but the way it’s measured has changed significantly. Speed is one factor among many. A slow site won’t automatically outrank a fast one with weaker content, but it compounds. A slow site raises your bounce rate, reduces dwell time, and signals to Google that visitors aren’t finding what they need. The ranking impact is as much indirect as it is direct. And beyond rankings, there’s a simpler argument: a potential client who waits four seconds for your homepage to load and gives up is a lost enquiry. No amount of good content fixes that.
If the last time you thought about your site’s speed was when you built it, there’s a good chance things have shifted underneath you.
What Google Actually Measures Now: Core Web Vitals
Google doesn’t just care whether your site loads fast. It cares about how the experience feels to a real person on a real device.
That’s what Core Web Vitals are: a set of three measurements that capture different aspects of the loading experience. They’ve been an official ranking signal since 2021.
Here’s what each one measures, in plain terms:
LCP (Largest Contentful Paint): how long it takes for the main content on the page to become visible. For most sites, that’s a hero image or a large heading. Google wants this under 2.5 seconds.
INP (Interaction to Next Paint): how quickly your page responds when someone clicks a button or taps a link. Replaced the older FID metric in 2024. Under 200 milliseconds is good.
CLS (Cumulative Layout Shift): whether the page jumps around while it’s loading. You’ve experienced this: you go to tap a button, the page shifts, and you tap the wrong thing. Google measures how much of this happens and penalises sites where it’s bad.
You don’t need to memorise these. But you do need to know whether your site is passing or failing them, because Google does.
How to Check Your Own Site Speed
The quickest way is Google’s PageSpeed Insights. Paste in your URL, and it gives you a score out of 100 for both mobile and desktop, plus a breakdown of what’s causing any issues.
A score above 90 is good. Between 50 and 89 is worth investigating. Below 50 is a problem.
Pay attention to the mobile score specifically. Most of your visitors are on their phones, and Google uses mobile performance as the primary signal for rankings.
GTmetrix is another useful tool. It gives more detail on what’s slowing things down and lets you test from different locations.
If your scores are low, the next question is: why?
The Cause Most People Don’t Think About: Your Hosting
When a site is slow, most people assume it’s the design, the images, or too many plugins. Those things matter. But the single most overlooked cause of a slow website is cheap hosting.
Every website lives on a server. When someone visits your site, their browser sends a request to that server and waits for a response. If the server is overloaded, underpowered, or physically far away from your visitors, every single page load starts with a delay before any of your content has even begun to load.
This is called Time to First Byte (TTFB), and it’s foundational. You can optimise everything else perfectly and still have a slow site if your hosting is poor.
A lot of web agencies use reseller hosting: a single server account they’ve divided up among all their clients. It’s cheap to run, and you’d have no way of knowing that’s what you’re on. But it often means your site is sharing resources with dozens or hundreds of others.
Good hosting isn’t necessarily expensive. But it does need to be appropriate for the size and traffic of your site, located in Australia if your audience is here, and not oversubscribed. It’s worth asking your developer or host directly what infrastructure your site is actually running on.
What Else Affects Speed
Once hosting is ruled out, these are the most common culprits:
Unoptimised images are the most frequent cause of slow load times on otherwise well-built sites. Images should be compressed and served in modern formats like WebP. If your site is still serving 3MB JPEGs uploaded years ago, that’s the easiest fix available.
Too many plugins add weight to WordPress sites, especially. Every active plugin loads additional code. A site with 40 plugins, half of them unused, is carrying unnecessary baggage on every page load.
Missing or misconfigured caching means the server rebuilds your pages from scratch on every visit, rather than serving a pre-built version. Most good hosting includes caching, but it needs to be set up correctly to make a difference.
Render-blocking third-party scripts (chat widgets, analytics tags, ad scripts) can hold up how quickly a page becomes visible to the visitor. A developer can load these asynchronously so they don’t delay the rest of the page.
A Quick Checklist
Before you call a developer, run through this:
If your scores are below 70 on mobile and you’re not sure where to start, the hosting question is usually the right first conversation to have.
Not sure whether your site’s speed is holding you back? We’re happy to take a look and give you an honest read, no obligation.
