IPv4
Detecting…
- Download
- –
- Upload
- –
- Ping
- –
- Jitter
- –
- Latency under load
- –
- Loss
- –
Ready
0 Mbps
- HTTP/1.1
- HTTP/2
- HTTP/3
Checking your IPv4 and IPv6 connectivity…
IPv6
Detecting…
- Download
- –
- Upload
- –
- Ping
- –
- Jitter
- –
- Latency under load
- –
- Loss
- –
How these numbers are measured
The test prefers HTTP/3, which runs over QUIC on UDP. If your network blocks UDP, your browser falls back to HTTP/2 or HTTP/1.1 over TCP. The lights under the gauge show which version each request actually used.
Download and upload use six parallel streams for 10 seconds each. The first 1.5 seconds are left out so connection ramp-up doesn't pull the result down.
Ping is the median of 20 small requests on an idle connection. Jitter is the average change between consecutive pings.
Latency under load is the server's view of round-trip time while the download is running. A big jump over your idle ping points to oversized buffers along the path (bufferbloat).
Loss is the share of download packets the server had to send again. Browsers can only use TCP, which repairs losses itself, so this is the closest reading of packet loss a web page can take. Pings that time out are listed next to it.