Stop Guessing: Diagnosing & Fixing WordPress Performance Problems
summary
Concrete steps to stop guessing: measure your time to first byte (goal under 500 ms, ideal 50–150 ms) with WebPageTest and Chrome DevTools, profile PHP/WordPress with New Relic to find slow plugins or hooks (example: a Jetpack hook adds ~2 seconds), optimize images and HTTP/2, and only use page caching as a last resort. Migrating to a faster host can yield dramatic wins (one example becomes 5× faster with no code changes). Tools shown include a TTFB scanner, migration plugins, and automated site crawls.
AI-written summary · about
chapters (12)
- 0:00Introduction and speaker background
- 2:32Why performance matters
- 7:46Measuring time to first byte
- 13:48Hosting providers impact on speed
- 18:17Migrating to optimized hosting
- 24:13Diagnosing server response time
- 29:41Profiling WordPress with New Relic
- 31:25Optimizing page loads beyond TTFB
- 35:02Understanding caching types
- 37:10Summary and final recommendations
- 37:54Live demo of performance tools
- 42:49Q&A session
