Website speed isn't a vanity metric — it's a revenue metric. Visitors who wait more than 3 seconds for a page to become interactive leave at materially higher rates. Here's what's causing slow sites and how to fix them.
The maths
A few benchmarks worth knowing:
- A 1-second delay in page load drops mobile conversions ~7% on average
- Sites loading in 1 second convert ~3x better than sites loading in 5 seconds
- Google Search prefers fast sites (Core Web Vitals are a ranking factor since 2021)
- Bounce rate rises sharply between 1 and 3 seconds of load time
For a UK small business getting 500 visitors a month, the difference between a 2-second site and a 6-second site is typically 8-12 lost enquiries a month. At a £2,000-£10,000 lifetime client value, that's serious money.
What's making most sites slow
Top causes in 2026, in rough order:
- Massive unoptimised images. A 4MB JPEG hero image is still common. WebP at 200KB looks identical.
- Render-blocking JavaScript from analytics, chat widgets, cookie banners loading synchronously
- Web fonts loading 8 weights when 2 would do
- Third-party scripts — Facebook Pixel, Hotjar, marketing automation — piling up
- Bad hosting — shared hosting with slow servers, no CDN
How to fix it without a rebuild
The 80/20 of speed improvements:
- Compress and reformat images — use WebP, serve responsively via `srcset`, lazy-load below-fold
- Reduce font weights to the minimum — usually 2 weights is enough for most sites
- Defer non-critical JavaScript — analytics, chat, marketing pixels should load after the page is interactive
- Inline critical CSS — the styles needed for above-the-fold paint
- Upgrade hosting — move from shared hosting to a modern platform with global CDN (Vercel, Cloudflare Pages, Netlify)
Most UK small business sites can be made 2-3x faster within a week without changing a line of design.
When a rebuild is the right answer
Speed problems sometimes indicate architectural issues that fixes can't paper over. Telltales:
- Site is built on a 2014 WordPress theme with 30+ plugins
- Page weight is over 5MB even before images
- TTFB (time to first byte) is over 1 second consistently
- You can't deploy changes without something breaking
In these cases a proper rebuild on a modern stack pays back faster than incremental fixes.
Measuring it properly
Three free tools:
- PageSpeed Insights (Google's tool) for Core Web Vitals snapshot
- GTmetrix for waterfall view of what's loading
- WebPageTest for the most thorough breakdown
Don't trust your own perception — your laptop, browser cache and broadband are all faster than your customers' devices and networks.
Sector context
For trades and emergency services where visitors arrive in distress mode, speed is the difference between a call and a competitor. For healthcare where booking is the goal, speed lifts conversion meaningfully. For e-commerce, speed correlates almost linearly with revenue.
Common mistakes
- Optimising for Lighthouse scores while ignoring real user metrics
- Adding "speed plugins" that themselves add bloat
- Not measuring before and after changes
A note from the Bloomorbit studio
Every Bloomorbit site we build hits Lighthouse 85+ on Performance by default. If your current site is dragging, a free audit tells you exactly which fixes will move the needle first.