...
Clicking on the dropdown caret to the right of the URL will reveal information about the size and load time of past URL runs, as well as Request and Response header information if “store Request/Response Headers” is enabled in the Edit Check settings:
...
Page Breaks in a Browser Check Result
Page breaks fulfill the need to separate different pages, typically consisting of multiple URL calls, from each other. They are used to organize the set of HTML pages into a single group before the next logical page navigation.
Page breaks are inserted into a browser check result whenever a new page load is triggered during a user journey. Specifically, a new page load is triggered when the “Open” command, the “insertPageBreak” command, and any of the “…andWait” commands (e.g. clickAndWait) are used.
Page breaks are automatically generated and inserted by default. However, there is an option to disable automatic page breaks in the Edit Check section. Page breaks can also be entered manually into scripts via use of the insertPageBreak scenario command
Waterfall Metrics
...
Number on Diagram | Metric Name | Description |
|---|---|---|
1 | Step Nr | The Step (sometimes Page) number |
2 | URL number | The identifier of a URL inside of a Step. This is a counter that is unique per Step and corresponds to a URL inside of the Step |
3 | URL | The complete URL including protocol, hostname, path and query parameters |
4 | HTTP method | The HTTP method used (e.g. GET, POST, PUT) |
5 | HTTP status code | The returned status code from the server (200, 302, 500, etc.) |
6 | URL Offset ms | The time offset in milliseconds from when the URL was initiated by the browser relative to the first URL on the Step |
7 | Blocked duration ms | The time the URL is blocked (aka Queued By Browser) inside of the browser before it is executed |
8 | DNS lookup duration ms | The time it took to perform a DNS lookup/query and receive the result back |
9 | Connect duration ms | The time it took to establish a connection to the target system |
10 | Send duration ms | The time it took to send the request from the browser |
11 | Wait duration ms | The time it took for the target system to return the first response (that is, the Response Headers) |
12 | Receive duration ms | The time it took for the complete response to be returned from the target system, including headers and content |
13 | Response time ms | The total network response time for this URL ( |
14 | Received bytes | The number of uncompressed bytes received from the server |
15 | Content mime type | MIME type of the response content |
16 | Blocked url offset ms | A timestamp indicating the offset of the Blocked timing relative from when the URL was started |
17 | DNS lookup URL offset ms | A timestamp indicating the offset of the DNS Lookup timing relative from when the URL was started |
18 | Connect URL offset ms | A timestamp indicating the offset of the Connect timing relative from when the URL was started |
19 | Send URL offset ms | A timestamp indicating the offset of the Send timing relative from when the URL was started |
20 | Wait offset ms | A timestamp indicating the offset of the Wait timing relative from when the URL was started |
21 | Receive URL offset ms | A timestamp indicating the offset of the Receive timing relative from when the URL was started |
22 | Step duration ms | The total amount of time it took all URLs on the page to finish loading. In the following example, the “Step duration” of the page is 6,030ms:  As you can see here, the final URL in the waterfall for this page finished loading between 6 and 7 seconds, roughly matching the 6,030ms reported as the “Step duration”:  For further confirmation, if you hover over the final URL and add the metrics together, you will find the sum of the metrics equals the Step duration: 
|
...