Hero battle royale · universalspeedtest.com
Test your connection for Apex Legends in about 20 seconds: ping, jitter, packet loss, download and upload, latency under load and a gaming-quality score. Apex moves faster than most shooters — movement tech, shield swaps and third-party timing all ride the same network numbers.
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. Apex’s speed amplifies it: a slide-jump peek, a zip-line entry, a shield swap under fire — each is resolved server-side, so high ping means the enemy sees you a beat before you see them. General guidance: under 50 ms feels responsive, under 30 ms is ideal. These are guidance figures, not measurements of Respawn’s servers; Apex’s own data-center list is the live reference for availability.
Jitter is ping varying between samples. In a game built on continuous movement, a link that swings between 30 and 90 ms never lets you trust a fight: looting stutters, doors desync, shots that should connect arrive between the server’s frames of truth. Keep jitter under 15 ms (general guidance) so movement and gunplay stay readable.
Packet loss is traffic that never arrives and must be retransmitted. Bursts show up as a magazine that vanished into nothing, a rubber-band mid-fight, or loot that refuses to pick up during a third-party collapse. Small rare losses happen everywhere; repeatable loss in matches means the path needs work. Target: 0%.
Apex shows its available data centers from the main menu — open the live list to choose deliberately; Indian players commonly see Singapore and other nearby options. We do not measure Respawn’s servers; every figure on this page is general guidance, not measured game-server latency.
Troubleshooting signals
01
Steam or the EA app starting a download mid-session fills your router’s queue — your ping rides up with it. Watch this test’s “under load” row: idle clean and loaded terrible is the signature of queueing, not of a broken line. Pause updates or enable QoS to keep game traffic first.
02
Apex lets you pick from available data centers — and Automatic or a stray selection can move you somewhere farther than your usual pick. Open the data-center list, note your choice, then compare this test’s baseline against your in-game ping: a new gap means the selection moved, not your network.
03
Wi-Fi shares spectrum with neighbours and household gadgets; interference arrives in bursts that add jitter while the bars still read full. Dense buildings make it worse. It is the classic fine-until-it-matters fault — which is why spikes land mid-fight.
04
Shared access networks fill up at night when streams and downloads compete with your match. Run this test at midday and at 9 PM from the same spot: if evenings collapse consistently, that is congestion on the line — schedule heavy transfers off-peak.
Apex’s movement punishes wireless variance: you are constantly committing to pushes, slides and exits, and a mid-action spike is worse than standing still with a slightly higher ping. Ethernet is the clean answer. If you stay wireless, sit on 5 GHz close to the router with clear line of sight, keep the band uncrowded, and measure your changes with this test — improving jitter and the “under load” row is what makes pushes feel trustworthy.
Actionable steps
Step 1
Run this test on your usual connection and once on a control (mobile data, or next to the router). Note ping, jitter and under-load latency — you are separating the line itself from how you reach it before changing anything.
Step 2
Open Apex’s data-center list and select your region deliberately instead of leaving it to Automatic. Then compare this test’s idle ping with what you see in-game — they should tell the same story; a persistent gap means the selection drifted.
Step 3
Pause launcher updates and platform downloads during play. If others share the line, enable QoS or SQM on the router so their traffic cannot monopolise the queue — verify with the “under load” row before and after.
Step 4
Ethernet removes airtime contention entirely. On Wi-Fi: 5 GHz, router elevated and in the open, away from fridges, microwaves and Bluetooth gear. Retest from your playing seat after each change and keep what lowers jitter.
Step 5
Idle wired ping above 80 ms, idle jitter above 30 ms, or repeatable packet loss are ISP-level findings. Send your ISP this test’s results, time of day and your data-center choice — measured evidence gets engineering-level replies.
A VPN reroutes your traffic through extra servers, which typically adds latency and jitter to a game where milliseconds decide a peek. It can pay off only when your ISP’s route to your chosen data center is unusually bad — a claim to test, not trust: run this test with and without the VPN and keep whichever is lower and steadier. Check the game’s and any tournament’s rules before connecting through one.
Frame rate vs connection
Apex runs at 60, 144 or 240+ frames per second depending entirely on your hardware — CPU, GPU, RAM, resolution, graphics settings, drivers and thermals — and none of those knobs touch the network. Ping is the round trip measured here. Cranking settings down raises your FPS and changes your ping by zero; upgrading your internet raises neither FPS nor your aim. When the game feels bad, decide which dial moved: frames froze (device) or did you rubber-band (network).
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 Apex Legends 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 peeks and pushes, and above 100 ms faster opponents act before your inputs land. Jitter under 15 ms and zero loss matter as much as the average — movement tech hides no spikes.
Directly — it sets the distance between you and the match server. Keep the selection deliberate rather than Automatic, then cross-check this test’s idle baseline against your in-game ping. If match numbers sit far above the baseline, re-open the data-center list and pick closer.
Evening congestion on shared access networks is the usual cause — everyone streams and downloads at the same hours. Test at midday and at 9 PM from the same spot: consistent evening degradation confirms it. Move big downloads off-peak and play on whichever connection measures better at night.
No. FPS comes from your CPU, GPU, RAM, resolution, graphics settings, drivers and thermals. Internet quality affects ping, jitter and packet loss — the network side, measured on this page. A high-refresh PC on a laggy line still loses fights, and a great line cannot render frames faster.
Sometimes, only when your ISP’s natural route to your data center is unusually bad; usually it adds latency instead. Settle it with measurement: run this test with and without the VPN and keep the lower, steadier result. Check the game’s and any tournament’s rules before using one.