A slow website is one of the most damaging things you can have as a small business — and one of the least visible. Most business owners don't realise their site is slow until someone tells them, or until they notice they're not getting any enquiries from it.
Here's how to diagnose the problem and, more importantly, what to do about it.
First: how slow is slow?
Before fixing anything, measure the actual problem. Run your site through Google PageSpeed Insights — it's free, takes 30 seconds, and gives you a score from 0–100 for both mobile and desktop, plus specific recommendations.
As a rough guide:
- 90–100 — fast. Well done.
- 70–89 — reasonable, with some room to improve
- 50–69 — noticeable performance issues affecting user experience and ranking
- Below 50 — significant problems. Visitors are experiencing slow load times and Google is penalising your ranking
Most people are surprised by their mobile score — desktop scores are typically higher, but Google's primary ranking signal is mobile performance. A score of 85 on desktop and 38 on mobile is a common finding on small business websites.
The most common causes of slow websites
Images that haven't been optimised
This is the single most common cause of slow websites. A photo taken on a modern smartphone can be 8–12MB. A web page with five of those images is trying to deliver 40–60MB to every visitor — which takes a long time, especially on mobile.
The fix: Compress images before uploading. Tools like Squoosh (free, browser-based) can reduce a 5MB photo to 200KB with no visible quality loss. Better still, use modern image formats: AVIF and WebP are significantly smaller than JPEGs for equivalent visual quality. A well-configured website (like ours) handles image conversion automatically at build time.
Cheap or shared hosting
Your web server is the starting point of every page load. If the server is slow to respond — because it's shared with hundreds of other sites on a cheap hosting plan — everything downstream is slower too.
PageSpeed Insights flags this as "Reduce server response time (TTFB)" — Time to First Byte. If this is over 600ms, your hosting is a bottleneck.
The fix: Move to better hosting. Fast managed hosting, VPS hosting, or infrastructure built on a global CDN (like Cloudflare) dramatically improves response times. The cost difference between poor and good hosting is typically £10–£30/month — a trivial amount compared to the business cost of a slow site.
Too many plugins or scripts
WordPress sites in particular accumulate plugins over time — a form plugin, a slider, an SEO tool, an analytics script, a live chat widget, a cookie banner. Each one adds code that the browser has to download, parse, and execute before the page fully loads.
The fix: Audit what's actually being used and remove what isn't. Combine and minify CSS and JavaScript files where possible. Load third-party scripts asynchronously so they don't block the page render. This is more technical but has a large impact.
Render-blocking resources
Certain CSS and JavaScript files load in a way that prevents the browser from displaying the page until they've finished loading. From a user's perspective, the page just appears blank for longer than it should.
The fix: Defer or async-load non-critical scripts. Load critical CSS inline rather than from a separate file. This is a technical fix that a developer handles at build time — it's one of the things we do by default at CloudLaunch.
No caching
Every time a visitor loads a page, their browser has to request all the files from the server. Caching stores copies of those files locally (in the browser) or at a content delivery network (CDN), so repeat visitors load pages much faster.
The fix: Enable browser caching and consider adding a CDN. Cloudflare offers a free CDN tier that makes a meaningful difference to load times for visitors far from your hosting server.
Large, unnecessary page elements
Oversized hero images, full-screen video backgrounds, parallax scrolling effects, large custom fonts — all of these add weight that slows the initial load without proportionate benefit for most small business sites.
The fix: Keep visual elements purposeful. A single hero image properly compressed is fine. A 40MB autoplaying background video is not.
What a speed optimisation project looks like
If your site is slow and you're not in a position to rebuild it, a targeted performance audit and fix can address the most impactful issues without a full redesign. This typically covers:
- Image audit and optimisation
- Hosting assessment and migration if needed
- Removing unused plugins and scripts
- Enabling caching
- Fixing render-blocking resource issues
- PageSpeed score before and after comparison
For sites with fundamental performance problems — built on slow platforms or with structural issues in the code — a rebuild on a faster foundation is often more cost-effective than patching an old site.
At CloudLaunch, speed is built into every site we build — not added as an afterthought. Every site targets a PageSpeed score of 90+ on mobile. If your current site is slow and you want an honest assessment of what it would take to fix it, get in touch.