The short answer
The most effective form of QoS is smart queue management, which caps your bandwidth slightly below the line’s capacity so the router controls the queue rather than your provider’s equipment. That single change fixes the video calls and games that break when someone starts a download, and it matters more than per-device prioritisation.
When a connection is saturated, packets queue somewhere. If they queue in your provider’s equipment, that queue is large and uncontrolled, and latency rises dramatically, which is what makes a call stutter while a download runs. If they queue in your router, which understands what is urgent, the same download barely affects anything.
The problem, briefly
This is bufferbloat. A speed test can show your full advertised speed while latency under load rises from 20 milliseconds to 400, and that latency is what you actually experience as the connection being broken. Testing specifically for it, using a test that measures latency while loading the connection, is the way to see whether you have it.
Smart queue management
The fix is to move the queue into your router by telling it your connection speed and letting it shape traffic accordingly. Routers implement this under various names: Smart Queue Management, SQM, Adaptive QoS, Dynamic QoS or Bufferbloat Reduction.
Measure your real speed first
Wired, with nothing else running, several times. Note download and upload.
Enable the queue management feature
In the router’s QoS or traffic control section.
Set the limits to about 90 percent of measured speed
Slightly lower than the line can carry, so the router remains in control of the queue.
Set upload carefully
Upload is usually the bottleneck and the one that causes call problems, and it benefits most from being capped correctly.
Test latency under load
Using a bufferbloat test before and after. A good result is latency rising by only a few tens of milliseconds while the connection is saturated.
Adjust downward if latency is still poor
Some connections need 85 percent or lower. The small speed sacrifice is worth it.
You are deliberately giving up a little speed for a large reduction in latency under load. On a 200Mbps connection, capping at 180Mbps costs you nothing perceptible and can be the difference between a video call that works while someone downloads a game and one that does not.
Per-device and per-application prioritisation
Many routers also offer priority rules. These are useful and less important than queue management:
- Prioritise devices that need low latency: a work laptop, a games console, a video calling device.
- Deprioritise devices that only need bulk throughput: a media server, a backup machine, a games console when it is downloading rather than playing.
- Application categories, where the router recognises video calls or gaming traffic. Accuracy varies, since much traffic is encrypted and difficult to classify.
- Schedules, so backups and updates run overnight rather than during the working day.
Keep the rules simple. A complex set of priorities is hard to reason about later and frequently does not do what its author intended.
What QoS cannot do
- It cannot create bandwidth. If the line is genuinely too slow for what the household does, prioritisation only chooses who suffers.
- It cannot fix Wi-Fi congestion, which is a separate problem with separate solutions.
- It cannot control traffic arriving from outside as precisely as traffic leaving, though modern implementations manage the inbound direction reasonably well.
- It cannot help if the bottleneck is on the provider’s network rather than your connection.
Router capability
Queue management requires processing power, and on a modest router enabling it can cap your maximum throughput. If your connection is fast and your router is basic, you may find it cannot shape at full speed. The router’s documentation usually states the maximum speed at which the feature works.
Where the built-in implementation is poor, community firmware on supported models offers considerably better queue management, at the cost of installing it and accepting the risks.
Set the bandwidth limits using your own measured speed rather than the speed on your contract. Contracted speed is an average or a maximum, and shaping against a number your line does not actually achieve leaves the queue outside your router, which means the feature does nothing.
What is bufferbloat?
Excessive queuing in network equipment when a connection is saturated, which causes latency to rise dramatically. It is why a call breaks when someone starts a download even though the speed test looks fine.
Will QoS slow my internet down?
Slightly and deliberately. Capping at around 90 percent of your measured speed keeps the queue in your router, which trades a small amount of throughput for a large reduction in latency under load.
Should I prioritise devices or use queue management?
Queue management first, because it addresses the underlying problem. Per-device priorities are a useful refinement afterwards, and they do not fix bufferbloat on their own.
Why does my router's QoS make no difference?
Usually because the bandwidth limits were set from the contracted speed rather than the measured one, or because the router lacks the processing power to shape at your line speed.
Does QoS help with Wi-Fi problems?
No. It manages traffic through your internet connection. Wi-Fi congestion, weak signal and channel interference are separate problems with separate fixes.
The short version
Measure your real wired speed, then enable smart queue management with the limits set at about 90 percent of it, paying particular attention to upload. Test latency under load before and after, and reduce the cap further if it is still poor. Add a few simple device priorities afterwards, and remember that none of this creates bandwidth that the line does not have.
