Download speed
How quickly this device receives data. It matters most for streaming, downloads, updates, and loading media. Reported in Mbps.
Measure download, upload, ping, jitter, and responsiveness under load. Compare the result with your plan and see what to test next.
Cloudflare receives the test traffic and sees your public IP. Standard schedules up to 131.4 MB; overhead or retries can add data. Results and history stay in this browser.
Ready when you are
For a clean baseline, pause downloads and connect with Ethernet or sit near your router. One click measures speed and responsiveness.
Throughput tells you how much data can move. Latency tells you how quickly the connection reacts. You need both stories to understand streaming, uploads, calls, games, and everyday browsing.
How quickly this device receives data. It matters most for streaming, downloads, updates, and loading media. Reported in Mbps.
How quickly this device sends data. Video calls, cloud backups, file sharing, and live streaming depend on it.
The browser estimates HTTP round-trip response time, shown here as ping. Jitter is how much that timing varies. Lower, steadier values feel more immediate.
Response time while the line is busy. A large increase can reveal queueing delay that a quiet ping and high Mbps miss.
This is an end-to-end browser measurement, not a direct reading from your modem. That makes it realistic for this device—but one run alone cannot prove which link caused a slow result.
Published minimums describe one activity. A practical target needs headroom for every other person, device, sync, and update using the connection at the same time.
15+ Mbps downNetflix’s published recommendation. Add headroom for other streams and active devices.
3–5 Mbps both waysStable upload, sub-100 ms latency, low jitter, and low loaded latency matter as much as spare download capacity.
10/3 Mbps + low delayA Blockify diagnostic starting point, not a publisher requirement. Ping, jitter, loaded latency, server distance, and packet loss shape play more directly.
100/20 Mbps baselineThis matches the FCC’s advanced fixed-broadband benchmark; it is a policy baseline, not a universal personal requirement.
Sources and context: Netflix speed recommendations, Google Meet network guidance, and the FCC 100/20 Mbps benchmark. Blockify’s “Ready” labels intentionally add headroom and are practical guidance, not service certification.
These are diagnostic clues, not automatic verdicts. Change one thing at a time, repeat the test, and let the difference point you toward the next check.
Your ISP capacity may be fine. Test beside the router. If both the router and device support them, compare 5 or 6 GHz nearby; they can be faster but generally lose more reach through walls than 2.4 GHz. Reposition a mesh node and check device limits or interference.
Pause other traffic, restart the gateway, test another device, and repeat off-peak. Persistent gaps are better evidence for an ISP conversation.
Downloads may feel fine while calls, backups, and live video struggle. Check whether another device is syncing and compare with your plan’s upload rate.
The line may become unresponsive when busy. Look for router SQM or smart queue management, stop saturation, and compare upload-loaded versus download-loaded delay.
Blockify keeps up to five results on this device. When the latest three use the same setup, mode, and method version, it shows their median download speed, range, and spread. Mixed setups remain a controlled comparison rather than being blended into a misleading average, and you can export every saved measurement for deeper review.
Use Ethernet if possible—or sit beside the router. Pause downloads, backups, streams, and VPNs you can safely stop.
Keep the same device and test mode, then move to the slow room or change from Ethernet to Wi-Fi. Label the setup in Test settings.
Repeat the setup that matters at the problem time. Review Recent tests for the three-run median and range, or export the CSV for jitter and loaded-latency details, before drawing a conclusion.
Connection speed and page speed are different. This test cannot prove that an extension increases the Mbps sold by your ISP. Blockify can prevent some ad and tracker requests from loading on supported pages, reducing unnecessary page activity and making browsing feel cleaner.
Blockify maintains the custom sequence configuration and the interpretation labels documented below; they are not Cloudflare ratings. Methodology version 1.1 was updated on July 27, 2026.
After you click Start, Blockify uses the open-source Cloudflare engine for a custom HTTPS sequence to Cloudflare's edge. Standard schedules 12 idle-latency probes, 10 download samples, and 8 upload samples from 100 KB to 25 MB each (131.4 MB of nominal payload). Data Saver schedules 8 latency probes, 8 download samples, and 8 upload samples from 100 KB to 5 MB each (25.4 MB of nominal payload). In both modes, the first 100 KB sample in each direction is a calibration round that cannot end that direction early.
An overall grade requires idle, download-loaded, and upload-loaded latency; missing values are shown as partial or not measured. With all three present, Blockify takes the higher loaded value, subtracts idle ping, and never reports a negative increase. The label is Excellent at 15 ms or less, Good above 15 through 40 ms, Sensitive above 40 through 100 ms, and Congested above 100 ms.
The optional plan check divides measured download speed by the download speed you enter, then rounds the percentage: Above at 110% or more, Near at 90% through 109%, Worth a wired retest at 70% through 89%, and Well below under 70%. It is a diagnostic comparison, not a service-compliance decision.
4K streaming is Workable at 15 Mbps download and Ready at 25 Mbps. A busy household is Workable at 50/10 Mbps and Ready at 100/20 Mbps. Video calls are Workable at 2/2 Mbps or more, with ping no more than 200 ms, jitter no more than 40 ms, and loaded increase no more than 100 ms. Ready requires 5/5 Mbps or more, with limits of 100 ms, 20 ms, and 40 ms respectively. Gaming is Workable at 5/1 Mbps or more, with limits of 100 ms, 40 ms, and 100 ms; Ready requires 10/3 Mbps or more, with limits of 50 ms, 20 ms, and 40 ms. Every listed condition must pass. Missing required values produce Not measured; measured results below Workable are Limited.
Blockify stores recent measurements only in local browser storage. Page analytics and the engine’s completed-results logging are disabled on this route. Export happens only when you choose it.
One browser run cannot isolate a faulty cable, Wi-Fi interference, long-term uptime, or every route. Blockify does not present this custom sequence as a calibrated lab instrument or ISP line certification. Packet loss is not shown because this page does not run a supported UDP loss test.
Measurement engine: Cloudflare Speedtest (MIT-licensed). Cloudflare supplies the engine and routed edge; Blockify configures the limited sequence, interpretation bands, activity labels, and methodology version. The test starts only after your click, and final-result logging is off.
Privacy note: test requests necessarily expose your public IP to Cloudflare just as other internet requests do. Read Cloudflare’s privacy policy and Blockify’s privacy policy.