What is Time to First Byte?
Time to First Byte (TTFB) measures how long a browser waits before receiving the first byte of a response from the server. A high TTFB usually points to slow hosting, backend processing, or missing caching.
Why Time to First Byte matters
Time to First Byte is the wait between the request leaving the browser and the first byte of the response arriving: DNS, connection setup, TLS, and above all the server's own thinking time. Everything else in page load waits behind it, so a 1.5-second TTFB caps LCP at well over two seconds before a single byte of HTML has been parsed. Google's guidance is 800 ms or less; good hosting does it in under 200 ms.
High TTFB is usually one of four things: a slow or overloaded server, a CMS rendering every page from scratch without caching, a database query on the hot path, or distance between the visitor and the origin with no CDN in between. Diagnosing which one takes a curl timing or a Server-Timing header rather than a front-end audit.
Example
Measuring it from the command line:
curl -o /dev/null -s -w 'dns %{time_namelookup} connect %{time_connect} tls %{time_appconnect} ttfb %{time_starttransfer}\n' https://example.com/If ttfb is far above tls, the server is the problem, not the network.
Common mistakes
- •Blaming the theme or images when the server itself takes a second to answer.
- •No page cache on a CMS, so every visit renders the page from the database.
- •Origin in one region with a global audience and no CDN in front.
How Webmatik checks it
The Server response speed check reports TTFB for the audited pages; when it fails, the report's action plan links the TTFB guide and, since a slow server is usually a hosting decision, points at hosting options.
Check your own site
Free Website Speed Test
See your LCP, CLS and INP on mobile and desktop, with the fixes ranked by payoff.
Related Performance terms
See how your website scores across SEO, GEO, performance, and more
Run a free audit