What is Time to First Byte (TTFB)?
Time to First Byte (TTFB) is how long a browser waits, after requesting a page, before the first piece of the server’s response arrives.
Want to know where your site stands on TTFB?
I’ll test your site on a real mid-range phone profile and send you the two or three fixes that matter most, free.
In plain English
TTFB covers everything before the page can start arriving: looking up the domain, connecting securely, and the server working out what to send. On a database-driven site, that last part can mean building the page from scratch on every visit.
It isn’t a Core Web Vital itself, but nothing can paint until the first byte lands, so it puts a floor under LCP. Google’s guidance suggests aiming for roughly 0.8 seconds or less.
Why it matters for a small business
If the server is slow, no amount of image compression on the front end will save you. Cheap shared hosting, an overloaded plugin stack or a server on another continent all show up here first. It’s often the quickest way to tell whether a slow site has a hosting problem or a page-weight problem.
An example
Common mistakes
Where I see TTFB go wrong most often.
Blaming images for a slow site when the server is taking a second or more to respond.
Testing TTFB once from a location near the server and assuming everyone gets that result.
Stacking redirects, such as http to https to www, each of which adds its own round trip.
TTFB, answered
Google’s guidance suggests about 0.8 seconds or less for most sites. Static pages on a good CDN are often far quicker than that.
Usually, because it serves pages from a server close to the visitor. It helps most when the pages can be cached rather than built on each request.
Keep reading
- nick@tavro.ca
- 587-439-9994
- Calgary, Alberta