A run takes a short while and consists of a latency check followed by a download phase and an upload phase.

All transfers are encrypted, and the random test data is discarded as soon as it has been counted.

How ping is measured

Each probe is a minimal HTTPS request with almost no payload. The browser notes when it leaves and when the reply arrives; the difference is the round-trip time.

Distance to the server, the number of network hops and the quality of your home network all add to this figure.

Jitter

Jitter describes how much the ping changes from one request to the next. We calculate it from the differences between consecutive round-trip times in the latency series.

Low jitter means a steady connection, which is what real-time voice and video need.

How download is tested

The browser opens several parallel requests and keeps them busy for a few seconds. Throughput is sampled continuously, and the figure you see reflects the sustained rate once the transfer has settled.

The received data is meaningless filler and is discarded immediately after it is counted.

Upload speed

For the upload stage, your browser generates random data locally and sends it to our server over several parallel connections. The rate at which the data leaves your device is the upload speed.

The server accepts the data, confirms receipt and throws it away. Nothing you upload during the test is kept.

Comparing with other tests

Speed tests differ in how many connections they use, how long they run, which part of the transfer they count and where their servers are. Each of these choices moves the result slightly.

None of them is wrong; they simply measure different paths. Use one test consistently when you track your connection over time.

What influences the measurement

Keep these in mind when you compare one result with another.