Why Is My Website Slow?

Here's the uncomfortable bit, and it's the reason slow websites stay slow for months without anyone noticing: your site is almost certainly not slow for you.

You've visited it a hundred times, so your browser has half of it sitting in cache. You're probably on decent broadband, on a desktop, quite possibly geographically close to wherever it's hosted. You know where you're going and what you're waiting for, which makes the wait feel shorter than it is.

Your visitor is on a phone, on a patchy connection, somewhere in a queue, and has never seen your site before. They have no idea what's meant to appear, no reason to wait for it, and nothing invested in staying. That person is who your site's speed is genuinely measured against, and you are the worst possible judge of their experience.

So let's work out what's actually going on.

What "slow" even means

Forget scores and metrics for a moment. From a visitor's point of view, there are only three questions, asked unconsciously in about two seconds:

1. Is anything happening? Blank white screen or signs of life.
2. Is this the thing I wanted? The main content, the headline, the product image.
3. Can I use it yet? Buttons that respond, a page that doesn't jump around while you're trying to tap something.

Every speed metric you'll ever see is a proxy for one of those three. If your site fails question one, nothing else matters, because they're already gone.

There's a second thing worth knowing, and it's why so many people get a clean bill of health and stay slow anyway: averages lie. A site can be perfectly quick most of the time and genuinely painful during the hours that matter, on the connections that matter, in the countries that matter. One test, run once, from one place, tells you almost nothing. Hold that thought, because it comes back at the end.

The usual suspects

Slow sites are rarely mysterious. In practice it's nearly always some combination of the following, listed roughly in order of how often they're to blame.

1. Images nobody ever compressed

The single most common cause, and the most boring.

Someone uploaded a 4MB photo straight from a camera or a stock site, the theme scaled it down to display at 600 pixels wide, and every visitor still downloads all 4MB of it. Multiply that by the eight images on your homepage and you've built a page that weighs more than a mobile game.

The fix is unglamorous: resize images to the size they'll actually be displayed at, compress them, and use a modern format like WebP. Most platforms will do this automatically now if you let them. It's usually the biggest single win available and it takes an afternoon.

2. Third-party scripts

This is the one people underestimate, badly.

Every tool you bolt onto your site loads its own code from someone else's server. The live chat widget. Google Analytics. The Facebook pixel. Hotjar. That A/B testing tool you trialled in 2023 and never removed. A cookie consent banner. A review widget. A font service.

Individually, each one feels harmless. Collectively they're often the majority of your load time, and here's the part that stings: you don't control any of them. If a chat provider has a bad afternoon, your site has a bad afternoon. Their outage becomes your slow page.

Go and look at what's actually loading on your site right now. Most people find at least two things they'd completely forgotten about and don't need.

3. Your hosting

Cheap shared hosting means your site sits on a server alongside a few hundred others, competing for the same resources. When one of your neighbours has a busy day, you get slower, and there's nothing you can do about it.

The signal to look for is a slow first response, meaning a long pause before anything at all begins loading, even on a simple page. That's the server thinking rather than the page being heavy. If moving to better hosting fixes it, it was never a code problem.

4. Theme and plugin bloat

Multipurpose themes are built to do everything for everyone, which means they load the code for the portfolio grid and the event calendar and the booking system whether you use them or not. Same with plugins: twenty active plugins is twenty sets of scripts and styles.

You don't need to strip your site back to nothing. You do need to be honest about which of those things earn their place.

5. The small stuff that adds up

Custom fonts loading before any text appears. Redirect chains where a URL bounces through three destinations before landing. Video backgrounds. Embedded maps. Animation libraries used for one fade effect.

None of these is a crisis on its own. That's rather the point.

It's almost never one big thing

This is the mental shift that makes the whole problem tractable.

People go looking for the one broken thing that's ruining everything, don't find it, and conclude their site is just "a bit slow, that's normal". It isn't one thing. It's four hundred milliseconds of unoptimised images, plus six hundred from scripts you forgot about, plus a sluggish server response, plus a font that blocks rendering. Each one is individually defensible. Stacked, they're the difference between a site that feels instant and one that feels broken.

Which is good news, because it means you don't need a rebuild. You need to remove four small things.

How to check properly

If you take one practical instruction from this post, take this one: test your site the way your visitors experience it, not the way you do.

That means:

• On mobile, since that's the majority of traffic for most sites and it's also the version Google judges you on.
• On a throttled connection, not your office wifi. Browser dev tools will simulate slower speeds for you.
• In a private or incognito window, so you're not benefiting from your own cached files.
• From somewhere else in the world, if you have visitors elsewhere. A site hosted in London can be sluggish in Sydney for reasons that have nothing to do with your code.
• On your real pages, not just the homepage. Homepages get optimised because that's what people test. Your slowest page is usually a product page or a blog post loaded with images.

The thing nobody mentions: speed drifts

Here's what actually happens to most websites.

You fix everything. Images compressed, scripts trimmed, hosting sorted. The site flies. You feel good about it and you stop thinking about it, because it's fixed.

Then in March, marketing adds a tracking pixel. In April, someone installs a plugin to run a popup. In June, a third-party widget you've had for years pushes an update that doubles its own file size. In August your host quietly migrates you to a busier machine.

Nobody did anything wrong. There was no single moment where the site broke. But by autumn you're two seconds slower than you were in February, and you have no idea, because you last checked in February.

Site speed isn't a fixed property of your website. It's a moving number, affected by decisions made by people who don't think of themselves as making performance decisions, and by companies you've never spoken to. Checking it once a quarter tells you what it was on the day you checked.

This is exactly the gap that continuous monitoring fills. Tools like WebsitePulse.io check your site's speed and availability on an ongoing basis from real locations, so a gradual slide shows up as a trend line you can see rather than a vague sense that things feel sluggish lately. The same applies to outright downtime, which is just the most extreme version of the same problem: you want to hear about it from a monitor, not from a customer.

The principle underneath it: you can't improve what you're not measuring, and you can't measure something that changes weekly by checking it twice a year.

If you only do one thing

Open your site on your phone, on mobile data, in a private window, and count the seconds before you can read something useful.

That number is the one your visitors are actually experiencing. If it's over three, start with your images, then go and look at what third-party scripts are loading. That'll cover most of the gap for most sites.

And once you've fixed it, put something in place to tell you when it drifts back. Because it will.