TTFB Checker
Measure approximate Worker-observed response-header timing with transparent limits.
Inspect a public website
Analyze URL sends the submitted URL, including its query parameters, to the WebToolspire API. The API checks public DNS and requests the target without your browser cookies or authorization. Do not submit secret URLs.
One URL, an eight-second server deadline, and at most five redirects. Only response headers are inspected; bodies are cancelled.
Understand your results
For developers comparing a bounded response-header observation from the API’s network location.
Timing starts immediately before each Worker GET and stops when response headers arrive. The reported sum and final-hop interval exclude DNS preflight and body download. It is one observation from one location, not browser TTFB, Lighthouse data, Core Web Vitals, or a definitive speed score.
How to use this tool
- Submit a public URL and start the measurement.
- Review the final HTTP status, redirect count, summed intervals and final-hop timing.
- Consider repeat measurements and browser tooling separately; cache state, TLS, location and bot policies affect the result.
What the observations mean
The duration measures one GET request from the Worker until headers arrive. The body is cancelled. DNS preflight and redirect information are reported separately; this is not a browser navigation or a Core Web Vitals score.
Worked example
Separate response-header delay from the time needed to render a whole page.
Public target: https://example.com/notebooks/
Observation: request start → response headersThe result reports the actual measured duration for that request from the Worker’s network location. Repeating the check can reveal variation; this example deliberately supplies no invented timing number or performance score.
Limits and processing
Requires the API. One Worker-to-target GET-to-headers observation includes network effects and is not browser navigation TTFB, LCP, INP or CLS. The body is cancelled and the page is not rendered.
Common problems and practical fixes
- Unexpected slow sample
- Repeat under comparable conditions and inspect target load, cache state, network distance, and redirects.
- Fast headers but slow page
- Measure rendering, asset transfer, and JavaScript execution using browser tooling.
- Timeout or unavailable host
- Check the actual service and bot protection. A failed sample has no invented timing score.
Best practices
Keep the vantage point and request conditions with each observation. Avoid drawing a site-wide conclusion from a single request.
Practical tips
- A fast error page can have a low response time. Always read the actual HTTP status.
- Redirect time is included only in the measured hop intervals; DNS validation overhead is excluded.
- The tool cancels the page body after headers rather than downloading it for a header-time measurement.
Frequently asked questions
Practical answers for using the TTFB Checker.
Is this a performance score?
No. The output is a measured interval in milliseconds with limitations, not a 100-point score.
Why does it differ from my browser?
The Worker has a different network path, cache state, transport setup, and request context. Browser timings also have different measurement boundaries.
Can a measurement time out?
Yes. DNS, headers and redirects share a strict deadline. A timeout returns an error, not a guessed value.