Ping
Round-trip time for a tiny packet — the delay between your action and the server hearing it. The number online games live or die by.
Score anchors: 15 ms = 100 · 30 = 95 · 50 = 85 · 80 = 65 · 120 = 45 · 180 = 25 · 250 = 10 · 400 = 0
Gaming quality test · universalspeedtest.com
One run tells you whether your network connection is suitable for online gaming — with transparent thresholds, and without pretending it can measure your frame rate.
Network-quality indicators, not guarantees of in-game performance · ≈20 seconds · no signup, no ads
Game-specific guides
Each guide runs the same test, then explains what the numbers mean in that game — why ping spikes, how Wi-Fi and VPNs affect it, and how to troubleshoot with evidence.
Tactical FPS
Tactical FPS
Mobile battle royale
Mobile battle royale
Battle royale & sandbox
Battle royale
Mobile FPS
Online FPS
Hero battle royale
Vehicular sports
Sandbox
MOBA
MOBA
Team hero shooter
Open-world multiplayer
Gaming internet test
One run measures ping, jitter, packet loss, download and upload, latency under load and connection stability — then scores the network for online gaming. The score grades your connection only; your frame rate belongs to your hardware.
≈20 seconds · typically 50–200 MB of data · no signup, no ads
Preparing test
Gaming quality
—/100
——
—
Actual FPS depends on your device hardware.
—
These are network-quality indicators, not guarantees of actual in-game performance. Measurements run against the nearest Cloudflare edge — browsers cannot reach game servers directly, so game-server latency on this site is always general guidance, never a measured figure.
Test failed
Something went wrong while running the test.
The seven indicators
Every threshold below is published on purpose. Nothing about the score is a black box: you can see exactly how your result was reached.
Round-trip time for a tiny packet — the delay between your action and the server hearing it. The number online games live or die by.
Score anchors: 15 ms = 100 · 30 = 95 · 50 = 85 · 80 = 65 · 120 = 45 · 180 = 25 · 250 = 10 · 400 = 0
How much ping varies between consecutive samples. Connections tolerate a steady delay far better than a jumping one.
Score anchors: 5 ms = 100 · 10 = 90 · 20 = 75 · 40 = 50 · 60 = 30 · 100 = 0
The share of probes that never arrived — estimated over HTTP, because browsers get no ICMP. Even 1–2% drops hit registration and call audio.
Score anchors: 0% = 100 · 0.2 = 95 · 1 = 80 · 2 = 60 · 5 = 30 · 10 = 0
How fast the line pulls data down — what keeps updates, streams and friends’ media flowing. Shown for context: it does not enter the gaming score, because in-match traffic is tiny.
Grades for context: A ≥ 200 Mbps · B ≥ 100 · C ≥ 50 · D ≥ 25 · E ≥ 10 · F below
How fast you send data out — call video, backups, clips. Also context, not part of the score: games send very little data up.
Grades for context: A ≥ 100 Mbps · B ≥ 50 · C ≥ 25 · D ≥ 10 · E ≥ 5 · F below
Your ping while the line is saturated — bufferbloat. It is why a match stutters the exact moment someone starts a download.
Score anchors: +10 ms = 100 · +30 = 90 · +50 = 75 · +100 = 50 · +200 = 25 · +400 = 0
A derived indicator: the equal-weight average of ping spread (max − min of the probes), jitter and loss, scored on the same anchor tables as the score.
Labels: ≥ 90 Steady · ≥ 70 Mostly steady · ≥ 50 Variable · below 50 Unstable
Methodology
Four inputs, each scored 0–100 against the anchor tables, then combined:
If under-load latency could not be measured, its weight is redistributed across the other three so the score stays comparable.
Inputs are linearly interpolated between these points (the same tables the metrics section shows):
Ping: 15 ms → 100 · 30 → 95 · 50 → 85 · 80 → 65 · 120 → 45 · 180 → 25 · 250 → 10 · 400 → 0
Jitter: 5 ms → 100 · 10 → 90 · 20 → 75 · 40 → 50 · 60 → 30 · 100 → 0
Packet loss: 0% → 100 · 0.2 → 95 · 1 → 80 · 2 → 60 · 5 → 30 · 10 → 0
Under load (delta): +10 ms → 100 · +30 → 90 · +50 → 75 · +100 → 50 · +200 → 25 · +400 → 0
Stability ping spread: 10 ms → 100 · 30 → 90 · 60 → 75 · 120 → 45 · 250 → 15 · 400 → 0 (averaged with jitter and loss sub-scores)
Online games send and receive very little data — a stable 10 Mbps line handles match traffic easily. What decides fights is consistency: latency, jitter, loss and how the line behaves under load. So the score grades those, and shows speeds as context.
What the verdict means
When your score lands in the Good or Excellent band, that is the verdict this test gives: your network is fast, stable and consistent enough that it will not be the reason you lose a fight. It grades the connection — nothing else.
Frame rate is rendering, and rendering is decided entirely by the machine in front of you. No internet plan, router or ping improves it — and no amount of GPU power fixes a 150 ms connection. Two dials, two fixes:
Stuttering frames → lower settings, check thermals, update drivers. Rubber-banding and late hits → that is this test’s side of the story.
Every number here is a network-quality indicator, not a guarantee of in-game performance. Real matches add server load, routing changes, Wi-Fi variance and the game’s own netcode. Test where you play, at the hour you actually play, and treat the score as strong evidence rather than a promise.
And remember what we never claim: internet speed does not determine FPS. If someone tells you a faster plan will raise your frames, they are confusing two independent systems.
FAQ
Seven indicators: ping (idle latency), jitter, packet loss, download speed, upload speed, latency under load (bufferbloat) and connection stability (derived from ping spread, jitter and loss). The first four latency-side inputs feed the gaming quality score with published weights and thresholds; download and upload are shown for context because in-match game traffic is tiny. Measurements run against the nearest Cloudflare edge in your browser.
As general guidance (not measured game-server latency): under 50 ms feels responsive for most games, under 30 ms is ideal for competitive titles, and above 120 ms starts to work against you. Jitter under 15 ms and 0% packet loss matter as much as the average — a steady 60 ms beats a line flipping between 20 and 90. Each game page on this site publishes game-specific guidance.
No. FPS depends on your device hardware: CPU, GPU, RAM, resolution, graphics settings, drivers and thermal conditions. Internet quality affects ping, jitter and packet loss — a different axis entirely. A faster plan will not lift a struggling PC from 60 to 144 fps, and a top-tier gaming rig cannot fix a 150 ms ping. When frames stutter, look at your hardware; when the game rubber-bands, look at this test.
It is your ping while the connection is busy. Routers with oversized buffers queue packets instead of dropping them, so when a download fills the pipe, your game’s packets wait behind it — ping balloons by hundreds of milliseconds. The test fires latency probes during the download phase and reports the jump. Fixes live at the router: SQM/fq_codel if available, or QoS rate caps slightly below line speed.
No — and we say so plainly. Browsers cannot send ICMP or reach game servers directly, so this test measures your line to the nearest Cloudflare edge. That is an excellent proxy for your network’s quality, but it is not your ping to Riot, Valve or Krafton. Any game-server figures on this site are labelled as general guidance, never as measured game-server latency.
Three equally-weighted sub-scores are averaged: ping spread (the max − min of the twenty idle probes), jitter, and packet loss — each scored on the same published anchor tables as the gaming score. The result is labelled Steady (≥ 90), Mostly steady (≥ 70), Variable (≥ 50) or Unstable (below 50). It is a derived indicator of consistency, shown alongside the raw numbers so you can check the maths yourself.