XungleeXungleeSpeed
Xunglee / SpeedAll tools ↗

Xunglee / Speed

Quick speed 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.

A shorter test uses less data and may be less precise.

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

Use Quick when you need a short connectivity check with a smaller transfer allowance. Keep background traffic low and wait for the test to finish before comparing values. Quick still transfers real data; it is not data-free.

Worked example

If a short run reports download, upload and latency, use it as a snapshot of conditions at that moment. A later standard run may differ because it observes a longer interval and has a larger allowance, even on the same connection.

Interpretation and limits

Short samples are sensitive to startup delays and bursts. Do not use one quick result as proof of your line’s maximum rate or long-term reliability. The displayed allowance and any limit warning matter when interpreting the measurement.

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.