Measure five HTTP response timings and report their median, then estimate download and upload rates from completed payload bytes and elapsed time.
Method, limits and data
This is a browser HTTP estimate, not ICMP latency, an ISP guarantee or a fixed service SLA. Blocked, stalled or rejected transfers remain unavailable; small fallback transfers are less representative. Examples and reference text are illustrative, not current measurements or guarantees of availability, precision or logging practices.
Transfers contact the existing Cloudflare endpoints; ping may use the existing Google fallback. Ten results remain in local browser history. Running a test consumes network data.
How to use
- Start the test when ready for data transfers.
- Wait through ping, download and upload; compare measured phases with their errors and history.
1,000,000 completed bytes in 1 second is 8 Mbps; 1,000 UTF-8 bytes in 1 second is 0.008 Mbps.
Does an upload refusal mean zero bandwidth?
No. HTTP 403 is a failed upload observation. An unavailable phase is shown as a dash, including in new history entries.
Invalid or empty input clears the previous answer. A timeout or refusal is a failed observation, not a zero measurement or proof of absence. Changing input discards late answers; retry only when ready.
Internet Speed Test
Measure five HTTP response timings and report their median, then estimate download and upload rates from completed payload bytes and elapsed time.
Note: This is a browser-based speed test. For more accurate results, use dedicated services.
Recent Tests
Copied
Copy failed. Select the result and copy it manually.
About Internet Speed Test
Measure five HTTP response timings and report their median, then estimate download and upload rates from completed payload bytes and elapsed time.
Compare repeated browser HTTP payload estimates under similar conditions. HTTP timing includes browser and service work; it is not ICMP latency, calibrated bandwidth metrology or proof that an ISP plan was delivered.
This is a browser HTTP estimate, not ICMP latency, an ISP guarantee or a fixed service SLA. Blocked, stalled or rejected transfers remain unavailable; small fallback transfers are less representative.
Transfers contact the existing Cloudflare endpoints; ping may use the existing Google fallback. Ten results remain in local browser history. Running a test consumes network data.
1,000,000 completed bytes in 1 second is 8 Mbps; 1,000 UTF-8 bytes in 1 second is 0.008 Mbps.
Use Cases
How to use
Start the test when ready for data transfers.
Wait through ping, download and upload; compare measured phases with their errors and history.
View your results in Mbps
Compare repeated browser HTTP payload estimates under similar conditions. HTTP timing includes browser and service work; it is not ICMP latency, calibrated bandwidth metrology or proof that an ISP plan was delivered.
Pro Tips
- Compare repeated browser HTTP payload estimates under similar conditions. HTTP timing includes browser and service work; it is not ICMP latency, calibrated bandwidth metrology or proof that an ISP plan was delivered.
- Close other apps/tabs during test
- Test at different times of day
Frequently Asked Questions
WiFi, network congestion, and ISP throttling can reduce speeds.
The displayed ping is a median of browser HTTP response times. It includes more than network transit and is not ICMP latency or a prediction of gaming performance.
Mbps (megabits) is 8x smaller than MBps (megabytes). ISPs advertise Mbps.
No. HTTP 403 is a failed upload observation. An unavailable phase is shown as a dash, including in new history entries.