How to compare wired and wireless loaded latency

Your connection may feel responsive until someone starts a download or upload. To find out whether Wi-Fi adds to the delay, compare it with Ethernet using the same computer and the same test.

The Bufferbloat Test measures how much response time grows while data is being downloaded or uploaded. Run it once over Wi-Fi and once over a wired connection, then compare the results under similar conditions.

Compare wired and wireless latency

1. Open the Bufferbloat Test on the computer you will use for both runs. Keep the same browser and close any other test tabs.
2. Connect over Wi-Fi and run the test. Note the grade and the response-time results during download and upload. Also note whether the connection drops or the results vary sharply.
3. Connect the same computer to the router with an Ethernet cable. Turn off Wi-Fi if the computer might keep using it, then repeat the test.
4. Repeat each run once or twice. Keep other internet use, such as streaming, cloud backups, and large downloads, paused for both sets of runs.

For a fair comparison, use the same room and computer if possible. If the Ethernet cable only reaches the router, the wired result still gives you a useful reference, but it also changes the computer's location. To separate the effect of Wi-Fi from distance and walls, compare from a place where you can test both connections.

What the result means

Wi-Fi has more delay under load than Ethernet

The wireless connection may be adding delay, or it may be less consistent. Radio interference, distance, walls, and other devices using the same wireless network can all affect the result. If the gap appears in repeated runs, check the Wi-Fi connection and router placement before changing your internet plan.

Both connections have similar loaded delay

Wi-Fi is probably not the main cause of the delay you measured. The router, internet connection, or the route to the test server may be contributing. A browser test measures the whole path between your computer and the server, not just the link inside your home.

Both connections get much slower under upload or download load

A similar problem on Ethernet and Wi-Fi points away from wireless as the only cause. The connection may be building a queue when it is busy, or another device may be filling the available bandwidth. Check whether the result changes when other household traffic is paused.

The results change a lot between runs

One run is not enough to pin the cause on Wi-Fi. Background traffic, changing radio conditions, or congestion farther along the connection can shift the readings. Compare several runs at different times before deciding that a cable or router setting fixed the issue.

The grade is good but calls or games still lag

The grade describes the test's response-time increase under its test load. It does not guarantee that every app, server, or game will respond the same way. If the problem happens only in one service, its server, route, or app may be involved.

How to reduce the difference

1. Pause other network activity. Stop cloud backups, large downloads, and video streams while testing. On Windows 11, check Settings › Network & internet for the active connection. On macOS, open System Settings › Network to confirm whether you are using Wi-Fi or Ethernet.
2. Move closer to the router. Test Wi-Fi in the same room as the router, then at the usual work or gaming location. If the result improves nearby, distance or obstacles may be part of the problem.
3. Check the Ethernet connection. Reseat the cable at both ends and try another router port or cable. A cable that appears connected can still have a damaged plug or an unreliable connection.
4. Restart the router. Restart it using its normal power procedure, wait for the internet connection to return, then run both tests again under the same conditions.
5. Compare at another time. Repeat the paired tests when fewer people are using the connection. If both wired and wireless results worsen at busy times, the cause may be upstream of your Wi-Fi link.
6. Review router traffic settings. If the delay rises sharply when the connection is busy, look for traffic-priority or queue-management options in the router's own settings. Change one setting at a time and retest both connection types.

Why loaded latency is different from idle ping

Idle latency is the response time when little data is moving. Loaded latency is measured while the connection is busy carrying test traffic. The difference matters because a connection can have a low idle ping but become sluggish when a large upload or download fills a queue.

The Bufferbloat Test sends test data to measure the connection while it is under load. That means it checks more than the Wi-Fi radio: the computer, router, internet service, and route to the test server can all affect the result. Use repeated wired and wireless runs to compare those complete connection paths, not to diagnose a single component from one score.