"Install a caching plugin" is the most common speed advice on the internet, and it's also the reason a lot of sites end up slower after someone "optimizes" them. Caching helps, but it's one piece of a bigger picture — and if the real bottleneck is somewhere else, a caching plugin just adds another layer of complexity on top of the actual problem.
What Actually Makes WordPress Slow
Oversized images. A product photo straight off a phone camera can be 4–8MB. Loaded at that size on every page view, it alone can account for most of your load time.
Plugin overload. Every active plugin adds its own scripts and styles, whether the page needs them or not. Ten plugins from a redesign three years ago, half no longer needed, is a common find.
No caching at all. Without it, WordPress rebuilds every page from scratch, from the database, for every single visitor — including the ones who just looked at the same page five minutes ago.
A database that's never been cleaned. Years of post revisions, spam comments, and abandoned draft data pile up in the database and slow down every query that touches it.
Hosting that's outgrown. A shared server split between hundreds of other sites has a ceiling. Past a certain traffic level, no amount of plugin tuning fixes a server that's simply out of resources.
How To Measure Speed Properly Before Changing Anything
Run your homepage and one inner page through Google PageSpeed Insights, checking the mobile score specifically — most of your visitors are on a phone, and mobile results are usually worse than desktop. Write down the load time and Core Web Vitals scores before touching anything. Without a "before" number, you can't tell whether a change actually helped or whether it just felt faster.
The Right Order To Fix Things
Fix in order of impact, not in the order a blog post lists them:
- Compress and resize images — usually the single biggest win, and the easiest to measure.
- Turn on proper caching — page caching plus browser caching, configured for your specific site rather than left on default settings.
- Remove unused plugins — fewer scripts loading means less for the browser to process on every visit.
- Clean up the database — revisions, spam, and orphaned data that add up over years.
- Reassess hosting — if the first four steps are done and the site is still slow, the server itself is likely the ceiling.
What Good Looks Like After Optimization
A well-optimized WordPress site should load in around two seconds on mobile, pass Core Web Vitals, and stay that way — not just on the day someone tuned it, but months later. That last part is the part most one-time speed fixes miss: without maintenance, plugins get added back, images get uploaded at full size again, and the site quietly slows back down over a few months.
How BS Solutions Approaches Speed Optimization
We measure first, using your real pages on real devices, so the before-and-after numbers are honest. Then we fix in the order above — images and caching first, since that's where most of the gain is, then plugins, database, and hosting if needed. You get the actual numbers, not a promise. See website speed optimization for the full service, or hosting support if the server itself turns out to be the bottleneck.
Frequently Asked Questions
I installed a speed plugin and my site got slower. Why?
Speed plugins can conflict with your theme or other plugins, or apply settings that don't suit your specific site. They're a tool, not a guaranteed fix — the underlying cause still needs diagnosing.
Will my hosting company's word that "everything's fine" tell me anything useful?
Hosting dashboards usually measure server response time, not the full page load a visitor actually experiences. The two can tell very different stories.
Does speed really affect Google rankings?
Yes — Core Web Vitals are a confirmed ranking factor, and slow pages also directly increase the number of visitors who leave before the page even finishes loading.
Want to know your real numbers?
Send your link — we'll measure it properly and tell you what's actually slowing it down.