This route measures request timing, not Mbps
The network check times five small HTTP requests to httpbin.org. It reports the mean completed-request duration and the mean absolute difference between consecutive completed samples. These are application-level request timings, not ICMP ping or packet-level jitter.
Results include browser scheduling, connection setup when needed, transport and server processing. The endpoint's location and load affect the result. A no-cors response is opaque: completion does not verify an HTTP success status.
Use the comparison you can control
- Run the check and note the completed sample count, average and variation.
- Repeat near the Wi-Fi access point under similar load. Compare with Ethernet or another connection if available.
- Change only one condition at a time. If this endpoint is slow but ordinary sites work, the test service or its route may be the cause.
Missing samples or a timeout mean the request could not complete in the allowed time. They do not identify an ISP fault. This short check cannot certify call quality, quantify packet loss or measure download/upload bandwidth.
Separate network trouble from call hardware
If a call is silent even on a stable connection, test the microphone recording and speaker output. A camera preview that works locally but freezes only in calls points to a different path than a preview that never opens.
Unlike local media tools, this test contacts an external service, which receives normal connection data such as your IP address. Each request has a timeout and leaving the page aborts the run. See the privacy policy.