Why Is My Website Slow? How to Test and Fix It

A slow website costs you customers who never tell you why they left. Someone taps a link, waits, and moves on to the next result before the page has even finished loading, and there's no error message, no complaint, just one fewer person who ever saw what you actually offer. Here's how to find out if that's happening on your own site, and what actually causes it.

Short version: test your actual page speed with a free tool, not a guess, and the fix is almost always oversized images, unnecessary scripts, or cheap hosting, usually all three at once.

Why speed actually matters

Google has used page loading speed as part of how it ranks websites for years, particularly for mobile search, which is where most local searches happen. Beyond ranking, there's the more immediate problem: people simply don't wait. Someone searching for a tradie, a cafe, or a shop on their phone is usually trying to make a decision right now, and a page that takes several seconds to load loses that person to whichever other result actually worked. This ties directly into the kind of "near me" search covered in how to show up on Google when someone searches "near me", someone finding you that way is often standing somewhere deciding in real time, and a slow page is often the reason they never actually see what's on it. A slow site doesn't just rank worse, it actively pushes away the visitors who do find it.

How to actually test your site's speed

Go to pagespeed.web.dev, Google's own free testing tool, and paste in your website's address. Click analyze and wait a few seconds. You'll get two scores out of 100, one for mobile and one for desktop, along with a specific list of what's actually slowing the page down. Test the mobile score first, since that's both what most visitors are using and what Google prioritises when it comes to ranking. It's also worth simply loading the site on your own phone using mobile data rather than wifi, since that's closer to what a lot of visitors actually experience, and a slow load in real life is sometimes more convincing than any score on a report.

How to read what it gives you back

A score of 90 or above is considered good. Anywhere from 50 to 89 means there's real room to improve. Below 50 means the site is genuinely working against you. It's worth noting the mobile and desktop scores can be quite different, sometimes a site tests well on desktop and poorly on mobile, and since mobile is what matters most for local search, that's the number to pay closer attention to if the two don't match. Don't worry about understanding every technical term in the report, focus on the specific recommendations it lists, since those point directly at what's actually causing the slowdown on your particular site rather than a generic guess.

What the technical terms in the report actually mean

A few terms in the report are worth knowing. Largest Contentful Paint is how long it takes for the main content on the page, usually a big image or a headline, to actually appear. Cumulative Layout Shift measures whether things jump around while the page loads, text shifting because an image above it just finished loading in, which is exactly as annoying to a visitor as it sounds. Interaction to Next Paint measures how quickly the page responds once someone actually taps something. None of these need to be memorised, but knowing roughly what they measure makes the rest of the report far less intimidating to read.

The most common cause: oversized images

This is, by a wide margin, the single most frequent reason a small business website is slow. A photo taken straight from a phone and uploaded without resizing can be several megabytes, when a properly sized version of the same image would be a fraction of that with no visible difference in quality. Multiply that across a handful of photos on a homepage and the page has to load tens of megabytes before someone can even see it. It's worth testing more than just the homepage too, a gallery or services page with several photos is often the actual slowest page on a site, even when the homepage itself tests fine. The fix is straightforward: resize and compress images before uploading them. Most website platforms also offer some automatic compression, but starting with a properly sized file makes the biggest difference.

The second cause: too much running in the background

Tracking scripts, chat widgets, embedded social feeds, and page builder plugins all add code that has to load before the page is usable, even if the visitor never interacts with any of it. It's common for a site to accumulate several of these over a couple of years, a booking widget trialled once and forgotten, a chat tool nobody actually monitors anymore, each one small on its own but adding up. A site can look simple and still be quietly loading a dozen scripts in the background for tools that were added once and never removed. Reviewing what's actually installed and removing anything that isn't earning its place is often worth more than any other single fix.

The third cause: where the site is actually hosted

Cheap, oversold hosting, the kind sometimes bundled into subscription website builders, can genuinely be slower than proper hosting, especially under any real traffic, since a lot of other sites are often sharing the same limited resources behind the scenes. This is worth checking directly rather than assuming, since it's one of the few speed issues that isn't something you can fix yourself by changing content on the page, it comes down to what's actually running the site behind the scenes, not what's visible on it.

Test again after any changes

Speed isn't something you fix once and forget. Adding a new photo gallery, a booking widget, or a fresh page builder plugin down the track can quietly undo the improvements from a previous fix. It's worth running the same test again after any noticeable change to the site, rather than assuming it's still fine because it was fine six months ago.

What to actually do with this

Run the test, note the mobile score, and work through the specific recommendations it gives rather than trying to fix everything blind. Start with images, since that's the fix most business owners can make themselves in an afternoon with no technical help required. If the score is still poor after that, the scripts and hosting questions above are the next place to look, and that's usually where a developer's help actually earns its cost.

Where ForgePoint fits in

Every site we build starts lean by default, properly sized images, no unnecessary scripts left running, and hosting that's actually built for the job rather than bundled cheaply into a subscription. If you've run the test above and don't love your score, that's a genuinely quick thing to fix on most sites, and worth a conversation before assuming a full rebuild is the only option. Speed is also one of the few things on this blog that's genuinely free to check for yourself right now, without needing to trust anyone's opinion about it first.