Skip to content

Tool: HTTP Latency

Ade Ramdani edited this page May 26, 2026 · 1 revision

HTTP Latency

Full HTTP request waterfall — DNS resolution, TCP connect, TLS handshake, TTFB, and download phases.


What it does

Makes an HTTP/HTTPS request and uses URLSessionTaskMetrics to extract precise phase timings without any custom instrumentation.


Interface

Element Description
URL field Full URL (with or without https://). Press Return to run.
Method GET, POST, HEAD, PUT, DELETE
Run / Cancel Execute request; red Cancel while in-flight
Run Again Re-run the same URL from the result summary bar
History table Previous results — click a row to restore URL + method

Phase Breakdown

Phase Measured From
DNS domainLookupStartDatedomainLookupEndDate
TCP Connect connectStartDateconnectEndDate
TLS Handshake secureConnectionStartDatesecureConnectionEndDate
Request Sent requestStartDaterequestEndDate
TTFB requestEndDateresponseStartDate
Download responseStartDateresponseEndDate
Total DNS start → download end

Summary Bar

Shown after a completed request:

  • HTTP status code (color-coded: green 2xx, orange 3xx, red 4xx/5xx)
  • Total time
  • Response size
  • IP address used
  • Protocol (HTTP/1.1, HTTP/2, HTTP/3)

Tips

  • DNS = 0 ms usually means the hostname was already cached
  • TLS > 200 ms on first request is normal; subsequent requests reuse the session
  • Use HEAD method for latency checks without downloading the response body
  • History table lets you compare repeated runs side by side
  • Large download times with fast TTFB indicate the response body is large, not the server

Clone this wiki locally