Request Timing Breakdown
You'll learn how to dissect a single HTTP request into its component timing phases to identify where delays actually occur.
When you look at a request in the Network panel's waterfall, you're seeing a single bar—but that bar hides a complex journey. The Request Timing Breakdown reveals the hidden stages every HTTP request passes through, from the moment your browser decides to fetch a resource until the last byte arrives.
The Timing Phases Explained
Queueing
Before your request even starts, it might wait in line. Browsers limit simultaneous connections per domain (typically 6 in HTTP/1.1). If all slots are busy, new requests queue. Think of it like waiting for an available checkout lane at a store.
DNS Lookup
The browser must translate the domain name (like example.com) into an IP address. This happens once per domain, then gets cached. Long DNS times might indicate slow DNS servers or connectivity issues.
Initial Connection
Your browser establishes a TCP connection with the server—the "handshake" that opens the communication channel. This includes network round-trip time.
SSL Negotiation
For HTTPS requests, the browser and server must agree on encryption methods and exchange certificates. This adds overhead but is essential for security. Multiple round-trips may be required.
Request/Response Time
Finally! The actual request is sent (usually very fast), then you wait for the server to process it and send back the response. The Time to First Byte (TTFB) measures server processing speed, while total response time includes downloading all content.
Why This Matters
By examining these phases in DevTools, you can pinpoint exactly where slowness originates—network issues, DNS problems, server processing delays, or simply large payloads taking time to download.
Key Takeaway: Request timing breakdown transforms a single waterfall bar into actionable data, revealing whether delays stem from connection setup, DNS, SSL negotiation, or actual data transfer.