Test History
No test history yet. Run a speed test to see your results here.
Network Information
Tips for Accurate Speed Tests
- Close other applications: Stop downloads, streaming, or other bandwidth-heavy activities
- Use wired connection: Connect via Ethernet cable for most accurate results (WiFi speeds can vary)
- Test multiple times: Run tests at different times of day to see variations
- Restart your modem/router: If speeds seem slow, try restarting your equipment
- Position matters: For WiFi, stay close to your router and minimize obstacles
- Check with ISP: Compare results with your internet plan's advertised speeds
Understanding Your Results
- Download Speed: Most important for streaming, browsing, and downloading files. 25+ Mbps is good for HD streaming.
- Upload Speed: Important for video calls, uploading files, and live streaming. 3+ Mbps is adequate for most uses.
- Ping/Latency: Critical for gaming and video calls. Under 50ms is good, under 20ms is excellent.
- Jitter: Shows connection stability. Under 10ms is ideal, under 30ms is acceptable.
- Connection Quality: Our overall rating based on all metrics combined.
How This Test Works
- Latency (ping): We send several small requests to Cloudflare's speed endpoint and measure the round-trip time of each. The reported ping is the median of those samples (the first, "cold" request is discarded because it includes DNS and TLS setup). Lower is better.
- Jitter: The variation between consecutive ping samples, calculated as the root-mean-square of successive differences. Lower jitter means a more stable connection.
- Download: We fetch sized chunks of data from Cloudflare for several seconds. Speed is computed as total bits received divided by total time: Mbps = (bytes × 8) ÷ seconds ÷ 1,000,000. This total-based method is more accurate than averaging individual chunks.
- Upload: We post randomly generated data to Cloudflare's upload endpoint and measure the time taken, using the same bits-over-seconds formula.
Honest Limitations
- This test runs entirely in your browser using the fetch API. Browser and JavaScript overhead, request setup, and connection limits mean it cannot match a dedicated, multi-connection desktop speed test.
- It uses a single provider (Cloudflare). Distance to Cloudflare's nearest server affects ping and can cap measured speed, so results may differ from tests that pick a geographically closer server.
- Upload numbers are the least reliable. The upload payloads are relatively small, so latency and request overhead have an outsized effect and may understate fast connections.
- Very fast connections (gigabit and above) may be underreported because a single browser fetch stream cannot always saturate the link.
- Treat the results as a useful real-world estimate, not a precise certified measurement.