TTFB: How to Speed Up Your Server Response Time

Time to First Byte (TTFB) is the time between a browser requesting a page and receiving the first byte of the response from the server. It is the foundation of all page speed metrics — a slow TTFB means every subsequent step in loading your page is delayed.

Google considers TTFB a key performance metric. Their recommended target is under 800ms, with 200ms being excellent. A TTFB over 1500ms is a serious performance issue.

What Causes Slow TTFB?

Slow server hardware is the most common cause of consistently slow TTFB. Shared hosting on overloaded servers, or underpowered VPS configurations, creates a fundamental bottleneck. No amount of front-end optimisation can overcome a server that takes 2 seconds to respond.

No server-side caching means every request requires the server to query a database and build the HTML from scratch. With caching, the server builds a page once and serves the pre-built version to subsequent visitors in milliseconds.

Slow database queries and unoptimised application code add overhead to every page load. WordPress sites with many active plugins are particularly susceptible — each plugin can add dozens of database queries.

Geographic distance creates unavoidable latency. A server in the US serving users in Australia will always have 150-200ms of latency from the physical distance alone. A CDN with edge nodes closer to users is the solution.

The Fastest Fixes

Enable Server-Side Caching

This is the single biggest TTFB improvement for most CMS-based sites. For WordPress, WP Rocket, W3 Total Cache, or LiteSpeed Cache (if on LiteSpeed server) are effective options. Properly configured, caching can reduce TTFB from 800ms to under 100ms.

For custom sites, Varnish Cache sits in front of your application server and serves cached responses without touching PHP or the database. Nginx FastCGI cache is built into Nginx with PHP-FPM and is highly effective.

Upgrade Your Hosting

Shared hosting has fundamental TTFB limitations that caching cannot fully overcome. A move to managed WordPress hosting (Kinsta, WP Engine) or a well-configured VPS typically reduces TTFB by 60-80%.

Use a CDN

A CDN caches your pages globally and serves them from the nearest server to each user. Cloudflare's free tier includes basic page caching and significantly reduces TTFB for visitors far from your origin server.

Reduce Database Queries

On WordPress sites, deactivate and delete unused plugins. Each active plugin adds processing overhead to every page load. Use Query Monitor plugin to identify slow database queries and work with a developer to optimise them.

Diagnosing TTFB

Use Chrome DevTools Network panel to measure TTFB. Load your page, click on the first HTML document request, and look at "Waiting for server response" in the Timing section.

For production monitoring, PageSpeed Insights and GTmetrix both show TTFB in their reports. Google's own threshold is that TTFB over 800ms needs improvement, while TTFB over 1800ms is poor.

After Fixing TTFB

Improving TTFB has a cascading effect — every other performance metric improves because the browser gets a head start. A 500ms TTFB reduction translates to roughly 500ms improvement in LCP, FCP, and overall load time, without changing any front-end code at all.