Ping Test

What this test measures

The test sends small requests to a measurement server and records how long each round trip takes. The result is your latency in milliseconds — how quickly your connection responds, not how much data it can move.

Alongside ping, the test reports download and upload throughput, which lets you see whether a responsiveness problem is caused by a saturated line or exists even when the connection is idle.

How to interpret your results

Run the test twice: once while nothing else is using the connection, and once while a large upload or download runs. Compare the two numbers. A small rise under load is normal; a jump from tens of milliseconds to hundreds means your router is queueing traffic badly, which is a fixable problem called bufferbloat.

What is considered a good ping?

Distance sets a physical floor: a round trip across a continent costs tens of milliseconds, and an intercontinental trip well over 100 ms, before any equipment is involved. A high ping to a distant server is not a fault.

What affects your ping

• WiFi instead of Ethernet — wireless adds a few milliseconds and much more variance.
• Distance to the server, and how efficiently your provider routes to it.
• A saturated uplink: one background upload can inflate every round trip.
• Connection type — satellite and some fixed-wireless links have a high floor by design.
• Other devices and automatic updates competing for airtime and queue space.
• A VPN, which adds both encryption overhead and a routing detour.

Ping, jitter and packet loss

Ping is the average delay. Jitter is how much that delay varies between packets, and it is usually what makes a game feel unstable even when the average looks healthy. Packet loss means data never arrives at all, which produces stutter in games and dropped words in calls.

All three matter together. If ping looks fine but the experience does not, measure jitter and packet loss over several minutes rather than trusting a single average.

How to improve your result

• Connect over Ethernet for anything latency-sensitive.
• Enable SQM or QoS on the router and shape slightly below your measured line rate.
• Pause cloud backups, game patches and system updates while you play or call.
• Choose the closest available server region in games and conferencing apps.
• On WiFi, move to 5 GHz, change channel away from neighbouring networks, and move closer to the router.
• Disconnect the VPN unless it demonstrably improves your route.