How to test your connection properly
Why the console speed test misleads, and how to measure what actually matters for gaming.
The built-in connection test on a console is useful but frequently misread. Knowing what it does and does not measure saves a lot of wasted effort.
What the console test actually tells you
It reports download speed, upload speed, and whether the platform''s network is reachable. What it does not report is stability, jitter or packet loss — and those are what cause lag.
A console can show a healthy speed and still play badly, because speed and latency are different properties. See ping, latency and servers.
Why the number is often lower than your subscription
Three reasons, all normal:
The test measures to the platform''s server, which may be far away. That is a measure of the route, not of your line.
Wi-Fi loses speed with distance and walls. A 100 Mbps line can test at 20 Mbps three rooms away.
Other devices are sharing it — a phone streaming video takes its share while you test.
Do not judge your subscription by the console test alone.
How to test properly
- Test on a phone next to the router first, with a normal speed test app. That is closest to your real line speed.
- Test on the phone where the console sits. The difference between the two is your Wi-Fi loss.
- Run the console test and compare. A large gap means the console''s connection, not your line.
- Test at two different times — evening and late night. A large difference means congestion.
What good looks like for gaming
Download: 25 Mbps is comfortable for most gaming. More only speeds up downloads, not gameplay.
Ping: under 60ms is good; above 150ms is difficult in fast games.
Stability matters more than speed. A steady 20 Mbps beats an erratic 100 Mbps for playing.
The most useful test of all
Plug the console into the router with a cable and repeat. If the problem disappears, it was Wi-Fi — and that is the most common finding of all. See fixing lag and NAT type.