Inspect network activity in Microsoft Edge DevTools
This is a hands-on tutorial of some of the most commonly-used DevTools features related to inspecting network activity for a page.
See Network Reference if you want to browse features instead.
When to use the Network panel
In general, use the Network panel when you need to make sure that resources are being downloaded or uploaded as expected. The most common use cases for the Network panel are:
- Making sure that resources are actually being uploaded or downloaded at all.
- Inspecting the properties of an individual resource, such as the HTTP headers, content, size, and so on.
If you are looking for ways to improve page load performance, do not start with the Network panel. There are many types of load performance issues that are not related to network activity. Start with the Audits panel because it gives you targeted suggestions on how to improve your page. See Optimize Website Speed.
Open the Network panel
To get the most out of this tutorial, open up the demo and try out the features on the demo page.
Open the Get Started Demo.
Open DevTools by pressing
J(Windows, Linux) or
J(macOS). The Console panel opens.
You may prefer to dock DevTools to the bottom of your window.
Select the Network tab. The Network panel opens.
Right now the Network panel is empty. DevTools only logs network activity after you open it and no network activity has occurred since you opened DevTools.
Log network activity
To view the network activity that a page causes:
Reload the page. The Network panel logs all network activity in the Network Log.
Each row of the Network Log represents a resource. By default the resources are listed chronologically. The top resource is usually the main HTML document. The bottom resource is whatever was requested last.
Each column represents information about a resource. In the previous figure the default columns are displayed.
- Status. The HTTP status code for response.
- Type. The resource type.
- Initiator. The cause of the resource request. Selecting a link in the Initiator column takes you to the source code that caused the request.
- Time. The duration of the request.
- Waterfall. A graphical representation of the different stages of the request. Hover over a Waterfall to see a breakdown.
The graph above the Network Log is called the Overview. You will not use the Overview graph in this tutorial, so you may hide it. See Hide the Overview pane.
After you open DevTools, it records network activity in the Network Log.
To demonstrate this, first look at the bottom of the Network Log and make a mental note of the last activity.
Now, select the Get Data button in the demo.
Look at the bottom of the Network Log again. You should see a new resource called
getstarted.json. Selecting the Get Data button caused the page to request this file.
Show more information
The columns of the Network Log are configurable. You may hide columns that you are not using.
There are also many columns that are hidden by default which you may find useful.
Right-click the header of the Network Log table and choose Domain. The domain of each resource is now shown.
See the full URL of a resource by hovering over the cell in the Name column.
Simulate a slower network connection
The network connection of the computer that you use to build sites is probably faster than the network connections of the mobile devices of your users. By throttling the page, you get a better idea of how long a page takes to load on a mobile device.
Select the Throttling dropdown, which is set to Online by default.
Choose Slow 3G.
Long-press Reload () and then choose Empty Cache And Hard Reload.
On repeat visits, the browser usually serves some files from the cache, which speeds up the page load. Empty Cache And Hard Reload forces the browser to go the network for all resources. This is helpful when you want to see how a first-time visitor experiences a page load.
The Empty Cache And Hard Reload workflow is only available when DevTools is open.
Screenshots let you see how a page looked over time while it was loading.
Select () and select the Capture screenshots checkbox.
Reload the page again via the Empty Cache And Hard Reload workflow. See Simulate a slower connection if you need a reminder on how to do this.
The Screenshots pane provides thumbnails of how the page looked at various points during the loading process.
Select the first thumbnail. DevTools shows you what network activity was occurring at that moment in time.
Select () again and deselect the Capture screenshots checkbox to close the Screenshots pane.
Reload the page again.
Inspect the details of the resource
Select a resource to learn more information about it. Try it now:
getstarted.html. The Headers tab is shown. Use this tab to inspect HTTP headers.
Select the Preview tab. A basic rendering of the HTML is shown.
This tab is helpful when an API returns an error code in HTML. You may find it easier to read the rendered HTML than the HTML source code, or when you inspect images.
Select the Response tab. The HTML source code is shown.
When a file is minified, selecting the Format () button at the bottom of the Response tab re-formats the contents of the file for readability.
Select the Timing tab. A breakdown of the network activity for this resource is shown.
Choose Close () to view the Network Log again.
Search network headers and responses
Use the Search pane when you need to search the HTTP headers and responses of all resources for a certain string or regular expression.
For example, suppose you want to verify that your resources are using reasonable cache policies.
Choose Search (). The Search pane opens to the left of the Network log.
Enter. The Search pane lists all instances of
Cache-Controlthat it finds in resource headers or content.
Select a result to view the resource in which the result was found. If you are looking at the details of the resource, select a result to go directly to it. For example, if the query was found in a header, the Headers tab opens. If the query was found in content, the Response tab opens.
Close the Search pane and the Headers tab.
DevTools provides numerous workflows for filtering out resources that are not relevant to the task at hand.
The Filters toolbar should be enabled by default. If not:
- Choose Filter () to show it.
Filter by string, regular expression, or property
The Filter text box supports many different types of filtering.
pnginto the Filter text box. Only the files that contain the text
pngare shown. In this case the only files that match the filter are the PNG images.
/.*\.[cj]s+$/. DevTools filters out any resource with a filename that does not end with a
cfollowed by 1 or more
-main.css. DevTools filters out
main.css. If any other file matched the pattern they would also be filtered out.
domain:cdn.glitch.cominto the Filter text box. DevTools filters out any resource with a URL that does not match this domain.
See Filter requests by properties for the full list of filterable properties.
Clear the Filter text box of any text.
Filter by resource type
To focus in on a certain type of file, such as stylesheets:
Choose CSS. All other file types are filtered out.
To also see scripts, hold
Control(Windows, Linux) or
Command(macOS) and then choose JS.
Choose All to remove the filters and see all resources again.
See Filter requests for other filtering workflows.
How does a page look and behave when some of the page resources are not available? Does it fail completely, or is it still somewhat functional? Block requests to find out:
P(Windows, Linux) or
P(macOS) to open the Command Menu.
block, choose Show Request Blocking, and select
Choose Add Pattern ().
Reload the page. As expected, the styling of the page is slightly messed up because the main stylesheet has been blocked.
main.cssrow in the Network Log. The red text means that the resource was blocked.
Deselect the Enable request blocking checkbox.
Congratulations, you have completed the tutorial. You now know how to use the Network panel in the Microsoft Edge DevTools!
Navigate to the Network Reference to discover more DevTools features related to inspecting network activity.
Getting in touch with the Microsoft Edge DevTools team
Use the following options to discuss the new features and changes in the post, or anything else related to DevTools.
- Send your feedback using the Send Feedback icon or select
I(Windows, Linux) or
I(macOS) in DevTools.
- Tweet at @EdgeDevTools.
- Submit a suggestion to The Web We Want.
- File bugs on this article using the Feedback section.
Portions of this page are modifications based on work created and shared by Google and used according to terms described in the Creative Commons Attribution 4.0 International License.
The original page is found here and is authored by Kayce Basques (Technical Writer, Chrome DevTools & Lighthouse).
This work is licensed under a Creative Commons Attribution 4.0 International License.