Wi-Fi response-time spikes during a four-person call

During a four-person video call, a frozen face or choppy voice can make it seem like your Wi-Fi is failing. A speed test may still look fine because a brief delay can interrupt a call without lowering the connection's peak speed.

Check the connection while the call is happening, then compare the timing of any pauses with the test results. Wi-Fi Signal measures response time, jitter and lost requests in your browser. It cannot measure Wi-Fi signal strength in dBm, and its route to the test server may differ from the route your call uses, so treat it as evidence rather than a verdict.

Check for response-time spikes during the call

1. Join the call on the computer with the problem. Keep your camera and microphone settings as they were when the issue happened, and note the time if audio or video freezes.
2. Open the Wi-Fi Signal in another browser tab. Let it measure the live connection while the call continues. Avoid starting a download or a separate speed test, since extra traffic can change the result.
3. Watch for response-time spikes, jitter, or lost requests. Note the time of each noticeable change and whether it matches a freeze, voice break, or delay in the call.
4. Keep observing for several minutes, including a period when the call is working normally. A single spike is less useful than a repeated pattern that appears alongside the call problem.
5. If you need a longer record, use Connection Stability after the call or during a separate test period. Compare its results with what you observed, but do not run a second test at the same time and assume the measurements are independent.

Try to keep the conditions consistent when comparing results. Use the same computer and place, and avoid moving between rooms or changing Wi-Fi bands halfway through. If other people are sharing the network, note whether they are streaming, gaming, or uploading files.

What the result means

Spikes happen when the call freezes

This is evidence of a connection delay or interruption that could affect the call. It does not prove the Wi-Fi link is the cause: the delay could be on the internet route, at the router, or elsewhere between the browser and TooLab's test server. Repeat the check, then compare Wi-Fi with a wired connection if you can.

The connection has high jitter but few lost requests

Jitter means that response times vary instead of staying steady. Real-time audio and video can be affected by changing delays, even if most requests get through. A brief variation may be harmless, but repeated large changes that coincide with choppy speech are worth investigating.

Requests are lost or the connection drops

Lost requests mean the test did not receive a response in time. Repeated losses can cause a call to pause or recover, but this browser test cannot identify exactly where they were lost. Check whether the problem happens on one device or across several devices on the same network.

The test looks steady while the call is still choppy

The call may be affected by a different network route, the meeting service, the computer's workload, or the app's audio and video processing. A browser test cannot measure the call's exact media path. Check the meeting app's own connection or call diagnostics if available, and close unnecessary CPU-heavy apps.

Response time rises when someone else uses the network

That pattern points toward congestion or queues building up at the router or internet connection. A four-person call does not automatically mean four people are using your home network, but multiple video streams and other household activity can add traffic. Look for uploads and downloads happening at the same time as the spikes.

How to reduce spikes

1. Move closer to the router. Test from the same room, with fewer walls or large objects between the computer and router. If the call improves there, coverage or interference may be part of the problem.
2. Pause competing traffic. Stop large uploads, cloud backups, game downloads, and video streams during an important call. Ask other people on the network to pause heavy transfers briefly, then see whether the timing of the spikes changes.
3. Reconnect to Wi-Fi. Turn Wi-Fi off and back on, then rejoin the network. On Windows 11, check Settings › Network & internet › Wi-Fi. On macOS, open System Settings › Wi-Fi. If the problem affects a phone instead, reconnect it to Wi-Fi and check whether the call improves near the router.
4. Restart the router once. If several devices have interruptions, unplug the router's power, wait about 30 seconds, and reconnect it. Give it a few minutes to come back online before testing again. Avoid repeated restarts during the call.
5. Compare with Ethernet. If possible, connect the computer to the router with an Ethernet cable and repeat the call check. If the spikes stop on Ethernet but return on Wi-Fi, focus on wireless coverage, interference, or router placement. If they remain, the problem may be beyond the Wi-Fi link.
6. Update the computer and router. Install available network driver or operating system updates, and check the router maker's instructions for firmware updates. Change one thing at a time so you can tell whether it helped.

Why a steady test may not guarantee a steady call

A browser test and a video meeting do not necessarily contact the same server or use the same network route. The Wi-Fi Signal test is useful for spotting response-time changes, jitter, and missed requests from your device, but it does not inspect the call's video quality, the meeting service, or your router's radio signal level.

Video calls also adjust picture quality when conditions change. A brief freeze can be caused by a slow computer or an app issue even when the browser test looks steady. If only one participant appears frozen, ask whether other people can see and hear them. If everyone freezes at the same moment, check your local network and the call app's diagnostics together.