Why Is My Website So Slow, and Is It Costing You Customers?

Nobody notices a fast website. A slow one gets noticed at the worst possible moment: a customer standing in a carpark with two bars of reception, trying to find your phone number while your homepage loads a slider they'll never watch. I build websites for a living, and when someone asks me to look at a slow one, it's nearly always the same four problems in some combination. None of them are mysterious. Two of them you can probably fix yourself this week without paying anyone. Here's how to work out which ones you've got.

First, get a real number

Don't diagnose from your office chair. Your site feels fast to you because you load it every day on the office wi-fi and your browser has most of it cached. Your customers get neither advantage. So run two tests. Put your address into Google's PageSpeed Insights, which is free, and read the mobile result, not the desktop one. The number that matters most is Largest Contentful Paint, which is roughly "how long until the main thing on the page shows up". Google's line in the sand is 2.5 seconds. Then do the low-tech test: open your site on your own phone, on mobile data, standing outside. That's how a tradie in a ute or a customer walking down Rundle Mall actually meets your business. If you've got Search Console set up, its Core Web Vitals report will also tell you how real visitors have been experiencing the site for months. I've written a plain-English explainer on what those Core Web Vitals numbers mean if you want to go deeper.

Suspect one: photos uploaded straight off the phone

This is the most common cause of a slow small-business site, and the cheapest to fix. A modern phone takes photos around 4,000 pixels wide and several megabytes each. The slot on your homepage might display them 400 pixels wide. Upload the original and every visitor downloads ten times the picture they'll ever see, then their phone does the shrinking. Multiply that by a gallery of twenty and your homepage weighs more than a whole album's worth of music. The fix is unglamorous: resize images to something near the size they're displayed at, convert them to a modern format like WebP, and make anything below the first screen lazy-load so it only downloads when someone scrolls to it. On a lot of the slow sites I've looked at, this one change would have solved most of the problem before anything else was touched.

Suspect two: the page-builder pile

WordPress, Wix and their cousins aren't automatically slow, but the way most small-business sites get built on them is. A multipurpose theme designed to demo a hundred different layouts. A page builder that ships its entire editing engine to every visitor. A plugin for the contact form, another for the gallery, another for SEO, another for the slider someone added in 2022, and a dozen more nobody remembers installing. Every one of those is code your customer's phone downloads and runs before the page settles down. The site you see in the editor is maybe a tenth of what actually gets sent. You can tame it, with a lean theme, ruthless plugin deletion and good caching, and if your site is otherwise serving you well, that's worth an afternoon. But be honest about the result: you're tuning a loaded trailer, not a lighter vehicle. If you're weighing up whether taming it is worth it, the maths in our Wix versus custom cost comparison is the sensible place to start.

Suspect three: hosting that's cheap for a reason

Where your website physically lives matters more than most owners realise. Very cheap shared hosting means your site is one of hundreds on the same overworked server, and the time it takes that server to even begin responding stretches accordingly. Distance stacks on top: if the server is in the United States, every request from an Adelaide phone crosses the Pacific and comes back before a single pixel renders, and a page is never one request. That's physics, and no amount of image compression fixes it. Ask your host two questions: where is the server, actually, and what am I sharing it with? If you can't get a straight answer, that is the answer. We covered what decent hosting should include, and what $30 a month ought to buy you, in our guide to small-business hosting in Australia.

Suspect four: the script pile-up

This one creeps in over the years. A live-chat widget nobody staffs anymore. A heatmap tool from a marketing experiment that ended in 2023. Two analytics tags because nobody removed the old one. A social pixel, an embedded reviews feed, five weights of a custom font when the site uses two. Each addition felt small at the time, and each one is a separate thing to fetch and run, often from a different company's servers, before your page feels usable. The audit takes ten minutes: list every third-party thing bolted onto the site and ask who looks at it. If the answer is nobody, it goes. On some sites I've reviewed, the trackers and widgets outweighed the actual content.

What slow is actually costing you

Here's the uncomfortable part. A slow site doesn't send you an error report. The customer who gave up at the spinner doesn't email to say so; they tap back and ring the next business in the results. You'll never see them in any dashboard, which is exactly why slow sites survive for years. The cost lands hardest on mobile, where most local searches happen, often on patchy reception where every unnecessary megabyte is felt. And yes, Google's page-experience signals mean speed plays a part in rankings, but I'd be straight with you: it's a modest part, and anyone selling speed as an SEO silver bullet is overselling it. The reason to fix a slow site is the person already trying to use it. Being genuinely usable on a phone is the whole game for a local business, and speed is half of usable.

What to fix this week

• Run PageSpeed Insights on your homepage and note the mobile LCP number.
• Load your site on your own phone, on mobile data, outside. Time it honestly.
• Resize and compress your ten heaviest images; convert them to WebP if you can.
• Delete every plugin, app and widget you can't name a current reason for.
• Remove the slider. One good photo beats five rotating ones every time.
• Ask your host where the server is located and what plan you're actually on.
• List every third-party script on the site and cut the ones nobody looks at.
• Re-test. If mobile LCP is still failing, the problem is the foundation.

When patching stops being worth it

Sometimes you do all of the above and the tests still fail, because the weight is baked into how the site was built. At that point you're deciding between paying someone to renovate a slow foundation or replacing it. I'll declare my bias: we hand-code sites precisely so this problem can't happen, no page builder, no plugin stack, nothing shipped to your visitor that the page doesn't use, and green Core Web Vitals as a build standard rather than an optimisation project. A one-page site is $399, a multi-page site is $899, they're live in 5 to 10 days, and hosting is $30/month with no lock-in contract. Compare that with a quote to speed up an ageing builder site and the maths often isn't close. The other thing worth reading before you spend anything is our rundown of the hidden costs of cheap websites, because slow hosting and bloated builds are usually symptoms of the same corner-cutting. You can see exactly what's included in the pricing and website packages.

Frequently asked questions

What is the easiest free way to test my website speed?

Two tests, ten minutes. Run your address through Google's PageSpeed Insights and look at the mobile result, especially the Largest Contentful Paint number, which Google wants under 2.5 seconds. Then open your site on your own phone using mobile data, not wi-fi, standing outside. If you're watching a spinner on your own website, so are your customers.

Will a faster website rank higher on Google?

A bit, but that's not the main reason to fix it. Page experience is a real ranking signal, but a modest one; great content on a slow site still beats thin content on a fast one. The bigger win is that speed stops you losing the visitors you already earned. Someone who bails at the loading spinner rings the next business on the list, and that loss never shows up in any report.

Why is my WordPress or Wix site so slow?

Usually weight. A multipurpose theme built to demo a hundred layouts, a plugin or app for every small feature, and a builder that ships its whole editing engine to every visitor. Each piece is code your customer's phone has to download and run before the page settles. A disciplined WordPress site can be reasonably quick, but getting there often costs more effort than the site is worth, which is why the honest comparison is sometimes patch versus rebuild.

How much does it cost to fix a slow website in Australia?

Often nothing, at first. Resizing oversized photos and deleting unused plugins is free if you're willing to spend an afternoon on it, and it's the biggest single improvement on most slow sites. If the tests still fail after that, the foundation is the problem. A hand-coded rebuild with us is $399 for a one-page site or $899 for a multi-page site, live in 5 to 10 days, plus $30/month hosting with no lock-in contract.