What it means
Every transfer passes through several links. The slowest relevant link can limit throughput, while competing devices share capacity. A fast Wi-Fi connection does not remove a slower internet uplink. File sizes often use bytes; eight bits make one byte, before accounting for transfer overhead.
How this affects everyday use
Congestion, a limited subscription, a slow cable link or heavy uploads can explain disappointing transfer speeds. A single remote server may also limit its own delivery.
A practical example
Two large downloads and a cloud backup share one connection, leaving less capacity for a meeting.
What to check
- Compare wired upload and download tests when other transfers are paused.
- Check Ethernet negotiation and Wi-Fi link details separately.
- Repeat with different destinations and inspect active background transfers.
Practical next steps
- Schedule large transfers away from time-sensitive work.
- Replace a confirmed faulty cable or slow link before buying a faster plan.
- Apply suitable traffic management when contention is the problem.
Keeping it reliable
Measure capacity and loaded latency together. Avoid promising application performance from the advertised number alone; server limits, overhead and signal conditions remain relevant.