Online FPS · universalspeedtest.com
Test your connection for Call of Duty in about 20 seconds: ping, jitter, packet loss, download and upload, latency under load and a gaming-quality score. Whether you play classic multiplayer or the big battle-royale modes, these are the numbers the server judges your fights by.
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. CoD’s gunfights resolve server-side in fractions of a second — slide-cancel peeks, trades around a corner, a sniper shot on a moving target — so your ping is baked into every duel. General guidance: under 50 ms feels responsive, under 30 ms is ideal. These are guidance figures, not measurements of the game’s servers; the latency shown during a match is ground truth for that match.
Jitter is ping varying between samples. It shows up as fights that feel different round to round: hitmarkers that land late, movement that stutters under pressure, cover that fails when it mattered most. Consistency beats a marginally lower average. Keep jitter under 15 ms (general guidance) so the game’s fast movement stays readable.
Packet loss is traffic that never arrives and must be retransmitted. Bursts mid-fight appear as shots that vanished, audio skipping, or a rubber-band that moves you into someone’s crosshair. Small, rare losses are absorbed; repeatable ones during matches mean the path needs fixing. Target: 0%.
Call of Duty uses region-based matchmaking, and the latency shown during a match is the true figure for that lobby. Indian players commonly connect via nearby Asian or Middle East options — check the network settings in your game for live choices. We do not measure the game’s servers; every figure on this page is general guidance, not measured game-server latency.
Troubleshooting signals
01
CoD’s patches and mode downloads run to tens of gigabytes, and launchers start them unprompted. A saturated link inflates your router’s queue — this test’s “under load” row measures exactly that. Pause updates before playing, or enable QoS on the router so game packets stay first in line.
02
Crossplay and region-based pools can place you outside your usual area, especially in off-peak queues. Compare this test’s idle baseline with the in-match latency: if the match sits far above your baseline, the lobby moved — not your line.
03
Wireless shares airtime with neighbours and every device in the flat; brief interference adds spikes that strike mid-fight while the bars still read full. A wired connection removes the whole category — otherwise, clean up band and placement, then verify with this test.
04
Shared networks saturate in the evening. Run this test at midday and at 9 PM from the same spot for a few days: consistent evening degradation is congestion, not configuration — move downloads off-peak and keep the connection that measures best at your real hours.
CoD’s movement-heavy play punishes wireless variance more than most shooters: average ping can look fine while brief spikes steal the fight that counted. Ethernet is the clean fix. Without it, play on 5 GHz close to the router with a clear line of sight, keep Bluetooth and microwaves away from it, and measure before/after changes using this test’s jitter and “under load” rows — those two numbers, not the headline, tell you if the link is match-ready.
Actionable steps
Step 1
Run this test on the connection you use — and on a control (mobile data, or next to the router). Note ping, jitter and under-load latency. You are separating the line itself from the way you reach it before touching a setting.
Step 2
Disable auto-update during play, and use the launcher’s schedule for off-hours. If others share the line, enable QoS/SQM so their traffic cannot fill your queue — then retest the “under load” row to prove the change.
Step 3
Ethernet is durable. On Wi-Fi: 5 GHz only, router elevated and in the open, away from fridges, microwaves and Bluetooth speakers, played from where signal is strong. Retest from your seat after each change.
Step 4
Note the in-match latency next time you play and compare it with this test’s idle ping. Small gap → your line is the limit; large gap → you are being placed far away or the route changed. Each points to a different fix.
Step 5
Wired idle ping above 80 ms, idle jitter above 30 ms, or repeatable loss are ISP-level evidence. Attach this test’s results, time of day and match latency to the ticket — specifics get engineering replies instead of scripted ones.
A VPN adds a detour, so the default outcome in CoD is higher ping and more jitter — the opposite of what a shooter needs. It can win when your ISP’s natural route to your usual server pool is unusually poor, but that must be measured, not assumed: run this test with and without the VPN and keep whichever is lower and steadier. Check the game’s terms and any competitive rules before playing through one.
Frame rate vs connection
FPS and ping live on opposite sides of your setup. FPS — especially in the large battle-royale modes — is set by your CPU, GPU, RAM, resolution, graphics settings, drivers and thermals; lowering settings raises frames on your hardware and changes nothing about the network. Ping is the round trip measured on this page. More bandwidth will not lift a machine struggling to render the map, and a top-tier PC cannot repair a 120 ms connection. Diagnose them separately.
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 Call of Duty servers directly — every figure on this page is general guidance, not measured game-server latency.
FAQ
General guidance — not measured server latency: under 50 ms feels responsive, under 30 ms is ideal for peek fights and trades, and above 100 ms fast movement resolves against you. Jitter under 15 ms and 0% loss keep hit feedback honest. Compare your result with the in-match latency readout for ground truth.
Check in order: an update or download running in the background, a farther-than-usual lobby (compare in-match latency to this test’s baseline), Wi-Fi interference, or evening congestion. Pause downloads and retest — if the “under load” row collapses back to idle levels, the download was the cause.
In-match, barely — the game exchanges small amounts of data, and even modest lines carry it. Download speed matters for patches and mode downloads. What decides fights is ping, jitter and loss (measured here), while FPS comes from your hardware and settings — no bandwidth raises your frame rate.
Ethernet: it eliminates interference and contention, which is where wireless spikes come from. If you must use Wi-Fi, play on 5 GHz near the router and verify with this test — compare jitter and the “under load” row before and after any change, not just average ping.
Usually the opposite — extra hops typically add latency and jitter. It helps only if your ISP’s route to your server pool is unusually bad, which you can test: run this game-side comparison with and without using this tool and keep the steadier result. Confirm the game’s terms allow VPN use first.