What actually makes a website slow, and why it costs you

Most business owners know their website feels slow. Far fewer know why, or how much that slowness is quietly costing them.

It's worth starting with the stakes, because "slow" sounds like a cosmetic complaint and it isn't. When a page takes too long to load, people leave before they ever see it and on mobile, where most of your visitors are, patience is shorter still.

Speed also shows up in search. Google treats page experience as a ranking factor, though a modest one. Relevance matters far more, and a good site won't rank badly for being slow alone. The bigger cost is closer to home: visitors who leave before the page renders never became customers, and you never see them in your analytics.

So what actually makes a site slow? A handful of culprits account for most of it.

The usual suspects

• Oversized images. The number one offender by a wide margin. A photo straight off a phone can be several megabytes and far larger in dimensions than it's ever displayed at. Multiply that across a page and the browser is downloading enormous files to render small pictures. Properly sized and compressed images alone often transform a site's speed.
• Too many scripts and plugins. Every add-on, tracker, chat widget, and third-party embed is more code the browser has to fetch and execute before the page is ready. Sites that have accumulated plugins over years carry a lot of weight most visitors never benefit from.
• Bloated builders and themes. Some platforms and templates generate heavy, inefficient code under the hood. The site looks fine, but it's shipping far more than it needs to just to render.

• No caching or CDN. Without caching, the site repeats work it could have reused. Without a content delivery network, visitors far from the server wait longer for everything. Both are invisible until you measure them.
• Heavy fonts and embeds. Loading many font weights, or dropping in full video and map embeds that load whether or not anyone scrolls to them, quietly adds seconds.

How to actually know

You don't have to guess. Google's PageSpeed Insights will assess any site for free, on both mobile and desktop.

One thing worth understanding about the report: it shows two different things. The lab score is a simulated test run on demand. The field data comes from real visitors over the previous 28 days, and that's what Google actually uses. They often disagree, a site can score poorly in the lab and fine in the field, or the reverse. Trust the field data where it's available.

Pay particular attention to mobile. It's usually the lower of the two, and it's the one that matters most. That's where your visitors are, and it's what Google weighs most heavily.

As a rough benchmark, a well-built site should render its main content in under 2.5 seconds on mobile. Under 1.5 is achievable and noticeably better.

What to fix first

Not everything is worth chasing. If you're prioritising:

1. Images. Usually the biggest problem and the easiest win.
2. Scripts and plugins. Cut what you don't actually need.
3. Hosting, caching, and delivery. Slower to change, but compounding.

That sequence tends to recover most of the lost speed for the least effort.

Speed isn't a technical vanity metric. It's something your customers feel the moment they arrive. Quietly deciding, before they read a word, whether they stay.

Most sites have more speed available than their owners realise, and it's usually recoverable without a rebuild. If you want to know what's slowing yours down, get in touch.