Tactical FPS · universalspeedtest.com
Test your connection for Counter-Strike 2 in about 20 seconds: ping, jitter, packet loss, download and upload, latency under load and a gaming-quality score. CS2 is angles, utility timing and trades measured in milliseconds — this is what your line contributes to the server’s view of them.
Network-quality indicators, not guarantees of in-game performance · ≈20 seconds · no signup, no ads
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.
What we measure
Ping is the round trip to the server and back. CS2’s sub-tick netcode records exactly when actions happen, but your inputs still have to reach the server for them to count — a 90 ms round trip means everything you do arrives late relative to what you saw. General guidance: under 40 ms feels responsive, under 20 ms is ideal for AWP duels and trades. These are guidance figures, not measurements of Valve’s servers.
Jitter is ping varying from sample to sample. In CS2 it shows up as inconsistency: sprays that feel different round to round, a peek that worked twice then failed, utility that lands a beat later than you planned. A steady 50 ms beats a connection flipping between 20 and 80. Keep jitter under 10 ms (general guidance).
Packet loss is data that never arrives and has to be retransmitted. Brief bursts mid-fight present as shots that “did not register”, stutter steps, or a position rubber-band — the classic clip of dying behind cover. CS2 absorbs tiny, rare losses; visible or repeated loss during matches means the path needs fixing. Target: 0%.
Valve’s matchmaking assigns a server for each match; Indian players typically land on the nearest Valve region (commonly Mumbai or nearby) — the ping on the match scoreboard is the true number for that server. We do not measure Valve’s servers; every figure on this page is general guidance, not measured game-server latency.
Troubleshooting signals
01
Valve’s matchmaking picks the server per match, so ping can jump between games without anything changing at home. The scoreboard ping during a match is ground truth for that server; this test gives you the baseline for your line. If scoreboard numbers sit far above your test numbers consistently, you are being placed away from the nearest server.
02
CS2 itself, or any other title in your library with auto-update on, can start a multi-gigabyte download mid-session. That fills your router’s queue and your ping rides up with it — visible in this test’s “under load” row even when idle ping looks perfect.
03
Apartment blocks put dozens of wireless networks on the same channels. Your average ping may stay low while retries and channel-switching add jitter in bursts — enough to lose a trade you had every right to win.
04
Shared access networks get busy in the evening when everyone streams and downloads at once. Compare a morning test with a 9 PM test from the same spot: a consistent evening collapse is congestion on the line, not your PC.
CS2 traffic is light but timing-critical, and Wi-Fi adds exactly the wrong kind of variation — brief contention spikes rather than a slow-but-steady link. Ethernet is the clean answer. If you must stay wireless, use 5 GHz close to the router, avoid crowded channels, and watch this test’s jitter and “under load” rows before and after any change: those two numbers, not average ping, tell you whether the wireless link is match-ready.
Actionable steps
Step 1
Run this test on the connection you play on — note ping, jitter and under-load latency — then repeat it on an alternative connection (mobile data as a control, or next to the router). You are isolating your line from your Wi-Fi before changing settings.
Step 2
Set Steam to update outside your playing hours and disable background downloads during sessions. If others share the line, enable QoS or SQM on the router so a download cannot monopolise the queue.
Step 3
Ethernet removes the variable entirely. On Wi-Fi: 5 GHz only, router in the open and elevated, away from fridges, microwaves and Bluetooth speakers. Retest after each change and keep what moves jitter down.
Step 4
Next match, note the server ping on the scoreboard and compare it with this test’s idle ping. Big gap → the server you were assigned is far; small gap but both high → the route from your ISP is the problem.
Step 5
A wired idle ping above 80 ms with nothing running, or under-load latency climbing past +100 ms, is ISP-level evidence. Send support your test results, the time of day and the scoreboard ping — specific numbers move tickets faster than complaints.
A VPN wraps your traffic in a detour through someone else’s server, which usually adds latency rather than removing it. It can occasionally help if your ISP’s routing to Valve’s network is poor — the only honest test is A/B: run this test without the VPN, then with it, and keep whichever gives the lower, steadier numbers. Also check the rules of any service you play on before connecting through one.
Frame rate vs connection
FPS and ping are independent. FPS comes from your CPU, GPU, RAM, resolution, graphics settings, drivers and thermals — CS2 players often run low settings for clarity and frame rate, and that changes rendering, not networking. Ping is the network round trip, measured here. A better connection will never turn 60 fps into 144, and a high-refresh monitor cannot fix a 120 ms ping. Fix each on its own side of the machine.
Everything on this page 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 play.
We do not measure Counter-Strike 2 servers directly — every figure on this page is general guidance, not measured game-server latency.
FAQ
General guidance, not measured game-server latency: under 40 ms feels responsive, under 20 ms is ideal for holds and trades, and above 100 ms the advantage clearly sits with better-connected players. Consistency counts too — jitter under 10 ms and zero packet loss keep sprays and utility timing predictable.
Four common causes: Steam started a download, you were assigned a farther server this match, Wi-Fi interference is adding spikes, or the line is congested at peak hours. Compare this test’s idle result against a match scoreboard ping, and run the test again while a download is running — the “under load” row will expose queueing instantly.
Only for updates. In-match, CS2 exchanges tiny amounts of data — a 10 Mbps connection handles it easily. What matters in-match is ping, jitter and packet loss, which this test measures. Your frame rate, meanwhile, is set by your hardware and settings — no bandwidth raises FPS.
Ethernet: fewer variables, lower jitter, no contention with other devices. On Wi-Fi, use 5 GHz near the router and verify with this test — compare jitter and the “under load” row, not just average ping, because wireless problems show up as spikes rather than averages.
Usually it raises it — a VPN is a detour through extra infrastructure. It helps only when your ISP’s natural route to the match server is unusually bad. Measure both ways with this test and keep the better result; check service rules before playing through a VPN.