DNS lookup time
Measures hostname-resolution timing observed during the browser navigation.
Free website response time test
Break website response time into DNS, connection, TLS and first-byte delay.
Run a live Chromium check and compare DNS lookup, connection setup, TLS handshake, Time to First Byte and full page-load timing from one test location.
Free · No signup required · Live public website check
What this tool checks
The timing stages before and during page load
Connection time
Shows browser connection setup timing where navigation timing exposes it.
TLS handshake
Shows secure-connection setup time for HTTPS pages when available.
Time to First Byte
Measures the delay between request start and the first response byte.
Page load time
Keeps network response timing beside the full document load milestone.
LCP context
Shows whether the main content remains delayed even after the server begins responding.
Interpret the result
Response time has several stages, so one number rarely explains the bottleneck.
A slow request can come from DNS, network distance, TLS setup, backend processing or work that happens after the first byte arrives. Breaking the navigation into stages helps identify where the delay begins.
These timings come from one SiteState browser location. They are useful for diagnosis and repeatable retesting, but they are not a global latency measurement across regions.
Methodology
SiteState uses browser navigation timing from a controlled Chromium run. DNS, connection, TLS and TTFB values represent the current SiteState test location and can differ for users in other regions.
FAQ
Common questions about this website check
What does a website response time test measure?
SiteState reports DNS lookup, connection setup, TLS handshake, TTFB and page-load timing when those values are available from the browser navigation.
Is response time the same as TTFB?
No. TTFB is one part of the request timeline. DNS, connection and TLS can occur before it, while rendering and page load continue afterward.
Is this test multi-location?
No. The free response-time test uses the current SiteState browser location. Multi-location monitoring is a separate future capability.
Can SiteState monitor response time continuously?
Yes. Scheduled monitoring stores response timing over time, while synthetic browser monitoring adds page-load and regression context.
Related free tools
Check another part of website health
Continuous website state
Need ongoing history? Website monitoring turns one-off health checks into continuous state, incidents and change detection. Website monitoring.
A one-off check tells you what is happening now.
SiteState continuous monitoring keeps watching and builds history for changes, incidents and regressions.