How the checklist works
Your browser runs the same tests as the network report: test requests over IPv4 and IPv6, round trips to this site, a download and upload test, and a WebRTC check. This site adds its lookups of your address on public blocklists and hosting network lists.
Each check reads one result and compares it with a plain threshold: latency under 200 ms, jitter under 30 ms, no unanswered requests, at least 10 Mbps down and 3 Mbps up, and a device clock in the same time zone as the IP location. Those are the levels where video, calls and browsing start to suffer.
Reading the results
Check this does not always mean something is broken: a VPN is supposed to show signs of a VPN. No IPv6 shows as Not in use, because many providers do not offer it yet and every website still works over IPv4. The steps under each item say when a result needs no action.
- Test on a cable and on Wi-Fi. A difference between the two points at the Wi-Fi, not the provider.
- Pause other downloads and backups, then reload the page to test again.
- Copy the checklist into a support ticket: it lists every result and when it was measured.
Questions
- Why does it say my latency is fine when pages feel slow?
- Latency is measured to this site. A slow site elsewhere, a busy DNS resolver or a browser extension can slow pages without affecting the round trip here.
- Does running the checklist use much data?
- The speed test at the bottom uses about 50 MB on a slow line and more on a fast one. It does not start on its own when your device reports mobile data or data saver.