You’ve noticed it. You open your own site on your phone while you’re waiting for a coffee and it just sits there. A white screen, then the logo, then eventually the rest of it turns up like it’s been stuck in traffic on Narellan Road.
Then you go looking for an answer and end up on a page full of red and orange scores, terms like “render blocking resources” and “cumulative layout shift”, and a recommendation to “eliminate unused JavaScript”. Which is useless if you install air conditioners for a living, this isn’t your area of expertise.
So here’s the version without the jargon. Why your website is slow, what it’s costing you, and which of the fixes you can sort out yourself against which ones need someone in the code.
How Do I Check My Website Speed in 30 Seconds?
Don’t start with a tool. Start with your phone.
Turn your wifi off so you’re on mobile data like a real customer, stand outside, and open your own site. Count. If you can’t read anything by about three seconds, you have a problem worth fixing. That test tells you more than any score out of 100, because it’s the exact experience the person deciding whether to call you is having.
If you want the number afterwards, Google’s own benchmark is that the main content of a page should appear within about 2.5 seconds. Anything past four is well into the range where people leave.
What Is a Slow Website Actually Costing You?
Enquiries you never hear about, which is what makes it so easy to ignore.
Roughly half of mobile visitors abandon a page that takes more than three seconds to load, and the drop-off gets steeper with every extra second. Those people don’t email to tell you your site was slow. They just ring someone else, and from where you’re sitting it looks like nothing happened.
There’s a search cost on top of that. Speed feeds into Google’s page experience signals, so poor performance makes it harder to rank in the first place, particularly on mobile. It sits alongside the other local SEO ranking factors rather than replacing them, but a slow site drags on all of it. You end up paying twice: fewer people find you, and fewer of the ones who do stick around.
The Four Things That Usually Cause It
In our experience nearly every slow site we look at has at least two of these.
Photos that are far too big
The most common cause by a distance. A photo straight off a phone or a camera can be several megabytes. Twenty of them on a gallery page and you’ve built something that loads fine on your home wifi and crawls everywhere else. Compressing images properly typically cuts total page weight by more than half without any visible drop in quality.
Too many plugins doing too much
Every plugin bolted onto a site adds code that has to load. Most sites we inherit have a handful doing genuinely useful work and a dozen left over from things somebody tried once in 2021. Heavy page builders are the other usual suspect, and between them plugin bloat and builder code account for a large share of slow sites.
No caching
Without caching, your site rebuilds every page from scratch for every visitor. With it, it serves a ready-made copy. It’s the difference between cooking each meal to order and having it plated up in advance, and it’s usually a switch someone just never turned on.
Cheap hosting
The five dollar a month plan puts your site on a machine shared with hundreds of others, all queuing for the same resources. No amount of tidying up the site fixes a slow server underneath it, which is why hosting is often the single highest-impact change available.
Which Fixes Can I Do Myself?
Some of this genuinely is a DIY job.
- You can do: resize and compress images before you upload them, delete plugins you don’t use, and remove old pages and galleries you’ve forgotten about. That trio alone fixes a meaningful share of slow sites.
- You’ll want a developer for: caching and server configuration, moving to better hosting without breaking anything, cleaning up the code a page builder has left behind, and working out which plugin is actually the culprit when several are suspect. Our website optimisation work in Macarthur is mostly this.
The honest line between them is this. If it involves the content you added, you can probably fix it. If it involves how the site is put together or where it lives, get someone who does this daily, because the failure mode is a site that’s offline rather than a site that’s slow.
Keeping It Fast Afterwards
Speed isn’t a one-off job, which is the part that catches people out. Sites get slower over time as photos get added, plugins update, and content piles up. A site rebuilt to load in two seconds will be back at five within a year if nobody’s watching it.
That’s the practical argument for ongoing hosting and maintenance rather than a rebuild every few years. Someone checking the numbers monthly catches a slow creep before it costs you work.
It also connects to everything else on the site. Speed sets the ceiling for the mobile experience and for turning visitors into enquiries, because none of the work you’ve put into trust signals or a tidy contact form counts for anything if the page hasn’t finished loading.
Where to Start
Three things. Do the phone test outside on mobile data, because that’s the reality your customers are dealing with. Compress your images first, since it’s the most common cause and the easiest thing to fix yourself. And treat speed as something to maintain rather than something to fix once.
If you’ve done the test and the answer was grim, send us the address and we’ll tell you what’s causing it and roughly what it’d take to sort out. No obligation, and if it’s a ten minute fix we’ll say so.