🏓 HTTP Ping Test
Measure DNS, TCP, TLS, TTFB and total response time for any website or API.
Understanding HTTP latency components
DNS Lookup — Time to resolve the domain name to an IP address. Fast for cached domains (<5ms), slower for cold lookups (20–100ms). Reduce with a fast DNS provider or CDN.
TCP Connect — Time to establish a TCP connection with the server. Primarily determined by physical distance (network latency). A server in India takes ~150ms to connect from Europe; a CDN edge node takes <10ms.
TLS Handshake — Time to negotiate encryption for HTTPS. TLS 1.3 requires one round-trip; TLS 1.2 requires two. CDNs terminate TLS at the edge, reducing this to near zero for most visitors.
TTFB (Time to First Byte) — Time from sending the request to receiving the first byte of the response body. This is the most important metric for server performance — it reflects database queries, rendering, caching, and backend processing time.
Transfer Time — Time to download the response body after the first byte. Proportional to response size and available bandwidth.
What is a good TTFB?
Google's Core Web Vitals guidelines rate TTFB as: Good = under 800ms, Needs improvement = 800ms–1800ms, Poor = over 1800ms. For APIs and SPAs, aim for under 200ms. For rendered HTML pages, under 400ms is a reasonable target.
Frequently Asked Questions
This tool measures the full HTTP request lifecycle: DNS resolution time (domain → IP), TCP connection time, TLS/SSL handshake time (for HTTPS), Time to First Byte (TTFB), and total response time. It runs multiple pings and shows min, avg, and max values.
TTFB is the time from sending the HTTP request to receiving the first byte of the response. It reflects server processing time plus network latency. Google recommends TTFB under 200ms for a good Core Web Vitals score. High TTFB usually means slow server-side processing, distant hosting, or no CDN.
No — this tool sends an HTTP request and measures response time, which is more relevant for websites and APIs than raw ICMP ping. ICMP ping measures raw network connectivity but doesn't account for DNS resolution or HTTP server processing time.
Under 200ms total is excellent. 200–500ms is good. 500ms–1s is acceptable. Over 1s is slow and will hurt user experience and SEO. For APIs, under 100ms is the target for interactive endpoints.
The first ping always does a fresh DNS lookup. Subsequent pings may benefit from the OS-level DNS cache. If DNS time is consistently slow (>100ms), consider switching to a faster DNS registrar or using a CDN that manages DNS with anycast routing.
TLS handshake involves cryptographic key exchange — typically one round-trip of network latency plus server CPU time. Modern TLS 1.3 reduces this to 1 round-trip (vs 2 for TLS 1.2). CDNs terminate TLS at edge locations, dramatically reducing TLS time for global visitors.