A real-world breakdown of the exact optimizations that moved the needle.
WordPress powers over 43% of the web for a reason — it’s flexible, mature, and battle-tested. But that flexibility cuts both ways: most performance issues I see in client audits come from accumulated plugin debt, unoptimized themes, and database queries that quietly compound over years.
The real bottlenecks
In nearly every audit I run, the top three offenders are the same: render-blocking scripts in the head, oversized hero images, and uncached admin-ajax calls. None of these require a rebuild — they require attention.
I start every optimization engagement with a measured baseline. Lighthouse alone isn’t enough; I run WebPageTest with mobile throttling, then dig into the waterfall to find the real bottleneck.
What actually moved the needle
For the project that inspired this post, three changes did 80% of the work: deferring non-critical JS, swapping to native lazy-loading on images below the fold, and moving to a properly configured page cache with edge caching at Cloudflare.
LCP went from 5.6s to 1.4s. Conversions tracked up 18% in the following two weeks, even without any other marketing changes.
Takeaways
Speed isn’t a one-time project — it’s a discipline. Set a budget, measure it, and treat regressions like bugs. Your future self (and your customers) will thank you.