How to read an internet speed test.
The three main numbers describe capacity and delay. Reading them together is more useful than chasing the highest download score.
Updated September 19, 2026 · 7 minute read
Download speed
A download speed test measures the rate at which data reaches your device, usually shown in megabits per second (Mbps). Streaming video, loading large websites, installing apps, and downloading files rely heavily on it. A result is shared capacity: several active devices can divide what is available.
Upload speed
An upload speed test measures the rate at which your device sends data. Video calls, posting large media, cloud backup, and live streaming can feel poor even when download speed is high. Many residential plans provide less upload capacity than download capacity.
Ping and latency
Ping latency is time, usually measured in milliseconds (ms). Lower is better. It affects the delay before a page begins loading, how natural a call feels, and how quickly an online game reacts. A connection can have high bandwidth and still feel slow when latency is high or inconsistent.
How much speed is enough?
Requirements vary by service, quality setting, number of devices, and background activity. These figures are planning ranges, not guarantees.
| Activity | Useful connection characteristics |
|---|---|
| Browsing and email | Modest download speed; responsive latency matters. |
| HD video | Roughly 5–10 Mbps per stream, with stable delivery. |
| 4K video | Often 25 Mbps or more per stream, depending on the service. |
| Video calls | Stable upload and download, commonly a few Mbps each, plus low jitter. |
| Online gaming | Usually modest bandwidth, but low and stable latency is important. |
| Large backups | Upload speed determines completion time. |
Why results change
- Wi-Fi conditions: distance, walls, interference, frequency band, and router placement affect the local link.
- Shared traffic: streaming, updates, backups, and other users compete for capacity.
- Device load: browser extensions, power saving, processor load, and memory pressure can influence a browser test.
- Routing and server load: every destination follows a path that can change or become congested.
- VPNs and relays: encryption and a longer network path can reduce throughput or add delay.
Run a test you can trust
- Pause downloads, backups, and streaming on the test device.
- For a Wi-Fi baseline, stand near the router. For the internet-plan baseline, use wired Ethernet where possible.
- Run at least three tests and use the middle result, not only the fastest.
- Repeat at different times if the issue is intermittent.
- Compare results using the same device and location before and after a change.
What to do next
If the result is poor only on Wi-Fi, focus on the local wireless network. If wired and Wi-Fi results are both much lower than expected, check the modem, router, provider status, and plan. If throughput is fine but services feel delayed, investigate latency, DNS, VPNs, and routing.