Run a detailed latency test from your browser — min, average, median, P95, max, standard deviation, jitter and packet loss, plus a distribution chart and a side-by-side server comparison.
A ping test measures round-trip time (RTT): how long a small packet takes to travel from your device to a server and back. It is the most direct way to see how responsive your connection feels — it decides input lag in games, the delay in a video call and how snappy web pages start loading.
Bandwidth (Mbps) tells you how much data you can move. Ping tells you how fast a single exchange happens. A 1 Gbps connection with 120ms ping still feels sluggish in real-time apps.
Your browser sends lightweight, cache-busted HTTP requests to the server you pick and times each one with performance.now(). The first 3 requests open the TCP and TLS connection, so they are shown but excluded from the statistics.
Browser pings include a little HTTP overhead, so values can be a few milliseconds higher than a command-line ICMP ping. Requests that don't answer within 3 seconds count as packet loss.
A single "ping" number hides a lot. These are the values this test reports and what each one tells you.
MinThe fastest reply. Close to the physical limit of your route — useful as a baseline, but it says nothing about consistency.
AverageThe mean of all replies. This is the number most tools show. A few slow spikes can pull it up noticeably.
MedianHalf of replies were faster, half slower. Less affected by spikes than the average, so it is often the more honest "normal" ping.
P9595% of replies were at or below this. If P95 is far above the median, you have spikes you will feel in games and calls.
MaxThe slowest single reply. One high max is normal; a max that keeps repeating near P95 means a congested link.
Std DevHow widely replies are scattered around the average. Under 5ms is very stable; over 20ms points to Wi-Fi or congestion.
JitterAverage difference between consecutive pings (RFC 3550). The key number for VoIP and gaming smoothness.
Packet LossRequests that never came back. Anything above 0% shows up as stutter in real-time apps; above 2% needs fixing.
"Good" depends on what you do. These are the ranges used for the verdict cards above.
| Use case | Excellent | Good | Playable | Struggling |
|---|---|---|---|---|
| 🎮 Competitive FPS / fighting | < 20ms | 20–40ms | 40–80ms | > 80ms |
| 🕹️ Casual / MMO / strategy | < 40ms | 40–80ms | 80–150ms | > 150ms |
| ☁️ Cloud gaming | < 20ms | 20–40ms | 40–60ms | > 60ms |
| 📞 Video calls & VoIP | < 30ms | 30–70ms | 70–150ms | > 150ms |
| 🌐 Browsing | < 50ms | 50–100ms | 100–200ms | > 200ms |
| 🎬 Video streaming | Ping barely matters — streams buffer several seconds ahead. Bandwidth is what counts. | |||