Peak vs. average latency on a Wi-Fi 6 access point

Your Wi-Fi connection may feel quick most of the time, then pause for a moment during a call or game. One latency number can hide those short delays. Comparing typical response time with the highest spikes helps you see whether the connection is steady, even when its average looks fine.

Use the Wi-Fi Signal test to watch response time, jitter, and lost requests on your device. The test does not read Wi-Fi signal strength in dBm, and an internet-based result cannot isolate the access point from the rest of your connection. You can still compare results in a consistent location and see whether spikes repeat.

Check latency near your access point

1. Open Wi-Fi Signal on the device you want to check. Keep it connected to the Wi-Fi 6 access point you are investigating.
2. Stay in one spot, preferably a few feet from the access point with no wall between you. Pause downloads, video streams, and cloud backups on this and other devices if possible.
3. Let the readings run for a few minutes. Note several response-time readings, the highest one you observe, any jitter changes, and whether requests are lost. The tool provides live connection-quality readings, not a guarantee of the access point's maximum latency.
4. Repeat the same check in the room where you notice the problem. Keep the device, access point, and other network activity as consistent as you can.
5. Run the check again at another time. A quiet network and a busy evening can produce different results, even in the same place.

For a simple average, add the response-time readings you wrote down and divide by the number of readings. For example, readings of 12, 13, 15, and 80 milliseconds average 30 milliseconds. The 80 ms peak raises that average, while the middle of the readings is around 14 ms. Keep both the average and the peak in your notes, since they answer different questions.

What the results mean

Low typical latency with a rare high peak

Most requests are responding quickly, but one or more delays are pulling up the average. A brief peak may be noticeable in a game or call if it happens at the wrong moment. Repeat the test: if the spike does not return, it may have been a temporary burst of network activity rather than a persistent access point problem.

High readings throughout the check

If most response-time readings are high, the issue is sustained rather than a single outlier. The delay could come from the wireless connection, the router, the internet service, or the test's route to its server. A browser test cannot prove which part is responsible on its own.

Jitter or lost requests appear along with spikes

Jitter means response time varies from one request to the next. Lost requests mean the test did not receive a response in time. Either can make a connection feel uneven, even if a separate speed test reports a strong download rate. Check whether the pattern repeats near the access point as well as farther away.

Results worsen farther from the access point

A clear difference between nearby and distant rooms points to a possible coverage or interference issue. The browser cannot report signal strength in dBm, so use the response-time pattern as evidence of how the connection behaves, not as a direct measurement of radio strength. For more detail on this limitation, see how to test Wi-Fi performance without dBm.

How to reduce spikes

1. Move closer for a comparison. Retest in the same room as the access point. If latency becomes steadier there, placement, distance, or obstacles may be part of the problem.
2. Check which Wi-Fi network you joined. On Windows 11, open Settings › Network & internet › Wi-Fi and confirm the connected network. On macOS, open System Settings › Wi-Fi. On a phone, check the network under Settings › Wi-Fi on iPhone or Settings › Network & internet › Internet on many Android devices. Menu names can vary by Android manufacturer.
3. Compare bands if your router offers separate networks. Try the same test on each available network name, then compare results in the same spot. A 2.4 GHz connection can reach farther but may face more interference. A 5 GHz connection can be faster nearby but may weaken sooner through walls. A 6 GHz band is available on Wi-Fi 6E or Wi-Fi 7 equipment, not on every Wi-Fi 6 access point.
4. Reduce competing traffic. Pause large downloads, backups, and video streams, then repeat the check. If spikes disappear, busy traffic may be affecting response time. A crowded network or an overloaded internet connection can cause this even when the access point is working.
5. Restart and update the access point. Use its manufacturer instructions to restart it and check for firmware updates. Avoid resetting it to factory settings unless you are ready to set up the network again.
6. Compare with a wired connection. If a computer connected by Ethernet has steady response time while Wi-Fi does not, focus on wireless coverage, interference, or access point settings. If both are poor at the same time, the cause may be farther upstream, such as the router or internet service.

What this test can and cannot tell you

Peak latency is the highest response time you observed during a particular check. It is not the worst delay the access point could ever produce. An average describes the readings you collected, but a short spike can make it less representative of what you usually experience. Note the number of minutes tested and the location each time so comparisons are meaningful.

Wi-Fi Signal measures how the wireless connection performs when reaching the test service. It does not read the access point's internal queue, show radio signal strength, or test only the local Wi-Fi link. Treat repeated results as a useful clue, then compare locations, times, and a wired connection before deciding what to change.