Measure this browser-to-edge route with a published method. No app install required.
WiFiSpeedTest.io transfers measured byte counts between this browser and the site's Cloudflare edge, then divides bytes by elapsed time to estimate throughput. It also times repeated requests for RTT and jitter. Saved history and plan speed stay in this browser's local storage; normal server, Cloudflare, advertising, and aggregate analytics processing is described in the Privacy Policy. See Data & Methodology for formulas and limitations.
Streaming: Netflix currently lists 3 Mbps for 720p HD, 5 Mbps for 1080p, and 15 Mbps for 4K per stream. Add simultaneous streams and other traffic. Netflix source.
Video meetings: Zoom currently lists up to 3.8 Mbps download and 3.0 Mbps upload for 1080p group video; Microsoft lists 4/4 Mbps per endpoint for best-performance Teams meeting video. Actual use adapts to layout and quality. Zoom source · Teams source.
Household planning: Add the per-device requirements for activities that happen at the same time, then compare repeated tests with the current broadband label and plan speed supplied by your ISP.
A WiFi result includes the wireless link, device, browser, other local traffic, access network, and route to the test edge. An Ethernet comparison under the same conditions can help isolate the WiFi portion, but neither result alone proves where a bottleneck is.
Repeatable test: Keep the device and connection type fixed, pause other traffic, run multiple tests, and compare medians at documented times. Do not assume a universal peak-hour window; your own saved history provides the relevant evidence.
Latency (RTT) is elapsed round-trip time to this site's edge, measured in milliseconds. Lower values leave less network delay, but application requirements vary by service and route.
Jitter here is the mean absolute difference between consecutive successful RTT samples. It describes variation on this test route.
Packet loss: this browser test does not send ICMP probes and does not claim to measure end-to-end packet loss. A failed HTTP sample is reported separately rather than converted into a network-wide loss claim.
Click START to measure application-layer download, upload, HTTP RTT, and RTT variation between this browser and the site's Cloudflare edge.
Add the current per-device requirements for simultaneous activities. Netflix lists 3 Mbps for 720p, 5 Mbps for 1080p, and 15 Mbps for 4K per stream; meeting providers publish separate upload and download requirements.
Repeat the test, pause other traffic, compare Ethernet and WiFi under the same conditions, and compare the result with the current plan speed and broadband label from your ISP. Change one variable at a time so the result supports the conclusion.
This page measures HTTP round-trip time to its Cloudflare edge. Lower is less delay on that route, but it does not measure every application server.
Download is data received by the browser; upload is data sent from it. Your plan may advertise different rates in each direction, so compare each result with the current figures supplied by your ISP.
The result includes the device, browser, local network, access network, and route to this edge. Compare repeated Ethernet and WiFi tests with the ISP's current broadband label before assigning the difference to one cause.
Test often enough to capture the problem you are investigating. Keep the setup consistent and save timestamps so your own history—not a universal schedule—shows whether a pattern exists.
It measures application-layer throughput and RTT between this browser and the Cloudflare edge serving the test. Another tool may differ because its route, server, payload, concurrency, browser, device, and current traffic differ.