Time to First Byte (TTFB)
The time between a request and the first byte of response from the server.
Key takeaways
- Time to First Byte (TTFB) is the time between a request and the first byte of response from the server.
- Serve static or pre-rendered pages from a CDN close to your visitors.
- Avoid: rendering every page on demand when it rarely changes.
What is Time to First Byte (TTFB)?
TTFB is a foundational performance metric. Slow TTFB caps how fast LCP can be. Edge delivery, caching, and lean server side rendering all help.
web.dev's guide to Time to First Byte covers what a good TTFB looks like and how to improve it.
Why Time to First Byte (TTFB) matters for SEO in 2026
TTFB is how long the server takes to start responding. Every other speed metric waits for it, so a slow server caps how fast a page can ever feel.
For a wider view of where this fits, see our full SEO glossary or explore the SEO and GEO service we run for clients.
How to apply Time to First Byte (TTFB) on your site
Knowing the concept is only half of it. Work through these steps in order to put Time to First Byte (TTFB) into practice on your own pages:
- Serve static or pre-rendered pages from a CDN close to your visitors.
- Cache dynamic responses wherever the content allows.
- Measure TTFB from your users' regions, not just your own location.
Common mistakes to avoid
Most sites that struggle with Time to First Byte (TTFB) fall into the same traps. Check your pages against each of these before moving on:
- Rendering every page on demand when it rarely changes.
- Hosting far from your main audience without a CDN.
- Adding redirects before the final page, each costing a round trip.
Questions about Time to First Byte (TTFB)
The time between a request and the first byte of response from the server.
TTFB is how long the server takes to start responding. Every other speed metric waits for it, so a slow server caps how fast a page can ever feel.
Start here: serve static or pre-rendered pages from a CDN close to your visitors. Then cache dynamic responses wherever the content allows.
The most common is rendering every page on demand when it rarely changes. Another is hosting far from your main audience without a CDN.