Glossary · Page speed

TTFB (Time to First Byte)

Also called: server response time

Definition

TTFB (Time to First Byte) is the time from requesting a page to receiving the first byte of the response; web.dev suggests 0.8 seconds or less.

TTFB explained

TTFB covers everything that happens before the browser receives any content: redirects, service worker start-up, DNS lookup, connection and TLS negotiation, and the time the server takes to produce the response. It is not a Core Web Vital itself, but it comes before every other loading metric, so a slow TTFB makes a good LCP hard to achieve.

web.dev suggests most sites should aim for a TTFB of 0.8 seconds or less as a rough guide. Common causes of slow TTFB include slow database queries, uncached pages rendered on every request, underpowered hosting, redirect chains, and visitors being far from the server.

Typical fixes are full-page caching, serving cached HTML from a CDN close to visitors, optimizing slow queries and plugins, upgrading hosting, and removing unnecessary redirects. Measure TTFB from real users where possible, because a test from one location near your server can look much better than visitors elsewhere experience.

Example

Your WordPress site feels slow for visitors in the US, while your server is in Europe and caching is off. Enabling page caching and serving cached pages from a CDN with locations near your visitors cuts TTFB for them significantly.

Why it matters

Every millisecond of server delay is added to every page view, so a slow TTFB holds back all other speed improvements.

Related service

Page Speed Optimization

We fix LCP, INP and CLS issues so pages load fast and respond quickly for real users.

Page speed and Core Web Vitals optimization

Sources

Published by Vidern, founded and led by Malhar Shah. Updated .

Find out what's holding your site back

Get a free SEO audit with prioritized fixes, delivered within 48 hours.