Ping / Uptime
TTFB, DNS time, TLS time, status code.
Reachability for https://green.ch
- DNS lookup
- 4.5 ms
- TCP connect
- 51.8 ms
- TLS handshake
- -51.8 ms
- Redirects
- 2
- Remote IP
- 89.145.166.14:443
- Final URL
- https://www.green.ch/de/
Measured from this server's network path. Single-shot, not aggregated.
About Ping / Uptime
This tool measures four discrete timing segments of a single HTTPS request: how long DNS resolution took, how long the TCP three-way handshake took, how long the TLS handshake took, and how long until the first byte of the response arrived. It also reports the final HTTP status code, the redirect count, and the remote IP your request landed on. Total time is the sum from request start to response end.
When to use it
Use this for a quick reachability check from the server's network path to see if a site is up and responding normally. Compare TTFB numbers between competing hosting providers when shopping. Diagnose slow page loads by identifying which phase (DNS, connect, TLS, or server processing) takes the most time. Sysadmins use it as a single-shot version of curl -w for quick checks.
How to read the results
For a well-tuned site DNS should be under 50 milliseconds (or near zero with a cached resolver), TCP connect under 100, TLS under 200, and TTFB under 500. Higher values point to specific bottlenecks. Slow DNS suggests your nameservers are far away or overloaded. Slow connect means high network latency. Slow TLS often means an old TLS version. Slow TTFB after the handshake usually means slow server processing.
Frequently asked questions
Why is this single-shot rather than averaged? ▾
A single shot is fast and good enough for is it up and roughly how fast answers. For real performance work, run it multiple times or use a synthetic monitoring service that runs from many geographic locations and aggregates over time.
How does TTFB relate to overall page speed? ▾
TTFB is the time from request to the first byte of the response. The full page load also includes downloading the HTML, parsing it, fetching CSS, JS, and images, and rendering. TTFB is the server-side floor that all those other phases stack on top of.
My site shows 200 OK but visitors report errors. Why? ▾
A 200 status means the server returned a response. The body may contain an error page that the application rendered with status 200. Visitors may also hit different CDN nodes or be served different content based on geography or device.
Why is the TLS time zero on some requests? ▾
TLS time is the difference between appconnect_time (when TLS finished) and connect_time (when TCP finished). On HTTP requests over plain port 80 there is no TLS, so the difference is zero. Make sure your URL starts with https://.