Why packet loss matters more than peak speed
Learn why brief packet loss can disrupt calls, games, and remote work even on a fast connection, then test stability and find where to look next.
Your speed test says the internet is fast, but a video call still freezes or an online game keeps stuttering. A high peak speed shows how quickly data can move in a short test. It does not tell you whether the connection keeps delivering data without interruption.
Even brief packet loss can delay or interrupt the small pieces of information apps exchange. Use the Connection Stability test to check for lost requests and dropouts, then compare the result with a separate speed test.
Check for connection interruptions
- Open the Connection Stability test on the device that has the problem. Run it for a few minutes from the usual spot where you use the internet.
- Leave your normal connection setup in place for this first check. Note whether the test reports lost requests or dropouts, along with response time and jitter. Jitter means response time that changes from one request to the next.
- If the problem happens at a particular time, repeat the test while it is happening. Write down the time and what you were doing, such as joining a call or playing a game.
- Then run the Speed Test separately to check download speed, upload speed, ping, and jitter. Compare it with the stability result, rather than treating a fast speed result as proof that the connection is reliable.
For a useful comparison, keep the device, location, and Wi-Fi or Ethernet connection the same. Avoid running a large download during the first baseline test. You can run another test while a download or stream is active if you want to see what happens under load.
What the result means
The test reports lost requests or dropouts
Some test requests did not receive a response in time. That points to an interruption somewhere along the route between your device and the test service. It could be local Wi-Fi, a router, a modem, an internet provider, or a temporary issue farther away. A browser test cannot identify the exact faulty device, and its result is not a record of every packet used by another app.
If the result repeats when calls or games are failing, it is useful evidence that the connection is intermittent. Repeat the test on another device and, if possible, with Ethernet to narrow down whether the issue follows one device or the whole network.
The test shows no lost requests, but an app still lags
A short test with no reported loss is reassuring, but it does not prove that every service has a perfect connection. The interruption may be brief, may happen only at another time, or may affect the route to the app you are using rather than the test service. Run the test during the problem and check the app's own connection status too.
Peak speed is high, but stability is poor
The connection can move a lot of data when it is working and still have interruptions. A file download can often recover missing data by requesting it again, which takes extra time. A live call or game has less time to wait, so a small gap can sound like a cutout, freeze a frame, or make an action arrive late.
There is no packet loss, but speed is low
This is a different problem. The connection may be consistent but too slow for the task, especially if upload speed is low while you are sending video or sharing files. Check the speed result at different times and compare it with the speed included in your internet plan.
How to reduce packet loss
- Pause heavy network activity. Stop large downloads, cloud backups, game updates, or video streams on your own devices, then repeat the stability test. If loss stops, the connection may be struggling when several devices compete for capacity.
- Compare Wi-Fi with Ethernet. If you can, connect the computer directly to the router with an Ethernet cable and repeat the test. On Windows 11, check the connection under Settings › Network & internet › Ethernet or Settings › Network & internet › Wi-Fi. On a Mac, open System Settings › Network and select the active connection. If Ethernet is stable while Wi-Fi is not, focus on wireless coverage, interference, or the router's Wi-Fi settings.
- Improve the Wi-Fi path. Move closer to the router and test again. Keep the router in an open, central spot rather than inside a cabinet or behind large objects. If a nearby room works better, distance or walls may be weakening the connection.
- Restart the network equipment. Restart the router and modem using their normal power controls, wait for them to reconnect, then test again. This can clear a temporary fault, but repeated losses after restarts need more investigation.
- Compare with and without a VPN. If your work or security rules allow it, test once with the VPN connected and once without it. If the loss appears only through the VPN, the tunnel or its route may be responsible. Do not turn off a required work VPN to access protected services.
- Check cables and other devices. Reseat the Ethernet cable, try another router port, and repeat the stability test on a second device. If one device has the problem on both Wi-Fi and Ethernet, check its network adapter or system updates. If several devices fail together, the router, modem, or internet service is a more likely place to investigate.
- Contact your internet provider if the issue continues. Share the times of repeated dropouts and whether they happen on more than one device. Ask the provider to check the connection to your home, especially if Ethernet devices also lose requests.
Why a speed test can miss the problem
A peak speed result measures how much data the connection can transfer during the test. It is useful for checking capacity, but the number alone can hide short interruptions. A brief burst of high speed may occur between two moments when the connection stalls.
Packet loss and speed are also not interchangeable. A fast connection can lose some requests, while a slower connection can deliver data steadily. For calls, games, remote desktop, and other live tasks, consistent delivery often matters more than the highest download number. Look at the stability result and the speed result together, and repeat the checks when the problem actually occurs.
