TTFB distribution
How TTFB is distributed across real-user data, plus pass-rate breakdown.
At a glance the headline numbers for TTFB distribution
How TTFB is distributed across real-user data, plus pass-rate breakdown.
58.6% of sites good on TTFB. The typical site's TTFB is 665ms. The worst 10% are above 2.0s.
The TTFB distribution site count at each TTFB, from good to poor
The tallest bar is between 300ms and 450ms. 19% of sites are in that one range, 350ms under Google's 800ms limit. Half of all sites are at 665ms or less. The tail is long. The worst 10% are above 2.0s and the worst 1% above 4.2s. That is 6.3 times the typical site.
The TTFB pass rate the share of sites that are good, needs improvement and poor
58.6% of sites are good on TTFB. 29.2% are in the needs improvement band, between 800ms and 1.8s. 12.2% are poor, above 1.8s. A miss is usually needs improvement, not poor.
Why this matters for the Core Web Vitals, and where to start fixing it
Time to First Byte is how long the browser waits for the server to start replying. It is a diagnostic metric, not a Core Web Vital, but it is the foundation the others are built on: nothing can render until the first byte arrives, so a slow TTFB pushes back every paint that follows. The causes are on the server and the network, slow backend processing, no caching, or a long trip to a distant origin.
Start by getting a fast, cacheable response out the door. Cache full pages where you can, put a CDN in front so visitors are served from nearby, and keep the backend work on each request small. Early Hints use that wait: the browser can start fetching critical resources while the server is still building the page.
How are sites doing on TTFB?
58.6% of sites have a good TTFB. The typical site sits at 1.2s at the 75th percentile; the slowest 1% pass 4.2s.
Chrome field data from 189,915 sites, representing millions of real page loads. How we measured.