How does the test work?
Your browser connects straight to Cloudflare's speed test servers (the ones behind speed.cloudflare.com), at the Cloudflare data center nearest to your network. Nothing passes through this site.
First, 16 tiny requests measure latency and jitter. Then the download: several requests run at once, and every byte is counted as it arrives, for 5 to 10 seconds. The first 30% is left out while the connection speeds up; the result is the average after that, and the test stops early once the speed settles. The upload is measured the same way. During both, a small request every 0.15 s measures the latency while your line is full.
Why is it slower than my plan, or than other speed tests?
Wi-Fi is the most common reason. To see what your line itself can do, plug in a cable to the router and pause other devices.
The other reason is how the test connects. Your browser uses a single connection to the test server (HTTP/2 or HTTP/3, shared by several requests), while Ookla's Speedtest app opens many. Close to the server the two agree; the farther away it is, the more a single connection loses. Ookla also often tests against a server inside your ISP's own network, which looks better than any route that leaves it.
In mainland China, Cloudflare's data centers are outside the country, so this measures your international bandwidth, often far below your plan's speed.
What is bufferbloat, and how is it graded?
Bufferbloat is when your latency shoots up as soon as your line gets busy. If your game or video call starts lagging the moment someone at home downloads a big file or streams in HD, bufferbloat is the likely cause.
It happens in your router and modem. When the line is full, they hold packets in large buffers, so game data and call audio wait in line behind the download.
The test measures your latency while the line is quiet, then every 0.15 s during the download and the upload, and takes the median of each. How much higher it is under load than idle (the worse of the two directions) sets the grade, using the same thresholds as Waveform's bufferbloat test: under 5 ms A+, under 30 ms A, under 60 ms B, under 200 ms C, under 400 ms D, more F.
How to fix it: from C down, turning on SQM (smart queue management, with fq_codel or CAKE) in your router fixes most of it, at the cost of a little top speed. Routers name it differently, often SQM, Smart Queue or QoS. If yours has none, OpenWrt or a router that supports it will.
How do I test latency and jitter?
Press Start; there's nothing to install. You get three latencies: idle, while downloading and while uploading, each with its jitter.
Latency is how long data takes to get to the server and back. When idle, it mostly reflects how far you are from Cloudflare and how good the route is. Jitter is how much it changes from one request to the next; high jitter makes calls choppy and games stutter. How much the latency rises while downloading and uploading gives the bufferbloat grade.
Testing right before a call or a game is the best way to see whether your connection will hold up.
Is it good enough for 4K, calls and gaming?
After the test, the page rates five uses as smooth, so-so or struggles. The thresholds are common rules of thumb; each service needs slightly different numbers.
4K video: smooth with a download of 25 Mbps or more; so-so from 5 Mbps, which is fine for HD but may buffer in 4K.
Video calls: smooth with 3 Mbps or more each way, latency up to 80 ms and jitter up to 20 ms; so-so down to 1.5 and 1 Mbps, 200 ms and 50 ms.
Online games: smooth with latency up to 40 ms, jitter up to 10 ms and no more than 30 ms added under load; so-so up to 100, 30 and 100 ms.
Cloud gaming: smooth with a download of 35 Mbps or more, latency up to 40 ms and jitter up to 10 ms; so-so down to 15 Mbps, 80 ms and 20 ms.
Live streaming: smooth with an upload of 20 Mbps or more, so-so from 5 Mbps.
Below so-so, it struggles. If games lag, the cause is usually latency, jitter or bufferbloat: try a cable first, then SQM in your router. If video or streams stall, you usually need more bandwidth.
I use a proxy or VPN. Whose speed is this?
The proxy's. With a proxy or VPN on, your browser reaches the test server through it. The speed is set by the slowest of three legs: your line to the proxy node, the node's own bandwidth, and the node's route to Cloudflare. That's handy for comparing nodes.
To test your own connection, add the direct rules (the button next to the progress bar): only speed.cloudflare.com goes direct, and nothing else changes. Clash/Mihomo, Surge, Shadowrocket, Quantumult X, Loon, sing-box and Xray are supported, most of them with a rule set that stays up to date on its own.
The exit shown under the heading (city, network, IP) tells you which way the test went, and the page warns you when it looks like a proxy.
How much data does a test use?
Each direction stops after 5 seconds once the speed settles, 10 at most. So a test uses 5 to 10 seconds at your top speed, each way: about 100 to 250 MB in total on a 100 Mbps line, 1 to 2.5 GB on 1 Gbps. The page shows how much each test used. On mobile data or a capped plan, test sparingly.
Why doesn't it start on its own?
A speed test uses a lot of data, so the page waits for you to press Start. If you test often, tick "Test as soon as the page opens" next to the progress bar. The choice is saved only in this browser.
What do the UDP loss and QUIC tiles mean?
Calls, games and live streams send their data over UDP, where a lost packet is gone for good. While the test runs, the page sends 50 tiny packets a second over UDP (WebRTC) to our server in Tokyo and counts those that never come back: with the line quiet, while downloading and while uploading. Under 1% is fine; a few % makes calls choppy and games stutter.
QUIC (HTTP/3) runs over UDP too. Some office, school and cross-border networks block or slow UDP; apps then fall back to TCP. The QUIC tile tells you whether it gets through, and compares its round trip with TCP to the same server. Safari doesn't support WebTransport, which the check needs, so it shows Can't check there.
The server is in Tokyo only. Far from Japan, part of the loss and jitter belongs to the long route there, not to your line. Both checks together use about 0.5 MB.
Do you collect my data?
This site doesn't collect your results. The test runs directly between your browser and Cloudflare's servers, and the results never reach this site, unless you choose Report a problem, which sends us this run. As with any website, Cloudflare sees your IP address. The UDP and QUIC check connects to our own server in Tokyo (rtc.1ms.dog): it sees your IP address while the test runs, only counts the packets, and keeps nothing, not even a log.
Your history stays in your browser. Share links and images are made in your browser too, and carry only the numbers and the time; you choose whether to add your country and Cloudflare data center, and your IP address is never included. The code is open source on GitHub.