Jitter is variation between latency measurements. Repeated variation can affect interactive communication, but a single jitter value cannot identify its cause.
Keep methods comparable
Different tools can calculate jitter differently. Compare runs from the same tool and mode first. Record whether the connection was busy and whether the device used Wi-Fi, Ethernet or mobile data. A number from a lightweight HTTP probe should not be treated as the same measurement as an in-game network statistic.
A repeatable procedure
- Run several tests with background transfers controlled.
- Compare Ethernet with Wi-Fi using the same device.
- Repeat during the problem period, keeping the results and their timestamps.
Follow the pattern
If only the wireless condition changes, investigate the local link. If variation grows during transfers over cable too, investigate competing traffic and queue management. If only one application shows a problem, check its server region and diagnostics. Do not infer packet loss from jitter alone.
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.