Evaluating network performance
The Network panel records information about each network operation in your application, including detailed timing data, HTTP request and response headers, cookies, WebSocket data, and more. The Network panel helps you answer questions about the network performance of your web application, such as:
- Which resource had the slowest time to first byte?
- Which resources took the longest time to load (duration)?
- Who initiated a particular network request?
- How much time was spent in the various network phases for a particular resource?
About the Resource Timing API
The API is available to any web page, not just DevTools. In Chrome, it's exposed as methods on the global
window.performance object. The
performance.getEntries() method returns an array of "resource timing objects", one for each requested resource on the page.
This evaluates the first element in the array of resource timing objects and displays its properties in the console, as shown below.
Network panel overview
The Network panel automatically records all network activity while DevTools is open. The first time you open the panel it may be empty. Reload the page to start recording, or simply wait for network activity to occur in your application.
Each requested resource is added as a row to the Network table, which contains the columns listed below. Note the following about the Network table:
- Not all columns listed below are visible by default; you can easily show or hide columns.
- Some columns contain a primary field and a secondary field (Time and Latency, for example). When viewing the Network table with large resource rows both fields are shown; when using small resource rows only the primary field is shown.
- You can sort the table by a column's value by clicking the column header. The the Timeline column behaves a bit differently: clicking its column header displays a menu of additional sort fields. See Waterfall view and Sorting and filtering for more information.
|Name and Path||The name and URL path of the resource, respectively.|
|Method||The HTTP method used for the request (GET or POST, for example).|
|Status and Text||The HTTP status code and text message, respectively.|
|Domain||The domain of the resource request.|
|Type||The MIME type of the requested resource.|
|Initiator||The object or process that initiated the request. It can have one of the following values: |
|Cookies||The number of cookies transferred in the request. These correspond to the cookies shown in the Cookies tab when viewing details for a given resource.|
|Set-Cookies||The number of cookies set in the HTTP request.|
|Size and Content||Size is the combined size of the response headers (usually a few hundred bytes) plus the response body, as delivered by the server.Content is the size of the resource's decoded content.If the resource was loaded from the browser's cache rather than over the network, this field will contain the text (from cache).|
|Time and Latency||Time is total duration, from the start of the request to the receipt of the final byte in the response.Latency is the time to load the first byte in the response.|
|Timeline||The Timeline column displays a visual waterfall of all network requests. Clicking the header of this column reveals a menu of additional sorting fields. See Waterfall view and Sorting and filtering for more information|
Preserving the network log upon navigation
By default, the current network record log is discarded when you navigate to another page, or reload the current page. To preserve the recording log in these scenarios, click the black Preserve log upon navigation button at the bottom of the Network panel; new records are appended to the bottom of the table. Click the same button again (now red ) to disable log preservation.
Sorting and filtering
By default, resources in the Network table are sorted by the start time of each request (the network "waterfall"). You can sort the table by another column value by clicking the column header. Click the header again to change the sort order (ascending or descending).
The Timeline column is unique from the others in that, when clicked, it displays a menu of additional sort fields.
The menu contains the following sorting options:
- Timeline — Sorts by the start time of each network request. This is the default sort, and is the same as sorting by the Start Time option).
- Start Time — Sorts by the start time of each network request (same as sorting by the Timeline option).
- Response Time — Sorts by each request's response time.
- End Time — Sorts by the time when each request completed.
- Duration — Sorts by the total time of each request.
- Latency — Sorts by the time between the start of the request and the beginning of the response (also known as the "time to first byte").
To filter the Network table to only show certain types of resources, click one of the content types along the bottom of the panel: Documents, Stylesheets, Images, Scripts, XHR, Fonts, WebSockets, and Other. In the following screenshot only CSS resources are shown. To view all content types, click the All filter button.
In addition to resource type filtering, you can narrow down resources by filter queries. For example, to find all resources which have a status code of
200, you can enter the query
StatusCode:200 in the filter input field.
Take note of the following behaviour: A filter query includes a type (
StatusCode) and value (
200). A filter query is case insensitive, so you can type uppercase or lowercase. The filter type gives you autocomplete suggestions. Use the arrows keys to form a selection and press Tab to select it. The filter value has autocomplete which shows you values present in the current network recording. Quickly preview the results of your query, use the Up / Down arrow keys to cycle through the autocomplete suggestions. The results appear immediately even you do not press enter or tab to complete the selection. To negate a filter query, prepend the query with a dash (
-), for example
Available filter types:
- The domain portion from the URL of the resource. E.g.
- Checks the resource has a response header, regardless of the value. E.g.
- Shows requests running at the current point in time. Current available value:
- Shows requests with a transfer size larger than the specified amount. Units assumed in bytes, but kilobyte (
k) & megabyte (
m) units also allowed: E.g.
- The HTTP method used. E.g.
- Also known as
Content-type- the identifier for the type of resource. E.g.
- The scheme portion in a URL. E.g.
- The name of the cookie as set by the server. E.g.
loggedIn(assuming a cookie like
- The value of the cookie set by the server. E.g.
true(assuming a cookie like
- The domain of the cookie as set by the server. E.g.
foo.com(assuming a cookie like
loggedIn=true; Domain=foo.com; Path=/; Expires=Wed, 13 Jan 2021 22:23:01 GMT; HttpOnly).
- The status code in the HTTP response. E.g.
To use a query shown in the above list, construct it in the format of:
<Filter Type>:<Description>. You will almost always want to use the autocomplete suggestions which ensures your query is valid.
Adding and removing table columns
You can change the default set of columns displayed by the Network table. To show or hide a column, Right+click or Control+click (Mac only) in the table header and select or deselect column names from the list.
Changing resource row sizes
You can view the Network table with large resource rows (the default), or small resource rows. Click the blue Use small resource rows toggle button at the bottom of the panel to view small rows. Click the same button (now gray ) to view large resource rows again. Large rows enable some columns to display two text fields: a primary field and a secondary field (Time and Latency, for instance). When viewing small rows only the primary field is displayed.
The waterfall view in the network panel graphs the time it took to load each resource.From the start of the HTTP request to the receipt of the final byte of the response.
Each resource loading time is represented as a bar.This has color-coded information related to each resource.Each color specifies a different step needed to recieve the resource.The larger the bar grows represents more data being trasmitted for the request.
Hovering your mouse over the bar itself will present the complete timing data.This is the same information that's presented in the Timing details tab for a given resource.
The waterfall highlights
load events display with blue and red vertical lines. When the engine has completed parsing of the main document the
DOMContentLoaded event fires. Upon retrieving all the page's resources the
load event will fire.
You may enable in the network settings to view the timeline as color-coded by resource type.If you do the network timing information is still accessible through the tooltip.Waterfall bars are color-coded as follows:
Saving and copying network information
Right-clicking or Ctrl + Click (Mac only) within the Network table a context menu appears with several actions. Some of these actions apply to the resource row under the mouse click (like copying HTTP request headers), while others apply to the entire network recording (such as saving a Network recording as a HAR file).
The following menu actions apply to the selected resource:
- Open Link in New Tab — Opens the resource in a new tab. You can also double-click the resource name in the Network table.
- Copy Link Address — Copies the resource URL to the system clipboard.
- Copy Request Headers — Copies the HTTP request headers to the system clipboard.
- Copy Response Headers — Copies the HTTP response headers to the system clipboard.
- Copy as cURL — Copies the network request as a cURL command string to the system clipboard. See Copying requests as cURL commands.
- Replay XHR — If the associated request is an XMLHTTPRequest, re-sends the original XHR.
Copying requests as cURL commands
cURL is a command line tool for making HTTP transactions. The Network panel's Copy as cURL command recreates an HTTP request (including HTTP headers, SSL certificates, and query string parameters) and copies it as a cURL command string to the clipboard. You can then paste the string into a terminal window (on a system with cURL) to execute the same request.
Below is an example cURL command line string taken from a XHR request on the Google News home page.
curl 'http://news.google.com/news/xhrd=us' -H 'Accept-Encoding: gzip,deflate,:sdch' -H 'Host: news.google.com' -H 'Accept-Language: en-US,en;q=0.8' -H 'User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/29.0.1510.0 Safari/537.36' -H 'Accept: */*' -H 'Referer: http://news.google.com/nwshp?hl=en&tab=wn' -H 'Cookie: NID=67=eruHSUtoIQA-HldQn7U7G5meGuvZOcY32ixQktdgU1qSz7StUDIjC_Knit2xEcWRa-e8CuvmADminmn6h2_IRpk9rWgWMdRj4np3-DM_ssgfeshItriiKsiEXJVfra4n; PREF=ID=a38f960566524d92:U=af866b8c07132db6:FF=0:TM=1369068317:LM=1369068321:S=vVkfXySFmOcAom1K' -H 'Connection: keep-alive' --compressed
Saving network data
You can save the data from a network recording as a HAR (HTTP Archive) file, or copy the records as a HAR data structure to your clipboard. A HAR file contains a JSON data structure that describes the network "waterfall". Several third-party tools can reconstruct the network waterfall from the data in the HAR file.
To save a recording:
- Right+click or Control+click on the Network table.
- In the context menu that appears, choose one of the following actions:
- Copy All as HAR — Copies the network recording to the system clipboard in the HAR format.
- Save as HAR with Content — Saves all network data to a HAR file along with each page resource. Binary resources, including images, are encoded as Base64-encoded text.
For more information, Web Performance Power Tool: HTTP Archive (HAR).
Network resource details
When you click a resource name in the Network table a tabbed window appears that contains the following additional details:
- HTTP request and response headers
- Resource preview
- HTTP response
- Cookie names and values
- WebSocket messages
- Resource network timing
The Headers tab displays the resource's request URL, HTTP method, and response status code. Additionally, it lists the HTTP response and request headers and their values, and any query string parameters. You can view HTTP headers parsed and formatted, or in their source form by clicking the View parsed/View source toggle button, respectively, located next to each header's section. You can also view parameter values in their decoded or URL encoded forms by clicking the View decoded/View URL encoded toggle button next to each query string section.
You can also copy request and response headers to your clipboard.
The Preview tab displays a preview of the resource, when available. Previews are currently displayed for image and JSON resources, as shown below.
You can view the resource's unformatted response on the Responsetab.
The Response tab contains the resource's unformatted content. Below is a screenshot of a JSON data structure that was returned as the response for a request.
You can also view formatted previews of some resource types, including JSON data structures and images.
The Cookies tab displays a table of all the cookies transmitted in theresource's HTTP request and response headers. You can also clear all cookies.
The Cookies table contain the following columns:
|Name||The cookie's name.|
|Value||The cookie's value.|
|Domain||The cookie's domain.|
|Path||The cookie's URL path.|
|Expires / Max-Age||The value of the cookie's expires or max-age properties.|
|Size||The size of the cookie in bytes.|
|Secure||The presence of this attribute indicates that the cookie should only be transmitted over a secure connection.|
The Frames tab shows messages sent or received over a WebSocket connection. This tab is only visible when the selected resource initiated a WebSocket connection. The table contains the following columns:
|Data||The message payload. If the message is plain text, it's displayed here. For binary opcodes, this field displays the opcode's name and code. The following opcodes are supported: |
|Length||The length of the message payload in bytes.|
|Time||The time stamp when the message was created.|
Messages are color-coded according to their type. Outgoing text messages are color-coded light-green; incoming text messages are white:
WebSocket opcodes are light-yellow:
Errors are light-red.
Notes about current implementation:
- To refresh the Frames table after new messages arrive, click the resource name on the left.
- Only the last 100 WebSocket messages are preserved by the Frames table.
Resource network timing
The Timing tab graphs the time spent on the various network phases involved loading the resource. This is the same data displayed when you hover over a resource bar in the waterfall view.
- Time the request spent waiting before it could be sent. This time is inclusive of any time spent in proxy negotiation. Additionally, this time will include when the browser is waiting for an already established connection to become available for re-use, obeying Chrome's maximum six TCP connection per origin rule.
- Proxy Negotiation
- Time spent negotiating with a proxy server connection.
- DNS Lookup
- Time spent performing the DNS lookup. Every new domain on a page requires a full roundtrip to do the DNS lookup.
- Initial Connection / Connecting
- Time it took to establish a connection, including TCP handshakes/retries and negotiating a SSL.
- Time spent completing a SSL handshake.
- Request Sent / Sending
- Time spent issuing the network request. Typically a fraction of a millisecond.
- Waiting (TTFB)
- Time spent waiting for the initial response, also known as the Time To First Byte. This time captures the latency of a round trip to the server in addition to the time spent waiting for the server to deliver the response.
- Content Download / Downloading
- Time spent receiving the response data.
To learn more optimizing the network performance of your application, see the following resources:
- Use PageSpeed Insights to identify performance best practices that can be applied to your site, and PageSpeed optimization tools to automate the process of applying those best practices.
- High Performance Networking in Google Chrome discusses Chrome network internals and how you can take advantage of them to make your site faster.
- How gzip compression works provides a high level overview gzip compression and why it's a good idea.
- Web Performance Best Practices provides additional tips for optimizing the network performance of your web page or application.