TTFB
PerformanceTTFB is a performance metric that measures the time between a user requesting a web page and the browser receiving the first byte of the server response. It reflects delays from DNS lookup, TCP/TLS negotiation, server processing, and initial network latency. Lower TTFB generally indicates faster backend responsiveness and can improve perceived speed, especially for dynamic sites and global audiences.
How It Works
TTFB starts when a browser initiates a request (for example, navigating to a URL) and ends when the first byte of the HTTP response arrives. The total includes several stages: DNS resolution (finding the IP address), establishing the connection (TCP) and, for HTTPS, completing the TLS handshake, plus any redirects before the final request is made. Each stage adds time, especially when the visitor is far from the server or the network path is congested.
After the connection is ready, the server must accept the request, route it through the web server (such as Nginx or Apache), and run any application logic. For dynamic sites, this can include executing PHP, querying a database, calling external APIs, or generating templates. Caching can dramatically reduce this processing time by serving prebuilt responses, while overloaded CPU, slow storage, limited PHP workers, or inefficient database queries can increase TTFB. CDNs can also lower TTFB by serving cached content from edge locations closer to visitors.
Why It Matters for Web Hosting
TTFB is a practical way to compare how quickly hosting plans can begin responding under real conditions. When evaluating providers, a consistently low TTFB often points to better server resources, optimized stacks, effective caching, and closer or more distributed infrastructure. High or inconsistent TTFB may signal resource contention on shared hosting, insufficient CPU/RAM, slow databases, or missing performance features like full-page caching, HTTP/2 or HTTP/3 support, and CDN integration.
Common Use Cases
- Benchmarking hosting plans by measuring backend responsiveness from multiple locations
- Diagnosing slow WordPress or PHP applications by separating server delay from front-end rendering time
- Validating the impact of caching layers (page cache, object cache) and CDN edge caching
- Monitoring performance regressions after code changes, plugin installs, or database growth
- Troubleshooting network and TLS issues such as slow DNS, extra redirects, or handshake delays
TTFB vs Page Load Time
TTFB measures how fast the server starts responding, while page load time reflects the full user experience, including downloading all assets (CSS, JavaScript, images), executing scripts, and rendering in the browser. A site can have a good TTFB but still load slowly due to heavy front-end code, large images, or third-party scripts. Conversely, a fast front end cannot fully compensate for a slow TTFB on dynamic pages, because the browser cannot begin rendering until the first response arrives.