“Ping” usually means ICMP Echo — the small packets routers and desktops use to probe reachability. Websites run in a sandbox: your browser cannot send raw ICMP pings to arbitrary hosts from JavaScript. This tool does the closest honest alternative: it times a tiny HTTPS request to this same origin (/api/latency) so you see round-trip time (RTT) to WhatIsMyTools — repeatable, comparable, and useful when testing VPN or Wi‑Fi changes. It does not report latency to arbitrary IPs or game servers unless they share the exact same network path, which they usually do not.
RTT versus ICMP ping
ICMP ping measures echo request/reply timing at Layer 3, often implemented in OS utilities (ping). HTTPS RTTwraps TLS and HTTP on top of TCP — heavier than a lone ICMP packet, closer to how real web pages behave. Numbers here skew a bit higher than raw ICMP but still track “how snappy is my path toward this edge?”
Why samples jump around
Wi‑Fi airtime contention, roaming, CPU throttling on phones, QUIC vs HTTP/2, TLS 1.3 resumption, and CDN routing can shift a few milliseconds between runs. Trend matters more than a single millisecond-perfect reading.
Compare with throughput
Bandwidth measures how wide the pipe feels; latency measures responsiveness. Pair this page with our Internet Speed Test when you're diagnosing “slow browsing”: high Mbps plus bad bufferbloat can still feel sluggish.
Privacy note
Runs are initiated in your browser; see our Privacy Policy for how analytics or ads behave separately from this diagnostic.