Read the result
What This Device Latency Test Measures
Treat the first run as a baseline. The useful question is not whether one number is perfect; it is whether packet loss, latency, or jitter changes when you switch device, network, or connection type.
Packet loss
The percentage of test packets that never return. Zero is ideal; repeated loss matters more than one isolated run.
Latency
Round-trip delay to the selected test region. Compare devices under the same conditions instead of chasing one universal number.
Jitter
Variation in packet timing. High jitter can make calls and games stutter even when the average latency looks acceptable.
Choose a device
Test Packet Loss by Device and Operating System
Run the test on the device that shows the problem whenever its browser supports the test. For consoles, combine built-in network statistics with a same-network browser comparison instead of assuming a phone result proves the console connection is clean.
Compare, do not guess
Network Device Testing on the Same Connection
Network device testing is most useful when every test condition stays the same. If one laptop shows loss while another stays clean, focus on the affected device. If every device changes together, investigate the shared Wi-Fi, router, modem, traffic load, or ISP path.
The one-variable rule
Change only the device, Wi-Fi band, or Ethernet connection between runs. Changing several settings at once hides the cause.
- 1Connect both devices to the same Wi-Fi band or the same wired network.
- 2Pause downloads, backups, streaming, VPNs, and software updates.
- 3Use the same preset, region, duration, and time window on both devices.
- 4Repeat each run once, then compare loss, latency, and jitter patterns.
- 5Swap Wi-Fi for Ethernet on the affected device when possible.
- 6Change one variable at a time and keep the result that changes.
Isolation map
What Cross-Device Results Usually Point To
| Pattern | Likely area | Next check |
|---|---|---|
| Only one device shows loss | Device Wi-Fi radio, driver, background traffic, VPN, browser, or power-saving settings | Update and retest that device; compare Ethernet |
| Every device shows loss | Router, modem, Wi-Fi congestion, local saturation, or ISP path | Reduce traffic, restart network gear, and test wired |
| Wi-Fi is unstable, Ethernet is clean | Signal strength, interference, channel use, mesh backhaul, or distance | Improve placement, band choice, or wired access |
| No loss, but latency and jitter jump | Queue pressure, uploads, VPN routing, or congestion | Stop uploads and repeat at a quieter time |
| Browser test is clean, one console game is not | Console link, game server, region, or route differs from the browser test | Check console statistics and the game-specific path |
Device notes
PC, Mac, Mobile, PS5, Xbox, and Linux Checks
Windows PC
Run the browser test on the PC or laptop that has the problem. Repeat once on Ethernet to separate Windows, Wi-Fi, and router issues.
Test this browser deviceMac
Test in a modern browser, pause iCloud or other background transfers, then compare Wi-Fi with a wired adapter if one is available.
Test this browser deviceMobile
Compare Wi-Fi and cellular separately. This test shows connection stability; it does not report mobile download or upload Mbps.
Test this browser devicePS5
Use the console test for bandwidth, then test a nearby browser device on the same network to investigate shared packet loss, latency, or jitter.
Test this browser deviceXbox
Use Xbox network statistics for the console link. Compare this browser test during Xbox Cloud Gaming or other real-time traffic.
Test this browser deviceLinux
Start with the same browser test, then use terminal tools only when you need to compare a local gateway or a specific remote host.
Test this browser deviceRepeatable method
Make a Device Speed Test Useful
Match the network
Do not compare cellular with Wi-Fi or 2.4 GHz with Ethernet and call it a device difference.
Match the route
Keep the same test region and preset so the network path and packet pattern stay comparable.
Match the load
Pause heavy traffic, then repeat during the real activity if you are investigating load-related instability.
Continue diagnosing
Published Packet Loss Resources
FAQ
Device Speed Test FAQ
What is a good device speed?+
A good download speed depends on how many people and apps share the connection. This page measures stability rather than Mbps: aim for no repeatable packet loss, consistently low latency, and low jitter for calls, games, and other real-time traffic.
Does this device speed test measure download and upload speed?+
No. It does not measure download or upload bandwidth. It sends real-time test packets to measure packet loss, latency, and jitter—the problems a normal bandwidth result can miss.
How do I check for packet loss on a PC or laptop?+
Run the test above on the affected PC, close background transfers, and repeat it. If possible, test the same PC over Ethernet and compare another device on the same network.
How do I check packet loss on a Mac?+
Run the browser test on the Mac, pause cloud sync and VPN traffic, then repeat under the same settings. A wired comparison helps show whether the problem is macOS or the Wi-Fi path.
How do I test mobile network quality on my phone?+
Run one test on Wi-Fi and a separate test on cellular data without moving location. Compare packet loss, latency, and jitter; do not treat these values as download or upload speed.
Can I run a PS5 or Xbox internet speed test here?+
Use the console's built-in network test for its bandwidth and console-link statistics. This browser test can check a browser-capable device on the same network, but that comparison does not prove the console's own Wi-Fi link is identical.
Why does my speed test look fast while games still lag?+
Bandwidth tests show how much data can move, while games also need packets to arrive reliably and evenly. Packet loss, latency spikes, or jitter can make a fast connection feel unstable.
How do I compare network performance between two devices?+
Use the same network, test region, preset, duration, and time window. Repeat both tests and change only one variable—such as device, Wi-Fi band, or Ethernet—before comparing the results.
Use the affected device
Run the same test, then change one variable.
Start on this device, repeat the result, then compare another device or Ethernet. That pattern is more useful than one isolated speed number.