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?
[[TOC]]
## About the Resource Timing API
The Network panel uses the [Resource Timing API](http://www.w3.org/TR/resource-timing), a JavaScript API that provides detailed network timing data for each loaded resource. For example, the API can tell you precisely when the HTTP request for an image started, and when the image's final byte was received. The following illustration shows the network timing data points that the Resource Timing API provides.
<imgsrc="network-files/resource-timing-overview.png"alt="alt text"/><!-- TODO: Fix alt text and URL -->
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.
Chrome](http://updates.html5rocks.com/2012/08/When-milliseconds-are-not-enough-performance-now) as the `window.performance.now()` method.
## 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.
* Some columns contain a primary field and a secondary field (**Time** and **Latency**, for example). When viewing the Network table with [large resource rows](#changing_resource_row_size) both fields are shown; when using small resource rows only the primary field is shown.
* You can [sort](#sorting_and_filtering) the table by a column's value by clicking the column header. The [the Timeline column](#timeline_view) behaves a bit differently: clicking its column header displays a menu of additional sort fields. See [Timeline view](#timeline_view) and [Sorting and filtering](#sorting_and_filtering) for more information.
<td><strong>Name</strong> and <strong>Path</strong></td>
<td>The name and URL path of the resource, respectively.</td>
</tr>
<tr>
<td><strong>Method</strong></td>
<td>The HTTP method used for the request (GET or POST, for example).</td>
</tr>
<tr>
<td><strong>Status</strong> and <strong>Text</strong></td>
<td>The HTTP status code and text message, respectively.</td>
</tr>
<tr>
<td><strong>Domain</strong></td>
<td>The domain of the resource request.</td>
</tr>
<tr>
<td><strong>Type</strong></td>
<td>The MIME type of the requested resource.</td>
</tr>
<tr>
<td><strong>Initiator</strong></td>
<td>The object or process that initiated the request. It can have one of the following values:
<dl>
<dt>Parser</dt>
<dd>Chrome's HTML parser initiated the request.</dd>
<dt>Redirect</dt>
<dd>A HTTP redirect initiated the request.</dd>
<dt>Script</dt>
<dd>A script initiated the request.</dd>
<dt>Other</dt>
<dd>Some other process or action initiated the request, such as the user navigating to a page via a link, or by entering a URL in the address bar.</dd>
</dl>
</td>
</tr>
<tr>
<td><strong>Cookies</strong></td>
<td>The number of cookies transferred in the request. These correspond to the cookies shown in the <ahref="#request_and_response_cookies">Cookies tab</a> when viewing details for a given resource.</td>
</tr>
<tr>
<td><strong>Set-Cookies</strong></td>
<td>The number of cookies set in the HTTP request.</td>
</tr>
<tr>
<td><strong>Size</strong> and <strong>Content</strong></td>
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).</td>
</tr>
<tr>
<td><strong>Time</strong> and <strong>Latency</strong></td>
<td>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.</td>
</tr>
<tr>
<td><strong>Timeline</strong></td>
<td>The Timeline column displays a <ahref="#timeline_view">timeline view</a> of all network requests. Clicking the header of this column reveals a menu of additional sorting fields. See Timeline view and Sorting and filtering for details.</td>
</tr>
</tbody>
</table>
### 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 <imgsrc="network-files/keep-log-off.png"alt="alt text"/> at the bottom of the Network panel; new records are appended to the bottom of the table. Click the same button again (now red <imgsrc="network-files/keep-log-on.png"alt="alt text"/><!-- TODO: Fix alt text and URL -->) to disable log preservation.
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.
<imgsrc="network-files/timeline-column.png"alt="alt text"/><!-- TODO: Fix alt text and URL -->
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.
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.
<imgsrc="network-files/add-remove-columns.png"alt="alt text"/><!-- TODO: Fix alt text and URL -->
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 <imgsrc="network-files/small-resource-rows.png"alt="alt text"/> at the bottom of the panel to view small rows. Click the same button (now gray <imgsrc="network-files/large-rows.png"alt="alt text"/>) 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.
In the following screenshot, the Network table is viewed with small resource rows and just the Timeline column.
<imgsrc="network-files/small-rows.png"alt="">
### Timeline view
The Timeline 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, color-coded according to the resource type. The length of the lighter-shaded part of each bar represents the request's latency, while the length of the darker-shaded part represents the time spent receiving the response data.
When you hover your mouse over a timeline row (but not over an actual bar) the request's latency and receipt time are displayed above the corresponding bar's light- and dark-shaded areas, respectively, as shown below.
<imgsrc="network-files/timeline-view-1.png"alt="alt text"/><!-- TODO: Fix alt text and URL -->
If you hover your mouse over the timeline bar itself, the complete timing data for the resource is presented in a pop-up. This is the same information that's presented in the [Timing details tab](#resource_network_timing) for a given resource.
The timeline indicates when the the [`DOMContentLoaded`](http://docs.webplatform.org/wiki/dom/events/DOMContentLoaded)
and [`load`](http://docs.webplatform.org/wiki/dom/events/load) events were fired with blue and red vertical lines, respectively. The `DOMContentLoaded` event is fired when the main document had been loaded and parsed. The `load` event is fired when all of the page's resources have been downloaded.
Right+clicking or Control+clicking (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](#copying_requests_as_curl_commands)), while others apply to the entire network recording (such as [saving a Network recording as a HAR file](#saving_network_data)).
<imgsrc="network-files/right-click.png"alt="alt text"/><!-- TODO: Fix alt text and URL -->
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.
[cURL](http://curl.haxx.se/) 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](http://www.softwareishard.com/blog/har-12-spec/)) 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](http://ericduran.github.io/chromeHAR/) [tools](https://code.google.com/p/harviewer/) can reconstruct the network waterfall from the data in the HAR file.
**To save a recording:**
1. Right+click or Control+click on the Network table.
2. 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)](http://www.igvita.com/2012/08/28/web-performance-power-tool-http-archive-har/).
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.
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.
<td>The value of the cookie's expires or max-age properties.</td>
</tr>
<tr>
<td><strong>Size</strong></td>
<td>The size of the cookie in bytes.</td>
</tr>
<tr>
<td><strong>HTTP</strong></td>
<td>This indicates that the cookie should only be set by the browser in the HTTP request, and cannot be accessed with JavaScript. </td>
</tr>
<tr>
<td><strong>Secure</strong></td>
<td>The presence of this attribute indicates that the cookie should only be transmitted over a secure connection.</td>
</tr>
</tbody>
</table>
### WebSocket frames
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:
<table>
<tr>
<thwidth="20%">Name</th>
<th>Description</th>
</tr>
<tr>
<td>Data</td>
<td>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:
<dl>
<dt>Continuation Frame</dt>
<dt>Binary Frame</dt>
<dt>Connection Close Frame</dt>
<dt>Ping Frame</dt>
<dt>Pong Frame</dt>
</dl>
</tr>
<tr>
<td>Length</td>
<td>The length of the message payload in bytes.</td>
</tr>
<tr>
<td>Time</td>
<td>The time stamp when the message was created.</td>
* 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 [Timeline view](#timeline_view).
The table below lists the network phases shown in the Timing tab and their descriptions.
<!-- TODO: Fix formatting of cells -->
<table>
<tr>
<thstyle="width:20%">Property</th>
<th>Description</th>
</tr>
<tr>
<td><strong>Proxy</strong></td>
<td>Time spent negotiating with a proxy server connection.</td>
</tr>
<tr>
<td><strong>DNS Lookup</strong></td>
<td>Time spent performing the DNS lookup. You want to minimize DNS look ups.</td>
</tr>
<tr>
<td><strong>Blocking</strong></td>
<td>Time the request spent waiting for an already established connection to become available for re-use.</td>
</tr>
<tr>
<td><strong>Connecting</strong></td>
<td>Time it took to establish a connection, including TCP handshakes/retries, DNS lookup, and time connecting to a proxy or negotiating a secure-socket layer (SSL). </td>
</tr>
<tr>
<td><strong>Sending</strong></td>
<td>Time spent sending the request.</td>
</tr>
<tr>
<td><strong>Waiting</strong></td>
<td>Time spent waiting for the initial response.</td>
</tr>
<tr>
<td><strong>Receiving</strong></td>
<td>Time spent receiving the response data. </td>
</tr>
</table>
## Additional resources
To learn more optimizing the network performance of your application, see the following resources:
* Use [PageSpeed Insights](/speed/pagespeed/insights) to identify performance best practices that can be applied to your site, and [PageSpeed optimization tools](/speed/pagespeed/optimization) to automate the process of applying those best practices.
Chrome](http://www.igvita.com/posa/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](/speed/articles/gzip) provides a high level overview gzip compression and why it's a good idea.
* [Web Performance Best Practices](/speed/docs/best-practices/rules_intro) provides additional tips for optimizing the network performance of your web page or application.
