When a business owner tells us their site is slow, they usually blame hosting. Occasionally that's the problem. Far more often, it's four other things — and they're worth knowing about before you pay anyone to fix them.
Images nobody resized
This is the single most common cause, and it is almost always the cheapest to fix.
Someone uploads a photo straight from a phone camera. That file is 4,000 pixels wide and four megabytes. It gets displayed in a box 400 pixels wide. The browser still downloads all four megabytes, then throws away 90% of the detail.
Put twelve of those on a homepage and you have a 48MB page. On a mid-range Android over 4G, that is not a slow site — that is a broken one.
The fix: resize images to roughly the size they'll actually display, compress them, and serve modern formats like WebP. On most sites this alone cuts load time by more than half, and it needs no rebuild.
Plugins you forgot you installed
A typical WordPress site accumulates 20–40 plugins. Each one can add its own CSS, its own JavaScript, and its own database queries to every single page — including pages that don't use the plugin at all.
A slider plugin used once on the homepage will happily load its 300KB of JavaScript on your contact page too.
The fix: audit what's installed, remove what isn't used, and replace the heavyweight plugins doing one small job. Expect to remove more than half.
Third-party scripts
Analytics, chat widgets, Facebook pixels, heatmaps, review badges, font services. Each one is a request to someone else's server, and your page often waits for it.
The painful part is that you have no control over their speed. If a chat widget's server is having a bad day, your site is slow that day.
We build with this in mind: on this site, the booking calendar doesn't load at all until you click a button. It keeps roughly 100KB of someone else's JavaScript off the page for the 95% of visitors who never open it.
The fix: list every third-party script and justify each one. Load what's left after the page is usable, not before.
Hosting — genuinely, sometimes
Cheap shared hosting puts hundreds of sites on one server. When a neighbour gets a traffic spike, your site slows down. And if your server is in another continent, every request pays that distance twice.
But notice this is fourth on the list. Moving a bloated site to a faster server makes a bloated site load slightly sooner. Fix the first three, then look at hosting.
The fix: for most business sites, a modern static host is faster than a traditional server and often free at small scale, because pages are served from whichever data centre is nearest to the visitor.
How to find out what your problem is
Run your URL through PageSpeed Insights. Use the mobile score, not desktop — that's what most of your visitors are on.
Two numbers matter more than the overall score:
- Largest Contentful Paint (LCP) — when the main content appears. Aim under 2.5 seconds.
- Cumulative Layout Shift (CLS) — how much things jump around while loading. Aim under 0.1.
The report lists the specific files causing problems. That list is what a developer should be working from — if someone quotes you for "speed optimisation" without referencing it, ask why.
What this is worth
Roughly half of mobile visitors abandon a page that takes more than three seconds. If your site takes nine, you are losing most of the traffic you already paid to attract — before anyone reads a word about what you sell.
That's what makes performance work unusual: it doesn't need more traffic or more ad spend. It just stops you losing what you already have.
If you'd like to know what's slowing your site down specifically, our web development service page explains how we approach it, or book a scope call and we'll run through your report with you.