BRev Internet speed test — with the number most tests skip
An internet speed test against Cloudflare's nearest edge: download, upload, latency, jitter and latency under load — the bufferbloat figure that predicts how a busy line feels. The data each profile uses is stated before you start.
How to read an internet speed testRead
This speed test runs Cloudflare's open-source measurement engine in your browser and times transfers to Cloudflare's nearest edge through speed.cloudflare.com. Download and upload speed are the 90th percentile of the per-request speeds it records. Idle latency is the median of 16 to 21 zero-byte requests, and jitter is the average change from one of those requests to the next. While the download and upload phases run, the engine keeps sending zero-byte requests with a 400 ms pause between them; the median of those is latency under load, and its rise over idle latency is your bufferbloat, graded OK below +30 ms, Moderate up to +100 ms and Severe above that. Three profiles set how far the transfers ramp up: Quick can move up to about 61 MB, Standard 316 MB and Thorough 1.27 GB, and the page states the figure before you press start. BRev has no server in the test path, finished results are not posted to Cloudflare's stats endpoint, and past runs stay in this browser.
What you can do
- Download and upload speed from Cloudflare's open-source speedtest engine, reported as the 90th percentile of per-request throughput
- Idle latency (median of 16 to 21 zero-byte requests) and jitter (average change between consecutive requests), each with an Excellent, Good, Fair or Poor chip
- Latency under load for the download and upload phases, and a bufferbloat grade: OK under +30 ms, Moderate from +30 to +100 ms, Severe above +100 ms
- Three profiles, Quick (~12s), Standard (~25s) and Thorough (~45s), with the worst-case data stated first: about 61 MB, 316 MB or 1.27 GB
- A live gauge on a log scale from 0 to 1,000 Mbps, plus Upload and Download panels that graph throughput as the test runs
- Use-case chips for 4K streaming, video calls, competitive gaming and big uploads, each with the threshold behind it printed on the page
- Copy results as a plain-text report, and a Past runs table of the last 12 completed tests kept in this browser's local storage
How to use internet speed test
- Pick a “Profile”Choose Quick · ~12s, Standard · ~25s (the default) or Thorough · ~45s. The box underneath states the most data that profile can transfer, split into download and upload, so you can decide before using a metered or mobile connection.
- Press “Start test”The engine loads, then measures latency, download and upload while the gauge follows the live figure. Press Stop at any point and every figure measured so far is kept.
- Read the “Results” panelLatency (idle) and Jitter carry verdict chips, and the line under latency shows latency under load for each direction. The Bufferbloat box turns the rise into OK, Moderate or Severe and says which direction was worse.
- Press “Copy results”This copies a plain-text report with the profile, the Cloudflare edge, every figure and the data transferred. Press Test again to add another row to Past runs and compare.
FAQ
Which server does this speed test use?
Every test transfer runs between your browser and Cloudflare's nearest edge: downloads come from speed.cloudflare.com/__down and uploads are posted to speed.cloudflare.com/__up. When the page opens it also makes one request to www.cloudflare.com/cdn-cgi/trace to show the edge's location code and country under Test server & connection, so that label comes from a separate request rather than from the test itself. BRev has no server in the test path.
What is bufferbloat, and how is it measured here?
Bufferbloat is latency that rises while the line is busy, because a router queues too much data ahead of everything else. During the download and upload phases the engine sends zero-byte requests with a 400 ms pause between them and takes the median of up to the last 20. The tool subtracts your idle latency from the worse of the two directions: under +30 ms is OK, +30 to +100 ms is Moderate and more than +100 ms is Severe.
How much data does a speed test use?
It depends on the profile and your line. At most, Quick moves about 61 MB (37 MB down, 25 MB up), Standard 316 MB (169 MB down, 147 MB up) and Thorough 1.27 GB (969 MB down, 297 MB up). A direction stops ramping up once every request in a step takes longer than a second, so slower connections use far less, and after a run the page shows the bytes actually transferred.
How are the download and upload figures calculated?
Each is the 90th percentile of the per-request speeds the engine recorded, ignoring requests that took under 10 ms. They are in megabits per second, so divide by 8 for megabytes per second: a 100 Mbps line moves at most 12.5 MB/s. The page grades download under 5 Mbps as Poor, 5 to 25 Fair, 25 to 100 Good and 100 or more Excellent, and upload under 3 Mbps Poor, 3 to 10 Fair, 10 to 50 Good and 50 or more Excellent.
Why is my result lower than the speed on my plan?
The advertised figure is the line's ceiling. Between you and it sit the Wi-Fi hop, which is often the bottleneck, plus peak-hour congestion, VPNs and other devices on the same connection. Run the test next to the router or on a cable, then again at a different time or with the VPN off, and compare the rows in Past runs before drawing conclusions about your provider.
Does it measure packet loss?
No. Cloudflare's engine measures packet loss through a TURN relay server, and this tool leaves that step out, so no packet loss figure is shown. For round-trip time, jitter and loss to several targets with live sparklines, use the ping test.
Are my speed test results stored or shared?
The engine's default of posting finished results to Cloudflare's aggregate stats endpoint is switched off, and the tool sends results nowhere else. Completed runs are saved in this browser's local storage, newest first and capped at 12, and Copy results writes only to your clipboard. Cloudflare does receive the test requests themselves, as the server on the other end.