Web development

Time to first byte (TTFB)

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 reflects server and network speed.

Before anything can appear on screen, the browser must receive a response. TTFB measures that wait, including DNS lookup, connection setup, server processing and the first data arriving.

In more detail

Google suggests a TTFB of 0.8 seconds or less as a rough guide. Slow TTFB usually comes from slow hosting, heavy server-side processing, uncached database queries, redirects or distance from the server. Fixes include caching, a CDN, static site generation, better hosting and removing unnecessary redirects. TTFB is not a Core Web Vital itself, but it directly delays LCP.

Why it matters

Every millisecond of TTFB is added to everything that follows. A fast server response is the foundation of good page speed.

Example

A WordPress site has a TTFB of 2.1 seconds due to an overloaded shared host and no caching. Adding page caching and a CDN brings it to 0.2 seconds, and LCP improves by nearly two seconds.

FAQ

TTFB: quick answers

What is a good TTFB?

Around 0.8 seconds or less is a reasonable target. Static sites on a CDN often achieve under 0.2 seconds.

How do I measure TTFB?

Use PageSpeed Insights, WebPageTest or the network panel in browser developer tools.

Free audit

Find out where you stand in search and AI answers.

Get a free audit of your SEO, AI visibility and email setup. We send a short, specific report with the three changes that would move the needle most.