Packet Loss Test
Sends 30 small requests to a global edge network and counts how many fail or time out, alongside average latency and jitter.
How to read the result
- 0% — healthy connection.
- 0.1–1% — acceptable; typical of busy WiFi.
- 1–3% — voice and gaming quality suffers.
- Above 3% — a real fault: cabling, hardware or upstream congestion.
Troubleshooting order
- Re-test over Ethernet to separate WiFi problems from line problems.
- Swap the cable and try a different router port.
- Test at several times of day to detect congestion patterns.
- Reboot the modem and router, then re-test.
- Share the results with your ISP if loss persists on a wired connection.
Frequently Asked Questions
Get answers to common questions about internet speed testing.
SwiftNetScan