Understanding the Request Waterfall
You'll learn how to read the waterfall timeline to identify request dependencies, blocking behavior, and critical rendering path bottlenecks.
What Is the Request Waterfall?
The request waterfall is a visual timeline in DevTools (Network panel) that shows when each resource starts loading, how long it takes, and what's blocking it. Each horizontal bar represents one request, stacked vertically in the order they occurred. Color-coded segments within each bar reveal different phases: DNS lookup, connection establishment, waiting for server response, and content download.
Reading the Waterfall
The horizontal axis represents time. The further right a bar extends, the longer that resource took. The vertical position shows order—resources at the top were requested first.
Key phases (left to right in each bar):
- Queueing (light gray): waiting for an available connection
- Stalled/Blocking (gray): browser delay before sending request
- DNS Lookup (green): resolving domain name
- Initial connection (orange): TCP handshake
- SSL/TLS (purple): secure connection setup
- Waiting (TTFB) (green): time until first byte from server
- Content Download (blue): receiving the response
Identifying Blocking Patterns
Look for vertical alignment—bars starting at the same time load in parallel. Staircase patterns reveal serial dependencies: one resource can't start until another finishes (common with JavaScript triggering new requests). Long waiting times suggest server bottlenecks, while long download times indicate large files or slow connections.
Critical Rendering Path
Identify which resources block page rendering—typically CSS and synchronous JavaScript in the <head>. These appear early in the waterfall and delay everything after them.
Key Takeaway: The request waterfall reveals the sequence, timing, and dependencies of resource loading, helping you spot serial bottlenecks, connection limits, and critical path blockers that slow down your site.