Use the same timing method. Relative changes do not establish a universal grade.
LOADED LATENCY
Bufferbloat Test and Fix: Compare Idle and Loaded Timing
Measure timing changes during transfers, repeat wired comparisons and evaluate router queue management without claiming a guaranteed fix.
Investigate bufferbloat by comparing idle response timing with timing during download and upload on the same endpoint. A repeatable increase suggests queueing pressure along the tested path. It does not locate the queue or prove how a particular application will behave.
How to run the check
- Record an idle baselineUse Ethernet when possible, pause other transfers and keep the endpoint unchanged. Save the timing method, median, sample counts and failures.
- Measure each transfer directionCheck download-loaded and upload-loaded timing separately. A busy upstream can delay otherwise small interactive messages.Open the relevant tool →
- Isolate local contentionRepeat on Ethernet and with other household traffic paused. A large change only on Wi-Fi can reflect radio contention as well as upstream queues.
- Evaluate one router changeConsult the router’s official documentation for supported queue management or shaping. Record original settings and compare repeat runs after one change. Throughput may fall when reserving headroom.
What the signals mean
Keep failure counts visible. Do not manufacture a numeric verdict from missing samples.
A lower throughput can be acceptable if the actual interactive problem improves; test the application too.
Frequently asked questions
Does a bufferbloat test prove my router is faulty?
No. Queueing, Wi-Fi contention, endpoint load and browser scheduling can affect results. Repeated controlled comparisons narrow the possibilities.
Do I need a new router?
First test the current equipment and consult its official queue-management documentation. A replacement is not justified by one synthetic test.