You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: microsoft-edge/devtools-guide-chromium/performance/overview.md
+39-2Lines changed: 39 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -130,6 +130,10 @@ In contrast, a recorded performance trace shows information about the performanc
130
130
| local metrics, local data | The LCP, CLS, and INP metrics. They are captured locally on the inspected webpage, and are updated as you interact with the page. ||
131
131
| field metrics, field data | Data from the Chrome UX Report (CrUX), showing how most of your users experience your website. |[Overview of CrUX](https://developer.chrome.com/docs/crux)|
When you open the **Performance** tool, it immediately captures and displays the local [Largest Contentful Paint (LCP)](https://web.dev/articles/lcp) and [Cumulative Layout Shift (CLS)](https://web.dev/articles/cls) metrics, and displays their scores (**good**, **needs improvement**, or **bad**).
134
138
135
139
The **Interaction to Next Paint (INP)** card is also displayed, initially without data.
@@ -139,6 +143,35 @@ The **Interaction to Next Paint (INP)** card is also displayed, initially withou
139
143
To get a breakdown of a metric score, hover over the metric value to see a tooltip.
140
144
141
145
146
+
To interact with a webpage to display the **Interaction to Next Paint (INP)** card:
147
+
148
+
1. Open the [Exploring the universe](https://microsoftedge.github.io/Demos/exploring-the-universe/) demo in a new window or tab.
149
+
150
+
1. Right-click the webpage and then select **Inspect** to open DevTools, and then select the **Performance** tool.
151
+
152
+
1. Set a 4x CPU slowdown and a slow 4G network throttle.
153
+
154
+
1. Right-click the **Refresh** button to the left of the Address bar, and then select **Empty cache and hard refresh**.
155
+
156
+
This ensures that the image is loaded again from the server, not from the local cache.
157
+
158
+
The **LCP** card shows that the image took a long time to load.
159
+
160
+
The engine identifies this image of stars as the largest item to be rendered.
161
+
162
+
The **CLS** card shows orange and **0.15**. This illustrates how sudden, unexpected jumps in the layout can negatively impact users. This is also due to the image taking some time to load.
163
+
164
+
The demo webpage neglects to specify a height for the image, and so the page initially loads without reserving much space for the image. When the image starts appearing, the content below it suddenly jumps down.
165
+
166
+
1. Click the accordion items in the right column.
167
+
168
+
**INP** values are displayed.
169
+
170
+
1. Click the INP values.
171
+
172
+
In the demo page, these values are designed to load slowly, so it takes a long time between clicking the value and rendering the corresponding content. It's a random value between 100ms and 1000ms, leading to a high INP metric.
173
+
174
+
142
175
<!-- ------------------------------ -->
143
176
#### Interaction to Next Paint (INP)
144
177
@@ -220,15 +253,19 @@ To add field data:
220
253
221
254
Additionally, if for some reason you can't get the field data automatically, you can select the **Always show field data for the below URL** checkbox and provide a URL. The **Performance** tool will attempt to fetch field data for this URL first and then show you this field data no matter what page you navigate to.
222
255
223
-
To change your field data fetch settings after setup, in the **Performance** tool home page, in the **Field data** section, click the **Configure** button. If the **Performance** tool home page is not shown, because the timeline is shown instead, optionally click the **Save profile** () button, and then click the **Clear** () button.
256
+
To change your field data fetch settings after setup, in the **Performance** tool home page, in the **Field data** section, click the **Configure** button. If the **Performance** tool home page is not shown, because the timeline is shown instead, to the right of the **x** (house) icon,
257
+
258
+
Or, click the **Save profile** () button, and then click the **Clear** () button.
259
+
260
+
<!-- todo: bug: tooltip not shown on house icon when on the Live -->
224
261
225
262
<!-- end expander section -->
226
263
227
264
1. Note the **Privacy disclosure**, and then click the **Ok** button.
228
265
229
266
With the field data fetch set up, the **Performance** tool now shows you a comparison between your local metric scores and those that your users experience. You can see the collection period in the **Field data** section on the right.
230
267
231
-
<!-- todo: redo showing edge -->
268
+

232
269
233
270
To get a breakdown of a metric score, hover over the metric value to see a tooltip.
0 commit comments