How to compare public Wi-Fi and wired stability

Public Wi-Fi may connect successfully but still pause during calls, uploads or remote work. A wired office connection can feel more reliable, but checking both on the same computer helps you tell whether the problem is the Wi-Fi, the internet connection or something else.

Use the Connection Stability test to watch response time, jitter, lost requests and dropouts over a few minutes. Compare the connections under similar conditions, changing one thing at a time.

Compare public Wi-Fi and the wired connection

1. Open the Connection Stability test while connected to public Wi-Fi. If the network has a sign-in page, complete that first.
2. Run the test for its full duration. Note the response time, jitter, lost requests and any dropouts, along with where you are sitting and whether a VPN is connected.
3. Connect the same computer to the office network with an Ethernet cable. Make sure it is using the wired connection, not still using Wi-Fi, then run the test again.
4. For a useful comparison, keep the browser, VPN state and other network activity as similar as possible. If the results vary, repeat each test once more.

A VPN changes the route your traffic takes. Keep it in the same state for both tests if you need a fair comparison. If workplace rules allow a separate test without it, you can compare that too, but do not bypass your office security policy.

What the result means

Both connections show steady results

Low, consistent response time with little jitter and no lost requests suggests the connection stayed responsive during the test. If a particular app still pauses, check that app, its server or the device rather than assuming the network is unstable.

Public Wi-Fi has more jitter or dropouts

Jitter means response time varies from one request to the next. A busy access point, weak coverage, interference or other users sharing the network can make public Wi-Fi less consistent. Try again closer to the access point, if you can, and compare the results.

The wired connection also loses requests

The cable removes the Wi-Fi link from the path, but the office network still depends on its router, internet service and any VPN. If both tests show interruptions at a similar time, the cause may be farther upstream or shared by both connections. The test alone cannot identify which router or service is responsible.

Response time is steady, but downloads still feel slow

Stability and speed are different. A connection can respond consistently but transfer large files slowly. This test is focused on response behavior, not download capacity. Also, a browser cannot read Wi-Fi signal strength in dBm, so it cannot show a precise radio signal level. For more on separating Wi-Fi from internet issues, see Is your Wi-Fi weak, or is it the internet?

How to improve the connection

1. Pause other network activity. Stop large downloads, cloud backups and video streams on your computer before testing. Shared public Wi-Fi and office networks can also be busy because of other users, so a second run at a quieter time may help explain changing results.
2. Finish the public Wi-Fi sign-in. Open a new browser tab and check for a network sign-in or terms page. Some public networks allow a device to connect to Wi-Fi before granting full internet access.
3. Try a different spot on Wi-Fi. Move closer to the access point and avoid placing the computer behind thick walls or metal furniture. Compare results from each spot rather than relying only on the Wi-Fi icon or number of bars.
4. Check which network is active. On Windows 11, open Settings › Network & internet and select Wi-Fi or Ethernet to check the connection. On macOS, open System Settings › Network and select the active service. Confirm that the wired test is actually using Ethernet.
5. Reconnect the cable. Unplug and firmly reconnect both ends of the Ethernet cable. If possible, try another cable or office network port. If you use a USB Ethernet adapter, reconnect it directly to the computer rather than through a hub.
6. Ask the network administrator about repeated wired drops. Share the test times and whether the issue also happened on Wi-Fi. An administrator can check the office switch, access point or internet service; changing network equipment yourself may violate workplace rules.

Make the comparison meaningful

Run the tests close together in time, but let one finish before starting the other. Keep the computer in the same place and use the same browser. A busy network can change from minute to minute, so a single run is a snapshot, not a guarantee about the whole workday.

Public Wi-Fi and office Ethernet may also use different routes to the test server. A difference in response time does not by itself prove that one connection is faulty. Look for repeatable patterns, especially lost requests and sudden interruptions, then report those alongside the time and connection type.