“Speed” gets treated as one problem with one plugin-shaped solution. In practice it’s five or six separate problems, and most sites are only slow because of one or two of them.
What actually moves the needle
- Image size. Still the single biggest win on most sites. Correctly sized, modern-format, lazy-loaded images fix more performance problems than anything else on this list.
- Server response time. No amount of front-end optimization fixes a backend that takes 800ms to respond before the browser has even started rendering.
- Unused JavaScript and CSS. Shipping an entire framework’s worth of styles for three components that are actually used on the page.
- Database query efficiency. Especially on WordPress and other CMS-driven sites, where a theme or plugin running dozens of unoptimized queries per page is common and invisible until you actually measure it.
What usually doesn’t help as much as advertised
Installing a caching plugin without addressing the underlying causes treats the symptom, not the problem — it can mask a slow page for repeat visitors while doing nothing for the first load that actually determines whether someone bounces. The same goes for CDNs: genuinely useful for static assets, but not a fix for a server-side bottleneck.
Measure before you optimize
A real audit — Core Web Vitals, a waterfall chart of what’s actually loading and when — tells you which of these problems you actually have. Guessing and installing plugins to see what sticks is how sites end up with five overlapping performance plugins and no real improvement.