What these numbers mean
- RTT (round-trip time): milliseconds for a request to reach the server and return. Lower is more responsive.
- Jitter: how much the RTT varies between probes. High jitter causes stutter in calls and games even when average RTT looks fine.
- Packet loss: the share of probes that never came back. Even a few percent noticeably degrades real-time traffic.
This is a single path — your browser to our server — sampled a dozen times. It's a useful health check, not a full network diagnosis, and there's no pass/fail verdict here: the numbers are the result.
What's a "good" reading?
- Under ~50 ms RTT feels snappy; 100–200 ms is fine for browsing, noticeable in games.
- Low, steady jitter matters more than a low average for calls and gaming.
- 0% loss is the goal; anything sustained above a few percent is worth investigating.
Improving a poor connection
High loss or jitter usually points at your local link — Wi-Fi interference, a congested uplink, or an overloaded router — before it points at distance. A VPN can occasionally route around a bad path, but it adds a hop, so treat it as something to test rather than a fix.
Common questions
Why is this slower than a speed test?
Speed tests measure bandwidth (how much data per second); this measures latency and loss (how quickly and reliably small requests complete). They're different properties — a fast connection can still have high latency or loss.
The test couldn't measure anything — why?
Every probe failed to return, usually because the measurement endpoint was unreachable or blocked. We report that as inconclusive rather than showing a made-up number.
Related checks
While you're here: