Why speed is a revenue issue, not a vanity score
Speed is not about chasing a number in a testing tool — it is about whether customers stay long enough to buy. Deloitte’s Milliseconds Make Millions study, run with Google, found that improving mobile load time by just 0.1 seconds lifted retail conversions by 8.4% and average order value by 9.2%. Earlier Google research found 53% of mobile visits are abandoned if a page takes longer than three seconds to load.
So speed work is conversion work. The goal is fast, responsive, stable pages where customers decide and act — measured by Google’s Core Web Vitals (load, responsiveness, and visual stability), not just a single lab score.
Start with the pages that make money
The homepage matters, but it is rarely where the money is decided. The highest-value pages are usually product, service, checkout, contact, quote, booking, and login pages. Optimise those first — a fast homepage and a slow checkout still loses sales. Fix the pages where visitors act, then work outward.
The fixes that actually move the needle
Most WordPress speed wins come from practical cleanup, not clever hacks. In rough order of impact for a typical business site:
- Compress and correctly size images — oversized images are the most common single cause of slow WordPress pages.
- Set up caching properly, and serve static assets through a CDN.
- Cut plugin overlap and stop scripts loading on pages that never use them.
- Defer or delay non-critical third-party scripts (chat, ads, trackers) carefully, without breaking interaction.
- Check hosting resources and database health — a cheap, overloaded server caps everything else.
What not to do
Do not stack optimisation plugins until the site breaks. Three caching or “speed” plugins fighting each other can hide the real problem, make pages feel laggy to tap (a Core Web Vitals fail in itself), and create conflicts that are hard to unpick. One well-configured tool almost always beats a pile of them — which is also why a plugin audit usually comes before speed work. Measure first, change one thing at a time, and re-measure — guessing is how sites end up slower than when they started.
Speed levers by effort and impact
Where to spend your time first. The biggest wins are usually the least glamorous.
| Lever | Effort | Typical impact |
|---|---|---|
| Image compression & sizing | Low | High — often the single biggest win |
| Caching + CDN | Low–medium | High |
| Remove/replace heavy plugins | Medium | High for responsiveness (INP) |
| Defer non-critical scripts | Medium | Medium–high, but easy to overdo |
| Upgrade hosting / fix database | Medium–high | High when the server is the bottleneck |
| Stacking more speed plugins | Low | Often negative — avoid |
Speed mistakes that backfire
- Optimising the homepage while checkout, product, and form pages stay slow.
- Stacking multiple caching/optimisation plugins until they conflict and slow the site down.
- Chasing a perfect lab score while real mobile visitors still wait.
- Uploading huge images and relying on the browser to shrink them.
- Treating speed as a one-time project instead of something that drifts back without upkeep.
How we keep a site fast (and keep it that way)
In our experience, speed is easy to win once and easy to lose quietly. A new plugin, an unoptimised batch of images, or an extra tracking tag can erode months of work without anyone noticing until conversions dip. So we treat performance as a maintained state under an ongoing WordPress care plan — measured on real devices, watched on the pages that matter, and re-checked after the changes most likely to break it.
- Prioritise speed work on revenue pages, not just the homepage.
- Keep one well-configured caching/optimisation setup rather than several competing tools.
- Re-check Core Web Vitals after plugin, theme, and content changes.
- Watch image sizes and third-party scripts, the two things that quietly creep back.
Frequently asked questions.
What is a good WordPress page speed score?
A score is a guide, not the goal — real customer experience matters more. Aim to pass Core Web Vitals (LCP 2.5s or less, INP 200ms or less, CLS 0.1 or less) on the pages customers use, and focus on fast, responsive, stable conversion paths rather than a perfect number.
Can plugins make WordPress slow?
Yes — plugins add scripts, database queries, and admin overhead, and they can conflict with one another. Quality and how each plugin loads matter far more than the raw count. Removing a few heavy, script-laden plugins often does more than any single tweak.
Does faster hosting fix WordPress speed?
It helps when the server is the bottleneck, but hosting alone rarely fixes everything. Oversized images, page-wide scripts, and missing caching usually account for more of the delay than the server does. Fix those alongside hosting.
Is speed really worth the effort?
For any site that sells or generates leads, yes. Deloitte’s research found a 0.1-second faster mobile load lifted retail conversions 8.4% and order value 9.2%, and slow pages lose visitors before they ever see your offer.
Research sources.
This guide was checked against current platform and search documentation before publication.