Reduce TTFB on WordPress: Optimising Server, Cache and CDN

27 Mar 2026 · 9 min read

Time to First Byte (TTFB) is the time between sending an HTTP request and receiving the first byte of the response from the server. A high TTFB slows down everything — LCP, FCP and the entire page build.

Google rates a TTFB under 800 ms as "good". Many WordPress sites sit above that — often without knowing it.

Why TTFB matters so much

TTFB is the first step in the loading chain. Everything else — loading images, executing JavaScript, rendering the page — can only start once the browser has received the first byte from the server.

A TTFB of 2,000 ms means: LCP can be no earlier than 2,000 ms — even if everything after that is perfectly optimised. TTFB is therefore often the single biggest lever for LCP.

The most common causes of high TTFB on WordPress

1. No server-side caching

WordPress is dynamic — without caching, a new HTML page is generated from the database on every visit. Under heavy traffic or with slow database queries, this leads to a high TTFB.

Fix: enable page caching

The best caching plugins for WordPress:

• WP Rocket — easiest setup, very effective
• LiteSpeed Cache — free, ideal for LiteSpeed servers (configuration in detail)
• W3 Total Cache — flexible, but complex
• WP Super Cache — free, solid baseline solution

With page caching active, the HTML is generated once and then served as a static file — TTFB often drops from 500-2,000 ms to under 100 ms.

2. Slow hosting

Shared hosting splits server resources across hundreds of other websites. Response time suffers noticeably during traffic spikes.

Fix:

• Upgrade to managed WordPress hosting or a VPS
• Use PHP 8.2+ — significantly faster than PHP 7.x
• Enable OPcache — caches PHP bytecode

3. Unoptimised database

Slow database queries increase the time WordPress needs to generate the HTML.

Fix:

• Optimise the database regularly (WP-Optimize plugin)
• Limit unnecessary post revisions
• Clean up transients and expired options
• Use Redis or Memcached for object caching

4. No CDN or a poorly configured CDN

Without a CDN, every request has to reach the origin server — even from users who are geographically far away.

Fix: set up Cloudflare

Cloudflare is free and reduces TTFB significantly:

• Static assets are served from the nearest edge server
• Configure Cloudflare cache rules for HTML pages
• Argo Smart Routing for dynamic content (paid)

5. Too many active plugins

Every WordPress plugin loads on every page request — even when it isn't needed on that particular page. More plugins mean more PHP execution time.

Fix:

• Deactivate and delete plugins you don't need
• Analyse plugin performance with Query Monitor
• Optimise asset loading: load plugins only on specific pages

6. Missing PHP optimisation

PHP 7.x is significantly slower than PHP 8.x. Without OPcache, PHP has to recompile the source code on every request.

Fix:

• Use PHP 8.2 or 8.3
• Enable and correctly configure OPcache
• Enable the JIT compiler (PHP 8.0+)

Measuring and monitoring TTFB

TTFB fluctuates a lot — depending on time of day, traffic and server load. One-off measurements aren't very meaningful.

turbometrics measures TTFB on every scheduled scan and shows:

• TTFB history over time
• TTFB from multiple locations (Germany, Finland)
• Alerts when TTFB crosses a threshold
• Your visitors' real p75 TTFB via live data

Target values for WordPress

Step-by-step guide

If your TTFB is over 800 ms, work through these steps in order:

1. Check page caching — is a caching plugin active and correctly configured?
2. Measure TTFB with cache — does the value drop below 200 ms? If not: check hosting.
3. Evaluate hosting — is it shared hosting? Then upgrade.
4. Check the PHP version — at least PHP 8.1, better 8.2+.
5. Put a CDN in front — Cloudflare Free is often enough.
6. Clean out plugins — install Query Monitor, identify slow plugins.
7. Optimise the database — use WP-Optimize or a similar plugin.

Conclusion

TTFB is often the most important performance lever on WordPress. The biggest improvements come from:

1. Enabling page caching
2. Upgrading hosting
3. Putting Cloudflare in front
4. Optimising the database
5. Removing unnecessary plugins

Measure your TTFB for free now — with turbometrics you see instantly where you stand.