Choose a consistent device, connection and test mode. Record the conditions and repeat before treating a change as meaningful.
Prepare the comparison
Close transfers you can control, but do not assume every household device is idle. Record the VPN state and the location of a Wi-Fi device. If comparing with Ethernet, confirm which network interface is active. Keep the same test service for a before-and-after comparison.
A repeatable procedure
- Run a baseline and save its timestamp and conditions.
- Change one factor, such as using Ethernet instead of Wi-Fi.
- Repeat the original condition as well as the changed one to check consistency.
Understand the practical limits
The standard website mode can transfer about 260 MiB of configured payload, plus overhead and retries. The lower-data mode uses about 14 MiB of configured payload but can underestimate fast links or miss queueing. These modes are not interchangeable measurements. Canceling a run discards its partial result.
Use the result without overstating it
Start with the DC SPEED connection test, choose the same mode for comparable runs and label the connection conditions yourself. The result panel separates idle latency from latency during download and upload. Its before-and-after view reports differences between compatible runs; it does not identify the cause automatically. History and CSV export let you keep a record without creating an account.
For a problem in a specific game, use the gaming diagnostic guide and the game own network statistics. Read the measurement methodology before comparing this tool with another service. These instructions are a troubleshooting workflow, not a report of laboratory experiments performed by the author.