How to Reduce TTFB on WordPress
Time to First Byte measures how quickly your server responds. Under 200ms is great, 200–500ms is acceptable, above 800ms and every other speed fix is fighting uphill.
1. Turn on full-page caching
If WordPress is running PHP on every request, TTFB will never be fast. A page cache serves static HTML in ~50ms — 10× faster than a fresh PHP render. Every managed WordPress host offers this; enable it before anything else.
2. Put a CDN in front of HTML, not just assets
Most CDNs cache CSS, JS, and images by default — not HTML. Enable HTML caching (Cloudflare APO, BunnyCDN Perma-Cache, etc.) so visitors hit the edge instead of your origin.
3. Use a modern PHP version
PHP 8.3 is roughly 2× faster than PHP 7.4 on real WordPress workloads. If your host still runs 7.x, switch versions in cPanel or ask support.
4. Enable object caching
Redis or Memcached caches database query results in memory. On plugin-heavy sites (WooCommerce especially) this can cut uncached TTFB in half.
5. Kill slow plugins
Install Query Monitor. Sort by slowest query. If one plugin owns most of them, replace or remove it. WordPress is not slow — plugins are.
6. Move to a real host
Cheap shared hosting ($3/month) throttles CPU during peak hours; nothing you configure at the app level will fix it. Managed WordPress hosts (Kinsta, WP Engine, Rocket, Cloudways) publish TTFB benchmarks — pick one under 200ms.
See your TTFB in seconds
AITurboWordPress reports TTFB alongside every scan and tells you which lever will move it fastest for your site.
Run a free scan