Test latency after QoS changes on a dual-band router

You changed QoS on your router, but calls or games still lag when someone downloads or uploads. A speed test alone may not show whether the change helped, because the issue can be extra delay while the connection is busy.

Use the Bufferbloat Test to compare latency when the connection is quiet and under load. Keep the test conditions consistent, and check each Wi-Fi band separately if you want to know whether 2.4 GHz or 5 GHz is affecting the result.

Test latency before and after the change

1. Open the Bufferbloat Test and run it with your router's current QoS settings. Note the grade and the latency readings at rest and during download and upload, if shown.
2. For a useful baseline, use the same computer in the same spot and on the same Wi-Fi band each time. Pause streaming, cloud backups, game downloads, and other heavy network activity on your devices.
3. Run the test two or three times and write down the results. A single run can be affected by brief network activity or a temporary change in your internet connection.
4. Change one QoS setting in the router at a time. If the router needs to restart, wait until it reconnects, then confirm that your test device is back on the same band as before.
5. Repeat the tests under the same conditions. Compare the loaded latency and grade, not just the connection's download speed.

If your goal is to compare the bands, make a separate set of runs on each one while leaving the QoS settings unchanged. Use the router's connected-device list to check which band your device joined, if the router provides that information. Some routers combine both bands under one Wi-Fi name and select the band automatically.

What the result means

Loaded latency falls after the QoS change

This is a good sign. The router is likely managing queues more effectively when data is moving. If the test grade improves but download speed drops slightly, QoS may be trading a little peak speed for a more responsive connection under load. Check whether that tradeoff helps with your actual calls, games, or other latency-sensitive tasks.

Download latency improves, but upload latency stays high

QoS can behave differently in each direction. Upload traffic often causes noticeable delay when it fills the available upstream capacity. Check that the router's upload limit or traffic-shaping rate is set appropriately, if it has one, and test again. Router features use different names, so consult the instructions for your model rather than assuming a setting called QoS does the same thing on every router.

The grade changes, but the readings are close

A grade summarizes the test result, but small differences between runs may not be meaningful. Compare the actual latency readings across several runs. If they vary widely, repeat the test when no other device is using much bandwidth.

Latency is high even when the connection is idle

QoS mainly helps manage delay caused by traffic competing for a connection. It may not fix a weak Wi-Fi signal, interference, a slow route to the test server, or a problem with your internet provider. Test close to the router, then compare with a wired connection if you can. A wired result can help separate a Wi-Fi issue from a wider connection issue.

Results are different on 2.4 GHz and 5 GHz

The bands can behave differently in your home. A nearby 5 GHz connection may be faster, while 2.4 GHz may reach farther through walls. A poor result on one band does not automatically mean QoS failed. Compare each band in the same location, and keep the router configuration and other network activity unchanged.

How to improve the test and the settings

1. Pause other traffic. Stop large downloads, video streams, backups, and software updates before measuring. If you want to see how QoS handles real household use, run a second set of tests while that activity is happening and note what is running.
2. Keep the test device consistent. Use the same device, browser, location, and Wi-Fi band for before and after results. If you compare 2.4 GHz with 5 GHz, treat them as separate tests rather than changing bands halfway through a QoS comparison.
3. Check the router's prioritization rules. In the router's management app or admin page, confirm that the intended device or type of traffic is prioritized. A priority rule may not help if it targets a different device, or if the router does not recognize the traffic you want to favor.
4. Review bandwidth limits carefully. If your router offers traffic shaping or SQM, check its upload and download rates. A starting estimate around 90 to 95 percent of your consistently measured usable speed can help the router manage the queue, but the right value depends on your connection and router. Adjust in small steps and test after each change.
5. Check the Wi-Fi link. Move closer to the router for a comparison, and avoid changing the device position between runs. If one band performs poorly only at a distance, the cause may be coverage or interference rather than the QoS rule.
6. Update or restart the router if needed. Save the current settings before making changes. If results remain inconsistent, check the router maker's instructions for firmware updates and restart the router, then run the same comparison again.

Why the Wi-Fi band is only part of the result

Dual-band describes the router's local wireless connection. QoS usually manages how traffic shares the connection between your home network and the internet. The test result can therefore reflect both the Wi-Fi link between your device and router and the router's handling of traffic going to the internet.

For a closer comparison, test once over Wi-Fi and, if available, once with an Ethernet cable. Keep the QoS configuration the same. If loaded latency improves on Ethernet but not over Wi-Fi, investigate the wireless connection. If both results show high loaded delay, review the router's traffic-shaping settings and your internet connection. For a related look at prioritization, see how to compare SQM settings with a bufferbloat test.

The Bufferbloat Test sends test traffic to measure your connection. It does not read your router's private settings or files on your device.