Ping Test — Check Your Latency and Jitter Online
This ping test measures how long a round trip to a server takes from your browser and how much that number wobbles between samples. The first figure is your latency; the second is your jitter, and in real-time games jitter is usually what is ruining things. It samples the round trip ten times while the link is idle, then again while the download stage is saturating it, and reports the gap as loaded ping — that gap tells you more than either number alone.
What is a good ping for gaming
Under 20 ms is excellent, 20-50 ms is good, 50-100 ms is playable, and above 100 ms is rough for anything competitive. Those bands map onto frame times: at 60 fps a frame is 16.7 ms, so 20 ms is about one frame of delay and 100 ms is six.
- Under 20 ms — excellent. Close server, clean route, immediate hit registration.
- 20-50 ms — good. Typical fibre to a regional server, well inside what lag compensation hides.
- 50-100 ms — playable. You lose tight duels, but the game works.
- Over 100 ms — rough. Fine for turn-based games, painful in a shooter; over 150 ms, competitive matchmaking starts flagging you.
Distance sets the floor. Light in fibre covers roughly 200 km per millisecond, so a server 1,000 km away costs 15-20 ms before anything else counts. If your ping here is 12 ms but your game shows 90 ms, the game server is far away — a server-selection problem, not a connection problem.
Ping vs jitter vs packet loss
Jitter wrecks a game faster than a slightly higher average ping, because games absorb delay they can predict. A steady 70 ms is compensated for: the client interpolates, the server rewinds time by a fixed amount when it checks your shot, and you learn to lead targets. A line averaging 30 ms that jumps to 200 ms breaks all three at once, which is why it feels worse than the slower but steadier connection.
Aim for jitter under 10 ms, or under 5 ms for competitive play. Above about 20 ms you get rubber-banding and hits that do not register. Packet loss is the least forgiving of the three: 1% shows up as stutter, and anything sustained above 2% makes a fast game unplayable however low the average ping looks.
Why ping spikes on Wi-Fi
Wi-Fi spikes are almost always retransmissions: a frame is damaged by interference, nothing acknowledges it, and the radio sends it again. Each retry costs milliseconds, and a few in a row is a 200 ms spike out of nowhere. Ethernet does not do this, which is why the same PC shows a flat 15 ms on a cable and a jagged 15-300 ms over the air.
2.4 GHz vs 5 GHz
2.4 GHz reaches further and through more walls, but it has only three non-overlapping channels and shares the band with every neighbour, Bluetooth device and microwave nearby. 5 GHz has far more channels and fewer neighbours on each, at the cost of range. If your router advertises one merged network name, your device may be sitting on 2.4 GHz without telling you — split the bands and join the 5 GHz one deliberately.
Other local causes worth ruling out
Signal bars measure strength, not error rate, so you can have full bars and heavy retransmission. Extenders and powerline adapters add latency of their own: a cable running to an extender is still a Wi-Fi link for most of its path.
Bufferbloat: fine when idle, terrible when someone streams
If your ping is 15 ms alone and 300 ms the moment someone starts a stream or an upload, that is bufferbloat, not a slow connection. Routers and modems hold oversized queues, so when the link saturates your small, urgent game packets wait behind a large transfer instead of being dropped early. A 1 MB buffer on a 10 Mbps uplink is roughly 800 ms of added latency.
The test does this for you in the download direction: the loaded ping row is the round trip measured while the download stage of the internet speed test is saturating the line. If it climbs by hundreds of milliseconds above the idle figure, you have found your lag. The upload direction is not measured here — static hosting has no endpoint to upload to — so test that one by hand: start a large upload of your own and watch the ping while it runs. Upload is the worse direction, because home connections have far less of it.
The fix is queue management, not more bandwidth: enable SQM or fq_codel if your router has it, QoS if not, and shape to about 85-95% of your measured line rate. A faster plan with the same oversized buffer bloats just the same.
Why a VPN or ping booster usually makes it worse
A VPN adds a hop, so it normally raises your ping: traffic goes to the VPN endpoint first, is encrypted and decrypted at both ends, and only then heads for the game server. Unless that endpoint sits on the direct path, you have made the route longer. Commercial "ping boosters" are the same product with gaming artwork.
Two cases make one worth trying. ISP throttling — your ping is clean at 2 a.m. and doubles at 8 p.m. while ordinary browsing stays fast. And bad peering, where your ISP hands traffic to the game's network at a congested exchange far away. Both show up in a traceroute as a hop where latency jumps and stays up. Everything else is free and comes first: a cable instead of Wi-Fi, the closest server region, background downloads closed, the router rebooted, bufferbloat fixed.
What this ping test can and cannot measure
A browser cannot send an ICMP packet — no web page can, because JavaScript has no access to raw sockets, and ICMP echo is exactly what the ping command in a terminal sends. What this test measures instead is the round-trip time of small HTTP requests to one web server — this site's own, the only host it talks to: the request goes out over TCP, the server has to look at it and answer, and the reply comes back. Every sample is a real request; a probe that fails is reported as a failure rather than replaced by a number that looks about right.
That number is therefore higher than a terminal ping to the same host, and legitimately so: it includes TCP behaviour, the TLS handshake, the server's own handling time and browser overhead. A browser test reading 28 ms where ping reports 14 ms is not broken; the two measure different things.
So read the result as a relative number. It is reliable for comparisons made the same way minutes apart: Wi-Fi against Ethernet, 2.4 GHz against 5 GHz, idle against saturated, before a router change against after. It is not your in-game ping, which depends on the game server region and will usually be higher. For an absolute figure to a named host, use ping or pathping in a terminal.
Ping test FAQ
What is a good ping for online gaming, and how do you test it?
Under 50 ms is good for almost any online game, and under 20 ms is excellent. Between 50 and 100 ms you are still competitive in most titles; above 100 ms you will feel it in shooters and fighting games. Test it with a browser ping test for quick comparisons between your own setups, and with the in-game network display for the figure that actually decides your matches.
Why does my ping spike so often?
Something is briefly holding your packets in a queue — usually Wi-Fi retransmissions, a saturated uplink, or congestion at your ISP. Find the pattern before changing anything. If spikes only appear when someone streams or uploads, it is bufferbloat in your router. If they appear on Wi-Fi but never on a cable, it is interference. If another device on the same network stays clean, the fault is local to your PC.
Why is my ping high on Wi-Fi but fine when I plug in an Ethernet cable?
Because Wi-Fi retransmits damaged frames and Ethernet does not. Interference from neighbouring networks, Bluetooth, microwaves and USB 3.0 devices corrupts frames, the radio resends them, and every retry adds milliseconds. A cable has none of that, so latency stays flat. If you cannot run one, move to 5 GHz and get closer to the router, and avoid extenders and powerline adapters — they keep the Wi-Fi problems while looking wired.
Does jitter matter more than ping for gaming?
Usually yes. A steady 70 ms plays better than an average of 30 ms that jumps to 200 ms, because games compensate for delay they can predict and cannot compensate for delay that changes. Jitter breaks interpolation and lag compensation at once, giving you rubber-banding and shots that do not register. Target jitter under 10 ms for normal play and under 5 ms for competitive, even if that means accepting a slightly higher average.
Is it possible to lower ping by tweaking router settings?
Yes, but only the part of your ping that your own network causes — distance to the server is fixed. What works: enable SQM or QoS to stop bufferbloat, use a cable instead of Wi-Fi, split 2.4 GHz and 5 GHz so you can join the 5 GHz band, disconnect idle devices doing background uploads, and reboot the router so it picks a cleaner Wi-Fi channel. Registry "optimisers" do nothing.
Why does my ping jump to 500 ms every 30 seconds when my speeds are fine?
That is bufferbloat: your download and upload figures are healthy, but something is filling a queue and your game packets wait behind it. Cloud sync, a console update or a backup is enough. Confirm it by watching your ping while you deliberately saturate the line — if it climbs by hundreds of milliseconds and recovers when the transfer stops, enable SQM and shape to about 90% of your line rate.
Can using a VPN when gaming lower ping?
Usually not — a VPN adds a hop and encryption, so it normally raises your ping. It helps in only two diagnosable cases: your ISP throttles gaming traffic at peak hours, or it hands your traffic to the game's network at a badly congested exchange. Run a traceroute and find the hop where latency jumps. If the bad hop is not inside your ISP, a tunnel will not route around it.