Time to First Byte (TTFB)
Measures the delay from navigation until the first response byte is observed for the main document.
Free TTFB test
Check TTFB from SiteState's test location and see the surrounding DNS, TLS, redirect and full page-load context so server response time is not interpreted in isolation.
Free · No signup required · Real Chromium lab test
What this tool measures
Measures the delay from navigation until the first response byte is observed for the main document.
Shows hostname-resolution time observed during the browser navigation where available.
Shows HTTPS connection setup time reported during the current run where available.
Shows document redirects because redirect chains can add delay before the final page loads.
Lets you compare server response delay with when the main visible content actually renders.
Keeps TTFB connected to page weight, blocking resources and JavaScript rather than treating it as the only cause of slowness.
Interpret the result
A slow initial response can delay everything that follows because the browser cannot start processing the main document until it receives data. But a fast TTFB does not guarantee a fast page if images, CSS or JavaScript dominate the rest of the load.
SiteState therefore shows TTFB inside the same browser report as LCP, TBT, resource weight and JavaScript impact. The measurement reflects SiteState's current test location and can differ from what users see in other regions.
Methodology
TTFB is measured during the same controlled Chromium navigation as the rest of the SiteState lab report. It is a single-location measurement, not a multi-region TTFB benchmark.
FAQ
Enter a website URL and run the SiteState TTFB checker. The controlled browser navigation measures Time to First Byte and keeps DNS, TLS, redirects and rendering context beside the result.
Time to First Byte measures how long the browser waits between starting a request and receiving the first byte of the response.
No. The current SiteState free TTFB test reports the timing from the SiteState browser test location. Multi-location monitoring is a separate product capability planned for later.
Yes. If the main document response is delayed, browser rendering starts later, which can also delay Largest Contentful Paint. Other resources and browser work can add further delay after the first byte arrives.
Yes. SiteState's scheduled monitoring stores response timing over time, and browser monitoring provides additional page-performance context.
Related free tools
Website Speed Test
See TTFB in the context of the complete page load.
Open toolLCP Test
Check how server and resource delays affect main content rendering.
Open toolCore Web Vitals Test
Measure synthetic page-experience signals.
Open toolPerformance Monitoring
Track response time and browser regressions continuously.
Open toolContinuous performance
Need more than one test? Website performance monitoring keeps compatible browser metrics and regression history over time. Performance.
A one-off speed test is only a snapshot.
SiteState can keep the same website under continuous monitoring and detect when performance changes.