XungleeXungleeSpeed
Xunglee / SpeedAll tools ↗

Xunglee / Speed

Download.

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

Use this mode to measure data arriving from the test server at your browser. Pause other downloads and streaming. The browser counts received bytes over elapsed time rather than inferring a rate from your network label.

Worked example

A received payload of 10,000,000 bytes in 2 seconds corresponds to 40 Mbps: bytes × 8 / seconds / 1,000,000. This illustrative calculation is not a live result. Mbps and MB/s differ by a factor of eight before overhead.

Interpretation and limits

The value describes this server and route. Shared Wi-Fi, VPN, device load and server limits can all reduce it. A fast cached file would not be a valid network measurement; Speed rejects cached or compressed protocol responses rather than accepting them as a speed improvement.

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.