Network Waterfall in Performance View
You'll learn how the Performance panel's network waterfall reveals the relationship between network requests, JavaScript execution, and rendering work.
While the Network panel shows you what loads and when, the Performance panel's network waterfall adds crucial context: how network activity interacts with browser rendering and script execution.
The Combined View
Think of the Network panel as showing trains arriving at a station, while the Performance view shows how those trains affect the entire city's traffic system. In the Performance timeline, network requests appear alongside:
- Main thread activity (parsing, JavaScript execution, layout, paint)
- GPU rendering work
- Frame boundaries and timing
This combined view reveals cause-and-effect relationships you'd miss looking at network alone.
What You Can Analyze
Request Timing in Context
See exactly when a script finishes downloading versus when it starts executing. A stylesheet might load quickly but block rendering while the browser parses it. The Performance waterfall shows both the network bar and the subsequent parsing work on the main thread.
Priority and Execution Correlation
High-priority resources (like blocking CSS) appear with different colors and you can trace their impact: request completes → parsing starts → layout triggered → paint happens. It's a complete story, not just isolated events.
Rendering Bottlenecks
Identify if a long task is caused by a large script that just downloaded, or if network delays are waiting on JavaScript that's blocking the connection queue.
Real Impact Measurement
The waterfall sits directly above the FPS graph and frame timeline, so you see immediate visual proof: "This image request completing triggered a layout shift" or "These three scripts executing back-to-back caused frame drops."
Key Takeaway: The Performance panel's network waterfall connects network activity to browser processing, revealing how downloads trigger work that affects user experience beyond just load time.