Measure the quiet connection first, then observe how response time changes during download and upload. Keep the two loaded directions separate.
Check the direction of congestion
A background upload can affect a call even when the download has plenty of capacity. Conversely, downstream traffic can expose a different bottleneck. The browser result describes the full path to the test server, so a difference between the two directions does not locate the responsible device on its own.
A repeatable procedure
- Pause other transfers and run the standard test.
- Repeat once while the problematic household activity is present.
- Restore quiet conditions and repeat again to check whether the change is consistent.
What counts as useful evidence
Keep the time, connection type, test mode and both loaded measurements. An unavailable field must remain unavailable. A lower-data run can be useful on a metered link, but it may not keep a fast connection busy long enough to expose queueing. Repeat a standard run when the data allowance permits.
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.