Test results can vary with network activity, wireless conditions, device load, server route and measurement method. A difference does not automatically mean the provider changed your plan.
Compare like with like
Use the same device and test mode when checking a change. A short lower-data test and a longer standard test can sample different behavior. A nearby test endpoint and a distant application server also answer different questions. A VPN deliberately changes part of the route.
A repeatable procedure
- Keep the test mode and connection constant for a series.
- Record time and background activity alongside each run.
- Change one factor and repeat the series, including a return to the original condition.
Look for repeatable patterns
A recurring problem at a particular time is more useful evidence than a single outlier. Compare both latency and throughput. Report incomplete measurements as incomplete, and avoid claiming a cause before testing alternatives. The history comparison displays numerical differences, not a causal diagnosis.
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.