Understanding Request Waterfalls
You'll learn how to read browser network waterfalls to visualize loading sequences and spot performance bottlenecks.
What is a Request Waterfall?
A request waterfall is a visual timeline that shows every network request your webpage makes, displayed in the order they occur. Think of it like a Gantt chart for your website—each horizontal bar represents a single resource (HTML, CSS, JavaScript, image, etc.), with its length showing how long that request took.
The "waterfall" name comes from how requests often cascade down the page, with some waiting for others to complete before they can even start. This visual dependency chain reveals exactly what's slowing down your page.
Reading the Waterfall
Each request bar typically shows several phases in different colors:
- DNS lookup – resolving the domain name
- Connection – establishing TCP/TLS connections
- Waiting (TTFB) – time until the first byte arrives from the server
- Content download – receiving the actual data
Horizontal positioning matters: requests further to the right started later. A request that begins only after another finishes indicates a dependency or bottleneck.
Identifying Bottlenecks
Waterfalls reveal common performance problems:
- Blocking resources – CSS or synchronous JavaScript that prevents other requests from starting
- Long TTFB – slow server response times
- Sequential loading – resources that could load in parallel but don't
- Late discovery – critical resources loaded only after JavaScript executes
You can find the waterfall in your browser's DevTools Network tab. The visualization instantly shows whether you're making too many requests, if they're properly parallelized, or if certain resources are unreasonably slow.
Key Takeaway: Request waterfalls turn invisible network activity into a visual timeline, making it easy to identify what's blocking your page from loading faster and where optimization efforts should focus.