Responses

Measuring request timing

See where a request spent its time, from DNS lookup to the last byte, including each redirect.

Overview

The Timeline tab of the response inspector breaks a request down into the stages of its exchange with the server, so you can tell whether a slow response comes from the network, the connection or the server itself. The tab's name shows the request's total time.

Read the timeline

In the response inspector, click Timeline. At the top, the tab shows two figures:

  • Total Time: How long the whole send took, from starting the request to receiving the last byte, including any redirects.
  • Response Size: The size of the response body.

Below them, a bar for each stage shows how long it took:

StageWhat it measures
DNS LookupLooking up the host's IP address.
TCP ConnectOpening the connection to the server.
TLS HandshakeSetting up the secure connection for an https URL.
Server ProcessingWaiting from the end of the request to the first byte of the response.
Content TransferReceiving the response, from its first byte to its last.

A stage that didn't happen shows 0 ms, such as TLS Handshake for an http URL.

The Waterfall below the bars places the stages one after another in a single bar, colored to match the legend, so you can see how they add up.

For an event stream, Content Transfer is called Streaming and measures how long the stream was open.

Follow a redirect chain

When Relay follows redirects, the tab adds a Redirect Chain section above the stages. It has one row for each request in the chain, labeled with its status and host, such as "301 example.com", and drawn where it started and as long as it took. The last row is the final response.

The stages below the chain, under Final Response, describe the request that got the final response.

See Also

  • Inspecting responses: Read a response's status, body and headers, and copy or save what you need.
  • Following redirects: Choose whether Relay follows redirects, how many, and what it sends to the next location.
  • Configuring request settings: Set the timeout, redirect behavior, proxy and certificate checks for a request or a group of requests.