How to spot repeated latency spikes during a workday

A call freezes for a moment, a remote desktop stops responding, or a work page takes too long to load, then everything seems normal again. When the problem comes and goes, one speed test may miss it.

Use the Wi-Fi Signal tool at several points during your workday. It shows response time, jitter and dropped requests, so you can note whether brief interruptions happen repeatedly and what else is going on at the time.

Track latency spikes during the day

1. Open the Wi-Fi Signal tool on the device that has the problem. Keep the page visible and the device awake while you observe it.
2. Watch the results for a few minutes when the connection feels normal. Write down the time and the usual response time, jitter and number of drops. These give you a baseline to compare with.
3. Check again when a call, remote desktop or work site stalls. Note the time and whether response time rises, jitter increases, or requests are lost. Also note your location and any large downloads, uploads or video calls in progress.
4. Repeat the checks at different times, including when the problem is not happening. For a longer check during a suspected interruption, use Connection Stability, which tracks response time, jitter, lost requests and dropouts over a few minutes.

A short log is more useful than a single dramatic number. For example, note “10:15 a.m., desk, video call, repeated drops” rather than relying on memory later. The tools do not create a workday history for you, so write down the readings as you observe them.

What the results mean

Response time rises at the same time as the interruption

Response time is how long it takes for a test request to receive a reply. A sudden rise at the time your work app stalls is evidence of a connection delay, but it does not by itself identify whether the cause is Wi-Fi, your router, your internet provider or the test server. Compare the time and conditions with other checks before changing equipment.

Jitter increases, even when the average seems acceptable

Jitter is variation in response time. If some replies are quick and others much slower, calls and remote controls can feel uneven even when a single average looks fine. Repeated jitter increases during your work calls point to inconsistency worth investigating.

Drops or lost requests appear during a stall

A lost request means the test did not receive a reply in time. Several losses clustered around an interruption are a stronger clue than one isolated lost request. They still do not prove that the Wi-Fi radio itself is at fault, because the test also depends on the router, internet path and server.

The readings stay steady while the work app stalls

The test did not see a matching connection problem at that moment. The app, its service, a VPN, or the device may be responsible instead. Repeat the check while the fault is actually happening, because a brief issue can end before you open the test.

Spikes happen only in one place or during heavy network use

A pattern tied to a room may point to weak or obstructed Wi-Fi coverage. If spikes appear when someone uploads a large file or starts a video stream, the connection may be busy or delayed under load. Compare like with like: same device, same location and roughly the same time of day.

How to reduce or isolate the spikes

1. Check whether other activity starts at the same time. Pause large cloud backups, downloads or uploads briefly, if you are allowed to, and observe whether the spikes stop. A work VPN or security tool can affect the route too, but do not disconnect an employer-required VPN without permission.
2. Move closer to the router. Run the same check in your usual workspace and near the router. If the results improve nearby, distance, walls or interference may be affecting the wireless connection. Keep the device and test duration consistent.
3. Reconnect to Wi-Fi. On Windows 11, open Settings › Network & internet › Wi-Fi, disconnect from the network, then reconnect. On a Mac, open System Settings › Wi-Fi, turn Wi-Fi off and back on, then reconnect to your network.
4. Compare with a wired connection if available. Connect the computer to the router with Ethernet and repeat the checks. If the wired connection stays steady while Wi-Fi spikes, focus on the wireless link or access point. If both have similar spikes, investigate the router, internet service or work network instead.
5. Restart the router at a suitable time. Ask other people on the network first, since restarting it disconnects everyone. After it comes back online, repeat your checks in the same location and during a similar type of work activity.
6. Contact your IT team or internet provider with the log. Share several timestamps, the response-time and jitter changes, any lost requests, your location and whether you were on Wi-Fi or Ethernet. This is more useful than reporting that the internet was “slow all day.”

What this test can and cannot tell you

Wi-Fi Signal measures how the connection responds, including response time, jitter and lost requests. A browser cannot read the Wi-Fi signal strength in dBm, the radio measurement often shown by specialized network tools. The results describe connection quality, not a direct measurement of radio power.

Because the test sends requests beyond your device, a spike can occur somewhere between the computer and the test server. Use location comparisons and, when possible, a wired comparison to narrow down the likely cause. If a work application stalls while the readings remain steady, report that difference to your IT team instead of assuming the Wi-Fi is responsible.