How to test ping under no load for a remote exam

A remote exam can lag even when a quick speed test looks fine. To get a useful baseline, check ping while your connection is not busy with downloads, video streams, cloud backups, or other devices using the network.

The Connection Stability test measures response time, jitter, lost requests, and dropouts over a few minutes. This gives you a better view of an idle connection than a download speed result alone.

Measure ping with no other traffic

1. Close streaming video, large downloads, cloud backups, and extra video calls. Ask other people on the same network to pause heavy internet use for a few minutes.
2. Open Connection Stability. Keep the same Wi-Fi or wired connection you plan to use for the exam.
3. Run the test for a few minutes without starting other network activity. Note the usual response time, whether jitter is low or high, and whether requests are lost or the connection drops.
4. Repeat the test once or twice at the time of day you expect to take the exam. If you use Wi-Fi, repeat near the router or with Ethernet if available, then compare the results.
5. Use Speed Test as a separate check for download speed, upload speed, ping, and jitter. It exchanges test data with a server, so run it after your quiet baseline rather than during the stability test.

Keep a short note of the time, connection type, and results. Comparing tests taken under similar conditions is more useful than comparing a quiet morning reading with one taken while everyone is streaming.

What the result means

Response time is low and steady

Requests are reaching the test server promptly and consistently. That is a good sign for a remote exam, but it does not guarantee the exam site will respond just as quickly. Your exam provider may use a different server or route. Check its published system and connection requirements before exam day.

Response time is usually low but jumps occasionally

Short spikes mean some requests take longer than others. Jitter is the variation in response time. A few spikes during an idle check may not disrupt anything, but frequent or large jumps can make a live session feel delayed. Repeat the test to see whether the pattern returns.

Jitter stays high or requests are lost

The connection is varying or failing to deliver some test requests. That can interrupt a login, save, or live proctoring session. Check for background traffic and test again. A stability result is not a direct test of the exam provider, but repeated loss or dropouts are worth addressing before you start.

Idle results look good, but the exam still has problems

The issue may appear only when the connection is busy, or it may be limited to the exam service, browser, or computer. A quiet test cannot rule out congestion that starts when another device uploads or downloads. For more preparation steps, see Connection planning for a remote exam.

How to improve a poor result

1. Pause traffic on your connection. Stop downloads, cloud syncing, game updates, and video streams, then wait about a minute before testing again. On a shared network, other devices can affect your result even when your exam computer is idle.
2. Move closer to the router. If you use Wi-Fi, test in the room where you will take the exam. On Windows 11, check Settings › Network & internet › Wi-Fi. On macOS, open System Settings › Network › Wi-Fi. A wired Ethernet connection can help you check whether Wi-Fi is the source of the variation.
3. Restart the router if the problem continues. Save the test results first, then restart the router and wait until its internet connection is back before running the test again. If other devices also have dropouts, the issue may be with the router or internet service rather than the exam computer.
4. Check for a VPN or proxy. A VPN can change the route your traffic takes and add delay. If your exam rules allow it, compare results with and without the VPN. On Windows 11, review Settings › Network & internet › VPN. On macOS, check System Settings › VPN, if shown, or System Settings › Network for the VPN connection.
5. Contact your internet provider if drops persist. Share the times of the tests, whether you used Wi-Fi or Ethernet, and whether other devices were affected. Ask whether there are known service problems or line issues at your address.

Why an idle ping is only a baseline

Ping is the time it takes a small request to reach a server and for a reply to return. It is usually shown in milliseconds. Lower is generally quicker, while consistent readings are often more useful than one exceptionally low result.

There is no single ping number that guarantees every remote exam will work. Requirements vary by exam platform, and the test here measures the route to TooLab's server, not to your exam provider. A speed test also creates network traffic while measuring speed, which is why it helps to run it separately from the quieter stability check.

Connection tests send measurement requests to TooLab's servers. Avoid running a speed test during the exam itself, since its data transfer can use part of your connection.