Guides
How to Read Speed Test Results
Interpret Mbps, ping, bars and quality scores, compare your plan and choose useful follow-up checks.
After the test finishes, read the available measurements before judging the connection. VMAXCHECK uses M-Lab NDT to measure data transfer over one TCP connection between your device and a test server at that time. This does not test every app or identify a fault on its own. Record the time, server, device and whether you used Wi-Fi or Ethernet.
What the numbers measure
- Download measures data coming to your device; upload measures data leaving it. Both are shown in Mbps. Compare each direction with the corresponding plan value. A high transfer rate does not establish a fast response in a game.
- Mbps means millions of bits per second; MB/s means millions of bytes per second. There are eight bits in a byte, so 100 Mbps corresponds numerically to 12.5 MB/s. This does not guarantee an app download rate: the remote service, device and storage also matter. MiB/s uses a different byte unit.
- The displayed ping is derived from the test server’s TCP timing statistics during NDT and rounded to milliseconds. It is not a measurement of your game server, delay spikes or separate idle and loaded latency. The site’s 30, 60 and 100 ms boundaries are not universal app requirements.
- An absent upload or latency value is not zero, and an interrupted test is not a complete result. Read any error and repeat if needed. Run throughput tests outside calls, streams or games: they create traffic. M-Lab publishes measurement results and the public IP address used for the test.
Read bars and percentages separately
The speed bars use a nonlinear scale with anchors from 1 Mbps to 10 Gbps. Half a bar does not mean half the maximum speed or half your plan. Use the numeric Mbps value. The plan percentage is a separate calculation: measured speed divided by your entered value, multiplied by 100 and rounded. A measured 300 Mbps against an entered 500 Mbps produces 60%.
What the quality rating means
- The overall label follows the lowest of the site’s own download, upload and latency levels. It does not average three measurements. A low upload can therefore limit the rating even with a fast download.
- The score displayed out of 100 is a fixed value assigned to that level. It is not a plan percentage or a measured reliability rate. The label does not prove that all measurements are available.
- Browsing, streaming, gaming and call ratings use simple thresholds. They are guidance rather than actual tests of those apps or guarantees of video, game or call quality. Check the relevant app’s current requirements and actual performance.
Compare with the right plan value
Enter download and upload separately, using the same units and the provider’s definition of each advertised value. Do not assume they must be equal. Your entry supplies the denominator; it does not independently verify the contract. One result, or the site’s own warning below 60%, does not prove a contractual shortfall or its cause. Use the provider’s documented conditions and measurement method when evaluating a contractual claim.
Choose a comparison that answers a question
- Repeat with the same device, method and connection type, and record the server and time. Compare quieter and busier periods. A different test service or server is a different measurement; do not treat a single difference as proof of a fault.
- Pause your own background transfers and repeat, changing one factor at a time. An improvement points to an effect worth checking; it does not prove that the plan itself was wrong.
- Compare Wi-Fi and Ethernet on the same device, checking which interface is active and whether its adapter and port can support the expected rate. Ethernet connected to a mesh unit may still use a wireless uplink. The comparison alone does not justify buying a router.
- If NDT looks good but one app performs poorly, compare that app on another device and other services on the original device. Record the app error, quality setting and reproducible symptom. Different services can use different servers and paths.
Keep evidence for the next step
Save comparable numeric results, times, connection details and the steps that reproduce the problem. Give support those observations, without passwords, and explain which devices or services are affected. If your actual use works well, a higher label alone is not a reason to pay more. Check the suspected cause before changing the plan or equipment.