Most site speed advice starts with minifying JavaScript, which for a typical small business site is roughly the last thing that matters. Here's the order actually worth working through, and roughly what each step tends to buy you.
First, measure the right thing
Run the site through a real page speed tool and look at Largest Contentful Paint — how long until the main thing appears. That's the number that correlates with people leaving. A perfect score on a synthetic test means very little if the hero image takes four seconds on a phone.
Test on mobile, on a throttled connection. Testing on your desktop over office fibre will tell you everything is fine, and it isn't.
1. Images (usually most of the problem)
On the majority of sites we audit, images are the single largest cause. Not because there are too many, but because they're being served at full camera resolution and scaled down in the browser. A 4,000-pixel-wide photo displayed in a 400-pixel box is downloading roughly a hundred times more data than it needs.
Resize to roughly twice the display size, convert to WebP, add width and height attributes so the layout doesn't jump, and lazy-load anything below the fold. This alone routinely halves page weight and it's the cheapest work available.
2. Hosting
Cheap shared hosting is cheap because you're sharing a server with a lot of other sites. Time-to-first-byte over half a second usually means the server is thinking too hard before it sends anything — and no amount of front-end optimisation fixes a slow server.
This is the one people resist because it costs money monthly rather than once. It's also frequently the biggest single improvement available.
3. Third-party scripts
Chat widgets, analytics, tag managers, tracking pixels, review embeds, font loaders. Each one is a request to somebody else's server, and your page waits. It's common to find four or five of these where two are actively used and the rest were added for a campaign that ended eighteen months ago.
Audit what's actually loading. Remove anything nobody looks at.
4. Plugins, if it's WordPress
Not the count — the weight. A single page builder can add more front-end code than twenty simple plugins. Look at what each one loads on every page versus only where it's needed. Sliders, form builders and anything with animation are the usual suspects.
5. Fonts
Every custom font is a download that blocks text from rendering. Two families with a couple of weights each is plenty. Use font-display: swap so text appears immediately in a fallback rather than sitting invisible, and don't load nine weights when you use three.
6. Caching
Worth doing, genuinely helps, and deliberately last on this list — because caching a bloated page just serves the bloat faster. Fix the weight first, then cache.
The honest summary
Work top to bottom and stop when it's fast enough. Most sites get the majority of the available improvement from images and hosting alone, which are steps one and two for a reason. If you've done both and it's still slow, then it's worth getting into the code — and at that point you're solving a real problem rather than a guessed one.
Run a free audit and see where yours stands.
Audit my site →