Idle latency
Your baseline response time when the connection is relatively quiet.
Check whether your broadband stays responsive while downloads, uploads and other devices place the connection under pressure.
Connection responsiveness
A normal speed test measures capacity. A loaded latency test asks a different question: what happens to ping when the line is carrying a large download or upload?
Troubleshooting route
Broadband troubleshooting hub → start with the issue, validate the cause, then follow the matching fix steps.
Issue → Validate → Fix
| Issue | Validate | Fix |
|---|---|---|
| Idle latency is low | The line is fine when quiet | Check download-loaded and upload-loaded latency next. |
| Upload loaded latency is high | Backups, CCTV or file uploads filling upstream | Pause uploads or configure SQM/QoS. |
| Both loaded results are high | Router queues, Wi‑Fi or provider congestion | Compare Ethernet and Wi‑Fi, then test at another time. |
Free browser test
The LinkSpeed bufferbloat test measures a quiet baseline, creates download and upload traffic, and continues checking latency while the connection is busy. It then reports the worst added delay.
Latency—often called ping—is the time taken for a small request to travel to a server and return. It is measured in milliseconds. Throughput and latency describe different parts of broadband performance: a connection can move a great deal of data each second but still respond slowly when its queues fill.
Your baseline response time when the connection is relatively quiet.
Ping measured while incoming traffic is filling the available download capacity.
Ping measured while outgoing traffic is filling the usually smaller upload capacity.
The loaded result minus the idle result. This is the most useful comparison.
Use the largest increase above idle latency from the download and upload phases. Lower is better.
| Added latency | LinkSpeed rating | Likely experience under load |
|---|---|---|
| 0–5 ms | A+ Exceptional | Responsiveness changes very little. |
| 6–15 ms | A Excellent | Well controlled for gaming, calls and mixed use. |
| 16–30 ms | B Good | Usually comfortable, with occasional small delays. |
| 31–60 ms | C Fair | Lag may become noticeable while the line is busy. |
| 61–120 ms | D Poor | Games, calls and interactive apps may struggle. |
| Over 120 ms | F Severe | Heavy traffic is likely to cause obvious delay. |
These are LinkSpeed guidance bands, not an industry certification. Browser load, Wi-Fi, VPNs, other users, routing and the test server can affect results. Repeat the test before changing equipment.
Inputs and voice chat can lag when another device downloads a game or uploads video.
Queued packets can cause delayed speech, frozen video and people talking over one another.
Cloud sync can make remote desktops and web applications feel slow despite high download speed.
Changing capacity and signal conditions can produce unstable loaded latency on 4G or 5G services.
When a connection reaches capacity, routers, modems and network equipment hold packets in a queue. Some queuing is normal. The problem appears when the queue becomes unnecessarily long and small, time-sensitive packets must wait behind bulk traffic.
Normal or idle ping is measured when the connection is quiet. Loaded latency measures ping while download or upload traffic is competing for capacity.
Many broadband packages have substantially less upload capacity than download capacity. A backup or large file upload can therefore fill the upstream queue much more easily.
Extra capacity can make saturation less frequent, but speed alone does not guarantee good queue management. A correctly configured router may make a larger difference under full load.
Yes. Full fibre can provide excellent capacity and low idle latency, but queues can still build when the connection is saturated or the router handles traffic poorly.
Test Ethernet first for the clearest line/router result, then repeat on Wi-Fi to understand the experience at the device.