Understanding the result
Requests shows progress, Failed counts timed-out or unsuccessful HTTPS requests, and Average response summarizes successful samples. It is a request-reliability check, not raw packet capture.
Other useful tools
Packet Loss Test
Send a series of small HTTPS requests and see how many fail or time out. Browsers cannot measure raw network packet loss directly, so this test reports request failure rather than claiming a true packet-loss percentage.
Requests0/20
Failed0
Average response—ms
Failed HTTPS requests are not the same as raw packet loss.
A successful HTTPS request can still contain retransmitted packets. For true packet loss, use network tools such as ping or MTR outside the browser.
How to use this tool
- Run the sample while connected to your usual network.
- Review failed requests and the range of response times.
- Repeat if the connection seems unstable.
Troubleshooting
- Repeat on wired and Wi-Fi connections to compare whether failures are local to the wireless link.
- Pause VPNs or heavy traffic and check whether the website endpoint is reachable before interpreting failures as a connection problem.
Browser and device limitations
TCP retransmission can hide lost network packets, and a failed request can have causes other than packet loss. Browsers cannot run ICMP ping or inspect raw packets here.
RELATED TOOLS
All toolsKeep checking
Online MirrorUse your front camera as a simple on-screen mirror.Open toolSpacebar ClickerCount how quickly you press the spacebar in a timed round.Open toolInternet Speed TestMeasure approximate download, upload and response time to this website's server.Open toolBrowser TestCheck browser features, screen details and permission availability.Open toolBattery TestCheck battery charge and charging state when your browser allows it.Open tool
Common questions
Does zero failed requests mean zero packet loss?
No. TCP can retransmit lost packets, so an HTTPS request can succeed even when packets were lost.
What can cause a failed request?
Network interruption, DNS issues, a timeout, browser restrictions or server trouble can all cause failures.
What does a high average response mean?
The completed requests took longer to reach this site's server and return; distance, congestion, Wi-Fi and server load can all contribute.