Xunglee / Speed

Jitter test.

Your connection. Measured, not guessed.

Test server Xunglee Server

Download—Mbps

Upload—Mbps

HTTP latency—ms

Jitter—ms

Ready when you are

—Mbps

Results measure the connection between your browser and this test server. They can differ from other tests depending on network conditions and server capacity.

Your connection may charge for this data. Press GO only when you want to start.

Ready when you are

History on this device

Nothing is saved automatically. Save a result to keep up to 20 tests in this browser. No IP address or identifiers are included.

Your browser

IP ↗

Using this tool with confidence

How to use it

Jitter here is the average absolute difference between consecutive HTTP latency samples. Preserve their order when comparing calculations. It describes variation during this short run, not a permanent property of the line.

Worked example

For consecutive latencies of 20, 25 and 21 ms, the absolute changes are 5 and 4 ms. Their average is 4.5 ms. A connection can have low typical latency yet substantial variation during a burst.

Interpretation and limits

This HTTP variation is not a measurement of RTP jitter or packet loss and does not qualify a connection for voice or gaming. Browser scheduling and server load contribute. Repeat comparable runs and consider the individual samples alongside the aggregate.

Understand your results

Mbps and MB/s

Mbps means millions of bits per second; MB/s means millions of bytes per second. Divide Mbps by 8 for decimal MB/s. Download receives data; upload sends it. These results include HTTP and server overhead.

HTTP latency and jitter

The browser cannot perform ICMP ping here. HTTP latency is the round-trip request time, including server processing. Jitter is the mean absolute difference between consecutive latency samples: sum(|r[i]−r[i−1]|)/(n−1). It is not an ICMP or packet-level jitter measurement.

Why tests differ

Wi-Fi signal, Ethernet, congestion, distance, shared hosting load, PHP capacity, browser CPU and protocol overhead affect the result. Proxies/CDNs, HTTP/2 or HTTP/3, compression, disk spooling and buffering can also change it. This is one server and one route, not a certified line-capacity test.

Download counts received payload bytes using a monotonic clock. Upload counts only bytes acknowledged by the server until its response arrives. Calibration is excluded from speeds but consumes the allowance. Aborted or unacknowledged upload data is not counted in the result.