Ping Test: What a Good Ping Is and 6 Fixes That Actually Lower Latency
Ping test decoded: good latency by use case (esports to cloud gaming), ping vs jitter vs bufferbloat, why your ping spikes, and the fixes ranked by real impact.
Quick answer: A ping test measures response time in milliseconds — and it is the number gamers, traders and call-heavy workers should optimize first. Under 20 ms feels instant; 50-100 ms is playable; over 150 ms and competitive gaming is effectively over. The good news: ping responds to fixes far cheaper than plan upgrades.
Ping vs latency vs lag: the vocabulary that ends confusion
Latency is the umbrella term for delay. Ping is the measurement of round-trip time (RTT) — named after sonar. Lag is what you feel when latency spikes or frames stutter. Related: jitter is the variation between pings (covered in the jitter guide) and bufferbloat is latency that appears only under load (its own guide). A complete test reports all four — which is why Toolfyra Internet Speed Test shows ping, jitter and a grade instead of a single number.
What is a good ping? (by use case, with numbers)
| Use case | Excellent | Playable | Frustrating |
|---|---|---|---|
| Esports / FPS (Valorant, CS2) | under 15 ms | 30-60 ms | 100+ ms |
| Battle royale, MMO | under 30 ms | 50-100 ms | 150+ ms |
| Turn-based, strategy, card games | under 80 ms | 80-150 ms | 300+ ms |
| Video calls | under 40 ms | 40-150 ms | 250+ ms (with jitter) |
| Cloud gaming (GeForce Now, xCloud) | under 25 ms | 25-60 ms | 80+ ms |
| General browsing feel | under 30 ms | 30-80 ms | 150+ ms |
Physics sets the floor: light in fiber covers about 200 km per millisecond round trip. Gaming a server 1,000 km away means roughly 10 ms of unavoidable path delay plus routing overhead — which is why "get a server closer" beats every settings tweak.
How to test ping properly
- Run Toolfyra Internet Speed Test — the ping phase sends multiple small probes and reports both the best and the wobble (jitter).
- Test idle, then under load: start a download and watch latency. If idle 12 ms becomes 200 ms under load, you have bufferbloat, not distance.
- Test to the destination that matters. The tool measures to a nearby edge; your game server adds its own path. In-game network stats are ground truth for that server.
- Compare ethernet vs Wi-Fi. A 5-15 ms penalty and periodic spikes are typical for a marginal radio link.
Why your ping is high — ranked by how often it is the cause
- Wi-Fi radio — retries and power-save add 3-30 ms and spikes. Ethernet is the single cheapest upgrade.
- Bufferbloat — idle ping fine, spikes under load; fix with SQM/QoS, see bufferbloat guide.
- Routing distance — your ISP’s path to the game server is long or detoured; a VPN with a better route occasionally helps (yes, really).
- Congestion — evening spikes that vanish at 8 am; document three timed runs, then complain to the ISP with evidence.
- Old modem/router — processor saturation adds latency under any load.
- satellite exceptions — GEO satellite (Starlink-class LEO is different) has ~600 ms physics; no settings change that.
The fixes that actually lower ping
- Wire the gaming device. One cable removes the largest single source of latency variance.
- Enable SQM/fq_codel if your router has it — it trades a little throughput for a flat latency curve.
- Pin the device to 5 GHz and park it in the same room as the router if cabling is impossible.
- Choose game servers by measured ping, not by region label — in-game server browsers exist for a reason.
- Pause background sync/updates during sessions; a saturating download destroys ping instantly.
FAQ
Is 5 ms ping possible? Yes — to nearby servers on fiber, in big cities. To a server 2,000 km away, physics forbids it.
Does a faster plan lower ping? Rarely. Upgrades help when the current link saturates (bufferbloat). Distance and routing dominate otherwise.
Why is ping to fast.com’s test lower than my game server? Different destination, different path. Always trust per-server in-game stats for that game.