browser HTTPS round-trip latency
HTTPS Round-Trip Latency Probe
Measure browser HTTPS round-trip latency including TLS and HTTP overhead via no-cors fetch timing. This is not ICMP ping.
Network tool FAQ
Is this the same as ICMP ping?
No. Browsers cannot send raw ICMP packets. This tool times five no-cors HTTPS fetches and reports the round-trip including DNS, TLS handshake, and HTTP overhead.
Why is this slower than ICMP ping?
A no-cors HTTPS fetch carries TCP, TLS, and HTTP overhead on top of the underlying network path, so timings will be larger than a raw ICMP ping.
Why can CORS affect the result?
Some hosts block browser requests or hide response details, so timing can fail even when the host is online.
What target should I use?
Use a stable HTTPS endpoint near the service you care about, such as a site homepage or health-check URL.
Why do samples vary?
Wi-Fi quality, routing, congestion, server load, TLS session reuse, and browser scheduling can all change fetch timing between samples.
Does this measure download speed?
No. It reports HTTPS round-trip latency and browser connection hints, not a full bandwidth test.