Idle latency
The quiet baseline before the connection is saturated.
Reduce ping spikes when your broadband is busy by controlling the queue at the real bottleneck—not by chasing headline speed alone.
Practical router optimisation
The most effective fix is usually to let your router manage the bottleneck deliberately, keeping queues short while sharing capacity between active devices.
Save or photograph the current configuration, confirm how to restore factory settings and change one thing at a time. Do not install third-party firmware unless the exact hardware revision is supported and you understand the recovery process. Provider phone services, TV products and support arrangements may depend on the supplied router.
The short version
Step 1
Use Ethernet from one computer to the main router, turn off that computer’s Wi-Fi, pause unrelated downloads and uploads, and temporarily disconnect a VPN where policy allows. Run the LinkSpeed test at least twice.
The quiet baseline before the connection is saturated.
Ping while incoming traffic fills the downstream capacity.
Ping while outgoing traffic fills the upstream capacity.
The loaded result minus the idle baseline—the key comparison.
If repeated tests show little increase, bufferbloat may not be the main fault. Investigate packet loss, Wi-Fi, provider congestion, device load or routing instead.
Step 2
| Test pattern | What it suggests | Best next step |
|---|---|---|
| Ethernet poor; Wi-Fi poor | The queue is likely in the router, modem or wider broadband path. | Configure queue management and shaping on the main gateway. |
| Ethernet good; Wi-Fi poor | Wireless interference, signal or mesh backhaul is adding delay. | Improve Wi-Fi separately rather than sacrificing line speed. |
| Upload much worse than download | The smaller upstream link is easy to saturate. | Prioritise upload shaping and control cloud/CCTV traffic. |
| Only poor in the evening | Available capacity may change with provider or mobile-network load. | Test at several times and use a conservative or adaptive rate. |
| Idle latency already high | The fault is not solely queue growth under local load. | Check signal, VPN routing, provider routing and fault status. |
Step 3
Router menu names vary. Search the manual for Quality of Service, QoS, Smart Queue Management, SQM, traffic shaping, congestion control or bandwidth management.
| Feature | What it usually does | Bufferbloat usefulness |
|---|---|---|
| Device priority | Favours one console, PC or call device. | May help that device but does not necessarily keep the total queue short. |
| Traditional QoS | Classifies traffic into priority groups. | Can help when configured well; quality varies considerably. |
| Adaptive QoS | Adjusts priorities or rates using router rules. | Potentially useful, but implementation and automatic rate detection matter. |
| SQM | Shapes the bottleneck and actively manages queues. | Usually the most direct home-router approach. |
| CAKE | Combines shaping, queue management and flow fairness features. | Strong option where supported and within router CPU capacity. |
| FQ-CoDel | Separates flows and controls persistent queue delay. | Effective, widely used and often less demanding than complex policies. |
| Bandwidth limiter | Caps a device or the whole connection. | Crude fallback that can prevent full saturation. |
Fair queueing is usually better than permanently giving one person absolute priority: it lets small interactive flows pass without allowing one bulk transfer to dominate.
Step 4
Queue management works best when the router becomes the narrowest controlled point. Start around 90–95% of stable wired speeds, then tune from real results. Variable 4G/5G, cable and busy shared connections may need more headroom.
Enter stable wired results—not the package’s advertised maximum.
Check the units: some router pages use Kbps or kbit/s rather than Mbps. For example, 18.4 Mbps is 18,400 Kbps. Entering 18.4 where the router expects Kbps could make the connection extremely slow.
Step 5
If enabling SQM cuts speed far beyond the configured headroom, the router’s processor may not handle queue management at the line rate. Check CPU load, hardware acceleration interactions and the router’s documented limits.
Step 6
Start a controlled download elsewhere and watch in-game ping and voice chat.
Check speech delay and stability while a cloud upload uses the connection.
Test VPN apps, remote desktop and cloud sync together.
Confirm fair performance when several people stream, browse and download.
A synthetic grade is useful, but the goal is a connection that remains responsive during the activities your household actually performs.
Cap the heaviest devices or background applications so they cannot fill the entire link.
Run game downloads, cloud backup and large uploads outside calls or gaming sessions.
Use the provider device in modem or bridge mode only where supported and compatible with phone/TV services.
Confirm WAN type, authentication, ONT/modem arrangements, port speed and support before buying.
Third-party firmware can add features to supported equipment, but a wrong image or interrupted update can make a router unusable and may affect warranty or provider support.
| Problem after enabling SQM | Likely cause | What to check |
|---|---|---|
| Speed far below the set rate | Router CPU limit, incorrect units or conflicting acceleration | CPU load, Kbps/Mbps units, hardware/NAT acceleration guidance. |
| Upload improves but download does not | Ingress shaping is harder or the downstream queue is elsewhere | Correct WAN interface, download rate and modem/router topology. |
| Results change every evening | Underlying capacity varies | Use a lower busy-time rate or suitable adaptive shaping. |
| Wi-Fi still lags | Wireless airtime, signal or mesh backhaul problem | Compare Ethernet, reposition equipment and improve Wi-Fi separately. |
| Gaming improves but downloads crawl | Limits are too conservative | Increase one direction gradually while watching added latency. |
| Double NAT appears | A second router was added without bridge/modem mode | Network topology, provider device mode and service compatibility. |
It reduces how often the line becomes full, but it does not guarantee well-managed queues. Upload capacity and router behaviour still matter.
Sometimes. Look for QoS, traffic prioritisation, bandwidth control or gaming modes. Provider routers vary and some expose only basic controls.
Device priority can help one machine, while effective fair queueing aims to keep all small interactive flows responsive. SQM is usually the more complete approach where available.
Many packages provide much less upload than download capacity, making it easier for cloud backup, CCTV or file sharing to saturate the upstream queue.
Usually not. Use stable measured throughput and leave enough headroom for your router to control the bottleneck.
It can, but queue management at gigabit speed requires capable hardware. An underpowered router may reduce throughput substantially.