Skip to content
Tutorials Center
My learning

Topics

Lesson 15 of 36 ยท Network Panel

The Network Panel: Requests and the Waterfall

Record requests, read the request table, the waterfall and the timing summary, filter by type, and find slow or large resources, with a runnable waterfall printer.

Every file a page uses, from the HTML document to each image, font and API call, travels over the network as a request and response. The Network panel records them all. It is the first tool to open when something fails to load, loads slowly, or sends the wrong data.

Recording requests

Open the Network panel before the activity you want to see; requests that happened earlier are not recorded. Check that the red Record button (top left) is on. Then:

  • Reload the page (Ctrl+R) to record a normal page load.
  • Hard reload and clear cache (right-click the reload button while DevTools is open, or Ctrl+Shift+R) to see a first-visit load.
  • Interact with the page to record later requests, such as an API call after a click.

Useful top-bar controls:

  • Clear (the circle-slash icon) removes the list; Preserve log keeps it across navigations, which is needed to see redirects.
  • Disable cache: while DevTools is open, ignores the browser cache so every request goes out, imitating a first visit.
  • Throttling: a network speed dropdown (next lessons).
  • Import/Export HAR: save or load a recording (a later lesson).
  • Search (magnifier icon, or Ctrl+F): search request and response contents.

The request table

Each row is one request. Right-click the column headings to choose columns. The defaults include:

  • Name: the file name or last part of the URL; hover for the full URL.
  • Status: the HTTP code (200, 304, 404, ...), or a note like (failed) or (blocked).
  • Type: document, stylesheet, script, fetch/XHR, image, font, media, manifest, websocket and others.
  • Initiator: what caused the request, such as index.html:12 or a script line. Hover for the chain.
  • Size: a pair. The top value is the transferred size (over the network, compressed, including headers); the bottom value is the resource size (decompressed). It says (disk cache) or (memory cache) when no network was used.
  • Time: total time from start to finish.
  • Waterfall: a bar chart of timing, one bar per request.

Extra useful columns to add: Protocol (h2, h3), Domain, Priority, Method, Remote Address, Connection ID and Cookies.

Filters

The filter bar narrows the list:

  • Type buttons: All, Fetch/XHR, JS, CSS, Img, Media, Font, Doc, WS, Wasm, Manifest, Other. Ctrl+click to select several.
  • The text filter accepts plain text and operators such as method:POST, status-code:404, domain:cdn.example.com, larger-than:100k, mime-type:image/png, has-response-header:set-cookie, scheme:https, and a - prefix to exclude, for example -domain:analytics.com.
  • Blocked requests, 3rd-party requests and Hide extension URLs checkboxes cut noise.

To find the largest resources, sort by Size (click the Size heading); to find the slowest, sort by Time.

Reading the waterfall

The Waterfall column draws each request as a horizontal bar on a shared time axis. Hover a bar to see a timing breakdown; the same breakdown is in the Timing tab of a request. The colored sections are:

  • Queueing: waiting before the request can start (browser limits, priorities).
  • Stalled / blocked: waiting for a connection slot or proxy.
  • DNS lookup: resolving the host name to an IP address.
  • Initial connection: TCP handshake; SSL is the TLS handshake portion.
  • Request sent: sending the request (usually tiny).
  • Waiting for server response (TTFB): time to first byte. Long values mean a slow server or backend.
  • Content download: receiving the body. Long values mean a big payload or slow bandwidth.

Two vertical lines on the waterfall mark page events: blue for DOMContentLoaded and red for the load event. The summary bar at the bottom shows the same counts in text, along with the number of requests, transferred data and the finish time.

flowchart LR
  A["Queueing"] --> B["DNS lookup"] --> C["Connect and TLS"] --> D["Waiting (TTFB)"] --> E["Download"]

The bar for a request is the sum of its phases; connection setup repeats only for the first request to a host.

Stand-in: a text waterfall

A real waterfall is drawn by DevTools from the timing data of each request. The stand-in below draws a plain-text version from a list of requests with phases, so you can see how phases stack and how total time is found. It is a model with made-up numbers.

JS Stand-in: draw a text waterfall

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Look at which requests overlap: styles.css, app.js and logo.svg start about the same time because the browser fetches them in parallel. api/user waits until about 400 ms because a script triggered it, which is a dependency chain. Long chains are a classic performance problem.

Finding slow resources: a worked analysis

Suppose you recorded a page and want the top suspects. This stand-in summarizes a list of requests by type and highlights large or slow ones, mimicking what you would do by sorting columns and reading the status bar.

JS Stand-in: summarize a recording

Press Run (or Ctrl + Enter) to see the console output here.

No output.

The sort-by-size and sort-by-time habits in the Network panel give exactly these answers in a couple of clicks.

The request details pane

Click a row to open details with tabs:

  • Headers: general info (URL, method, status, remote address), request headers and response headers. Covered next.
  • Payload: query string parameters and the body that was sent (form data or JSON).
  • Preview: a formatted view of the response (a tree for JSON, a rendered image, formatted HTML).
  • Response: the raw body text.
  • Initiator: the call stack that triggered the request.
  • Timing: the phase breakdown from above.
  • Cookies: cookies sent and received, with reasons if any were blocked.

Press Esc or the close icon to hide the details and see the full table again.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Why should you open the Network panel before reloading the page?

    The panel only records while open, so open it first and then reload.
  2. 2. What does a long 'Waiting for server response' phase usually mean?

    Waiting is time to first byte; a large download appears in the Content Download phase.
  3. 3. In the Size column, what do the two values mean?

    The top value is bytes over the network; the bottom is the decompressed size.
  4. 4. Which filter text shows only POST requests?

    The method: operator filters by HTTP method.

Summary

  • Record with the panel open; use Preserve log and Disable cache when needed.
  • The table shows status, type, initiator, size, time and waterfall; filters and operators narrow it.
  • The waterfall breaks time into queueing, DNS, connection, TTFB and download.
  • The details pane has Headers, Payload, Preview, Response, Initiator, Timing and Cookies.

Next: HTTP Status Codes, Headers and Caching