Network connectivity test

This tool measures browser HTTPS response times to probe endpoints, not command-line ICMP ping. Timing can include DNS, TLS, proxy routing, connection reuse, server processing and browser scheduling. It is a website latency and connectivity check, not a download or upload speed test.

Finish a test on your current connection and download its report. Switch your proxy, VPN, Wi-Fi or mobile hotspot and run again. Compare the same site's response count and median. Groups classify sites, not the physical location of responding servers; a CDN may respond nearby.

Each site receives 3 sequential lightweight requests. Successful response times are sorted and the middle value is used; with two responses, their average is used. Failures never count as 0ms. One or two responses are marked partial so you can inspect each round before comparing.

Browser security policies, privacy extensions, corporate networks, target-site restrictions or a changed probe endpoint can block cross-site requests. A timeout means a round did not finish within 5 seconds; it does not prove an outage or blocking. Open the site directly and compare on another connection.

Not necessarily. Each test checks a selected favicon or lightweight endpoint, sometimes on the brand's CDN or API domain. Cross-origin responses may be opaque, so a response does not confirm HTTP 200, sign-in access, regional eligibility or full application availability.

Requests run directly in your browser. AdsCrawl does not proxy the probes or upload test results. A full run makes at most 144 lightweight requests without site credentials; destinations still see your exit IP and standard request information. Keep the tab in the foreground for more consistent timing, or stop at any time.