What lost browser requests do and do not prove

A browser connection test reports lost requests, but that does not automatically mean your Wi-Fi is broken or that every app is dropping data. It means the test did not get a usable response for one or more checks.

Use the Connection Stability test to see whether losses repeat, whether response time changes, and whether the problem appears under the same conditions each time. The pattern is useful evidence, but it cannot name the faulty device or network hop by itself.

Check for lost requests

1. Open Connection Stability and let the test run for a few minutes. A longer run gives intermittent interruptions more time to appear.
2. While it runs, use the connection normally, but avoid starting a large download or video stream for your first check. This gives you a baseline without heavy traffic you added yourself.
3. Note the number and timing of lost requests along with response time and jitter. Jitter is the amount response time varies from one check to the next.
4. Run the test again after changing one condition, such as moving closer to the router, switching to Ethernet, or pausing a VPN. Change only one thing at a time so you can compare results.

A single run is a snapshot of one browser connection to the test service. If the problem comes and goes, repeat the check at the time it usually happens.

What the result means

No lost requests during the test

The browser received responses for the checks during that run. This is a good sign for that connection at that time, but it does not prove every website, game, or calling app will work perfectly. A specific service could be having trouble, or the problem may happen only at a different time or under load.

One or two requests are lost

A small number of losses shows that some checks did not get a usable response in time. It does not prove that your router, Wi-Fi, or internet provider caused them. A brief interruption, a busy connection, a problem along the route, or an issue with the test endpoint could all produce a similar observation.

Losses repeat or arrive in clusters

Repeated losses are stronger evidence that the connection between your browser and the test service is unreliable during the measurement. If they line up with a call freezing or a page pausing, that makes a connection problem more plausible. The test still cannot tell you where along the route the failure occurred.

There are no losses, but another app still disconnects

The test checks its own browser requests, not the internal connection of every app. The affected app may use a different server, protocol, or route. Check that app's service status and settings, and repeat the connection test while the app is having trouble.

Response time or jitter rises without lost requests

The connection is still getting responses, but they may be arriving slowly or inconsistently. This can cause delays in calls and games even when the test reports no losses. High response time is delay; jitter is variation in that delay. Neither number identifies the cause on its own.

How to investigate repeated losses

1. Repeat the test before changing anything. Run it again from the same place and on the same connection. If the losses do not return, you may have caught a brief interruption rather than a persistent fault.
2. Pause competing network activity. Stop large downloads, cloud backups, and high-resolution streams, then test again. If losses or delays improve, heavy traffic may be contributing. This comparison does not tell you which device or service created the traffic.
3. Compare Wi-Fi with a wired connection. If your computer has Ethernet, connect it to the router and repeat the test. If wired testing is clear while Wi-Fi testing repeatedly loses requests, focus on the wireless link. If both show losses, the cause may be elsewhere, including the router, modem, internet connection, or route to the test service.
4. Check your active network and location. On Windows 11, open Settings › Network & internet and check whether you are connected by Wi-Fi or Ethernet. On macOS, open System Settings › Network. On iPhone, open Settings › Wi-Fi. On many Android phones, open Settings › Network & internet › Internet; the wording varies by manufacturer. If you are on Wi-Fi, compare a test near the router with one from the room where the issue occurs.
5. Temporarily check VPNs and browser extensions. If you use a VPN, repeat the test with it off, then turn it back on and compare. You can also try a private browser window if it disables your extensions. Change one setting at a time, and restore protections after testing.
6. Restart the router if several devices are affected. Restart it using its normal power procedure, wait for the connection to return, then repeat the test. If losses continue across wired and wireless connections, contact your internet provider with the times and results. Those details help describe the symptom, but they do not prove the provider is at fault.

What a browser test cannot prove

A lost browser request is not the same thing as a direct measurement of every network packet. The test observes whether its own check receives a usable response. It does not inspect each link between your device and the server, identify where a request stopped, or show whether a router dropped a packet locally.

It also cannot establish that your Wi-Fi signal is weak. A request can be lost for reasons beyond the wireless connection, and a weak wireless link can cause slow or inconsistent responses without making every request disappear. Compare Wi-Fi with Ethernet, or test in more than one room, before deciding which part to investigate.

Use lost requests as a clue about the connection to the test service, then compare repeat runs and connection types before replacing hardware or changing network settings.