A slow website isn’t a mystery, it’s a bottleneck. When you click and nothing happens for three seconds, something specific is causing it. The hard part isn’t fixing it; it’s finding out which of the usual suspects it is.
The usual suspects
Most slow sites I look at have one of these problems:
- Unoptimized images. A hero image saved from a template can be 2–5 MB. That alone can double your load time.
- Too many JavaScript bundles. Five analytics scripts, a slider library, a font loader - each one adds a network round trip.
- No caching. Every visitor re-downloads everything, every time.
- A slow or overloaded server. Shared hosting that worked five years ago may not survive your traffic now.
- Render-blocking CSS. Stylesheets that must finish downloading before the page can paint.
Diagnose it properly
Guessing is a waste of time. Start with the tools:
- PageSpeed Insights - a free, server-side analysis of your real site. It gives a Core Web Vitals breakdown.
- WebPageTest - more detailed waterfalls: exactly which request was slow, and why.
- Browser DevTools - the Network panel shows request sizes and timings in real time.
The numbers that matter
Core Web Vitals are the three metrics Google uses for ranking:
| Metric | What it measures | Good |
|---|---|---|
| LCP | Largest contentful paint, when the main content appears | under 2.5s |
| INP | Interaction to next paint, how responsive the page feels | under 200ms |
| CLS | Cumulative layout shift, how much the layout jumps | under 0.1 |
Fix the biggest offender first. Usually that’s an image or a bundle, not your hosting.
What a fix looks like
For most sites, a realistic outcome after optimization:
- Images compressed and served in the right format: 4.2 MB → 0.9 MB
- JavaScript deferred or removed: one or two fewer blocking scripts
- Caching headers configured: repeat visits load from cache
If you’d rather not dig into the waterfall yourself, that’s exactly what a technical audit is for, we run the checks and hand you a list, in plain language, of what’s slow and what it costs to fix.
The one-sentence version: your website isn’t randomly slow. Find the bottleneck, fix it in priority order, and measure again.