How to test ping on a Wi-Fi extender with no load

Your Wi-Fi extender shows a strong connection, but web pages still pause or calls feel delayed. To check whether response time is steady when nobody is using the network, measure ping while the connection is otherwise idle.

Use TooLab's Wi-Fi Signal to watch response time, jitter, and lost requests over several minutes. This measures how the connection behaves, not the extender's radio signal strength. A browser cannot read Wi-Fi signal strength in dBm, and a ping to an online server includes your internet connection as well as the local Wi-Fi link.

Measure ping while the network is idle

1. Connect your computer or phone to the extender's Wi-Fi. Open Wi-Fi Signal in the browser on that device. If you are not sure the device is connected to the extender rather than the main router, check the extender or router's connected-device list.
2. Pause downloads, cloud backups, video streams, game updates, and other heavy network use. Ask other people to avoid large transfers during the test. Normal background activity can still happen, so aim for a quiet period rather than assuming the network is perfectly silent.
3. Leave Wi-Fi Signal running for several minutes. Watch the response time, jitter, and lost-request readings. Note the time and the room where you tested, especially if you want to compare results later.
4. Repeat the check once or twice in the same place. For a useful comparison, connect to the main router instead, if you can, and repeat under similar conditions. Confirm which access point the device is using, since some extenders reuse the router's Wi-Fi name.

Do not run a download or speed test during an idle-ping measurement. Those activities add traffic and can raise latency. To check throughput and see ping and jitter during a separate test, use the Speed Test after the idle check is finished.

What the result means

Response time stays low and steady

A stable reading with few or no lost requests is a good sign for basic connection consistency at that moment. It does not prove every app will respond instantly, because the server, internet route, and the app itself also affect delay.

Response time jumps or jitter is high

Jitter means the delay changes from one request to the next. Spikes can point to interference, weak communication between the extender and router, or traffic elsewhere on the network. Run the test again at a quieter time before deciding the extender is at fault.

Requests are lost

Repeated lost requests suggest the connection is dropping packets, meaning some data does not reach its destination. A few isolated misses are not enough to identify the cause. Compare another test and note whether the problem happens only through the extender or also near the router.

The extender and router readings are similar

The extender may not be the main cause of the delay. The route to the test server, the internet service, or other network activity can affect both readings. A browser test cannot isolate the extender's internal wireless link from every other part of the connection.

The extender reading is consistently worse

The extender's location, its link back to the router, or local interference may be adding delay or instability. This comparison is most useful when you use the same device, same room, and similar conditions, and confirm the access point for each run.

How to improve the connection

1. Confirm which Wi-Fi point you are using. Some extenders share the router's network name, so your device may switch between them without making it obvious. Check the extender's app or administration page for its connected-device list. If the router and extender show separate network names, connect to the intended one directly.
2. Pause other network activity. Stop cloud sync, downloads, streaming, and updates on nearby devices, then rerun the idle check. If the delay settles, congestion may be contributing. Don't treat this as proof that the extender is defective.
3. Move closer to the extender. Test in the same room, then a little farther away. If response becomes steadier nearby, the device may be struggling with the extender's signal at its usual location. On Windows 11, check the connected network at Settings › Network & internet › Wi-Fi. On macOS, open System Settings › Wi-Fi. On iPhone, open Settings › Wi-Fi; on Android, look under Settings › Network & internet › Internet (the wording varies by device).
4. Try a better extender location. Place it between the router and the area with poor coverage, where it can still receive a reliable connection from the router. A spot at the very edge of the router's coverage may simply repeat a weak link. Keep it away from large metal objects and avoid enclosing it in a cabinet.
5. Restart the extender and router. If repeated checks show trouble, restart both devices according to their instructions. Wait for Wi-Fi to return, reconnect the test device, and repeat the measurement before changing more settings.
6. Update or reset only after simpler checks. Check the manufacturer's instructions for a firmware update. If the extender remains unstable, use its setup guide to reset and configure it again. Keep the router's network password handy, and avoid resetting equipment managed by a landlord or workplace without permission.

Why a ping to the internet is not a local-only test

A browser-based ping measurement sends requests to a remote server and measures the round trip. It includes Wi-Fi, the extender's connection to the router, the router, your internet service, and the route to that server. A higher number does not automatically mean the extender itself is slow. The test also cannot show the extender's radio channel, exact signal level, or which internal link caused a delay.

For a fair comparison, use the same test device and location, test during a quiet period, and make sure you know whether the device is connected through the extender or directly to the router. A difference that repeats across several checks is more useful than one unusually high reading.

Wi-Fi Signal tests connection behavior from your device, so run it on the device and network you want to check.