Bandwidth describes capacity, throughput describes achieved transfer rate, and latency describes delay. A high-capacity connection can still feel unresponsive if queues, packet loss, Wi-Fi contention, or a distant server delay small requests.
Keep bits and bytes straight
Internet plans usually use megabits per second, written Mbps or Mbit/s. Downloads may display megabytes per second, written MB/s. Eight bits make one byte, so 100 Mbit/s has a theoretical ceiling of 12.5 decimal MB/s before overhead and other limits.
Decimal GB and binary GiB also differ. A 1 GB file is 1,000,000,000 bytes; 1 GiB is 1,073,741,824 bytes. Choosing the wrong unit can make an otherwise correct transfer estimate look inaccurate.
Calculate a transfer, then add context
A 5 GB file contains 40 billion bits. At a constant 100 Mbit/s, the ideal transfer takes 400 seconds, or 6 minutes 40 seconds. At 80% of that rate, the estimate becomes 500 seconds, or 8 minutes 20 seconds. Startup, retransmissions, storage speed, and server throttling can make the real result longer.
The same file over a much faster link can finish sooner while a game still feels sluggish. Games and calls depend heavily on timely delivery of smaller exchanges; downloading an extra large file is a different workload.
Match the measurement to the complaint
| Complaint | Measure first |
|---|---|
| Large downloads are slow | Sustained throughput, server limits, storage, competing traffic |
| Calls break up | Loss and delay variation during the call |
| Everything pauses during upload | Loaded latency and upload saturation |
| First page load stalls | DNS, connection setup, server response, then page assets |
Use Ethernet for a baseline, stop unrelated transfers temporarily, and compare more than one reputable destination. A speed test reports its own path and workload at a particular time. It is not a promise that every remote service will deliver that rate.
Choose the change that addresses the limit
A larger Internet plan may help when total household demand regularly reaches the line's capacity. It may do little for a weak Wi-Fi link, overloaded access point, distant server, or poorly managed queue. Improving access-point placement, wired backhaul, or queue management may address those constraints more directly.
Compare idle and loaded ping while watching upload and download use. If latency rises dramatically under load, inspect bufferbloat and supported smart queue management. Keep the baseline and change one setting at a time so a faster speed-test number does not obscure worse call quality.
Put it into practice
References & further reading
Protocol standards and official documentation supporting this guide. Device menus and provider policies vary; use the documentation for your equipment when applying a change.