...
The following diagram explains the different metrics which are displayed in the waterfall for a Browser Check result. These metrics are pulled from the ASM API. If you hover over a URL in the waterfall, detailed information about the URL is shown:
...
Metric Name
Description
Started
Timestamp of when the URL was initiated.
Elapsed ms
The complete time in milliseconds that the URL took inside of the Browser. Includes both Blocked (aka Queued By Browser) time and network processing time.
Sent bytes
The amount of bytes sent to the server.
Error code
Internal error code.
Error message
Internal error message (if applicable).
Complete
Was the URL (request + response) completed? 1=True, 0=False.
Redirect
Was the response from the server a redirect? 1=True, 0=False.
Redirect URL
If the URL was a redirect, what URL was the original URL redirected to?
HTTP result
The result of the HTTP call.
Content from cache
Was the response content retrieved from the Client Browser Cache? 1=True, 0=False.
Content size bytes
Response Content size in bytes, excluding headers.
Request cookie count
Number of request cookies sent to the server.
Request header count
Number of request headers sent to the server.
Response cookie count
Number of response cookies received back from the server.
Response header count
Number of response headers received back from the server.
Response status line
A text with the response status.
TTFB duration ms
Time-to-first-byte, the timing that indicates how long it took to receive the first byte from the server. (TTFB = DNS Lookup + Connect + Send + Wait
).
TTFB URL offset ms
Not applicable.
Started UTC ISO 8601
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 e.g (200, 302, 500, etc.) |
6 | URL Offset ms | The time Offset 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, e.g a DNS or Connect is fired. |
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 away request from the browser. |
11 | Wait duration ms | The time it took for the target system to return the first response (that is, which 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 amount number of uncompressed bytes received from the server. |
15 | Content mime type | MIME type of the response content . |
16 | Blocked url offset ms | The A timestamp indicating the offset of the Blocked timing relative from when the URL was started (timestamp). |
17 | DNS lookup URL offset ms | The A timestamp indicating the offset of the DNS Lookup timing relative from when the URL was started (timestamp). |
18 | Connect URL offset ms | The A timestamp indicating the offset of the Connect timing relative from when the URL was started (timestamp). |
19 | Send URL offset ms | The A timestamp indicating the offset of the Send timing relative from when the URL was started (timestamp). |
20 | Wait offset ms | The A timestamp indicating the offset of the Wait timing relative from when the URL was started (timestamp). |
21 | Receive URL offset ms | The A timestamp indicating the offset of the Receive timing relative from when the URL was started (timestamp). |
22 | Step duration ms | What the current Step duration is on this url to retrieve the final Step duration, find the MAX(Step Duration ms) among all URLs in this Step. |
The following metrics are also pulled from the ASM API for Browser checks, but they are NOT displayed on the waterfall. They are used to present more information on each URL.
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:
|
Legend
The Legend section at the bottom of a Browser Check Result page displays the color coding which is used to identify different URL operations for each URL in the result. Hover over the “question mark” icons to learn more about how ASM defines DOM Interactive, DOM Content Loaded, and DOM Complete:
...
History Information
The History Information table shows information about the check run. If the check has been purged, only the most basic information regarding the check run will be available:
...
Item | Description |
---|---|
Severity | Check status Severity |
Time | The timestamp for the check run |
Elapsed (ms) | Duration of the test |
Attempts | The number of connection attempts |
Result Code | Returned HTTP Status Code |
Message | If a result message is available (for example, a failure message), it will be displayed here |
Legend
The Legend section at the bottom of a Browser Check Result page displays the color coding which is used to identify different URL operations for each URL in the result. Hover over the “question mark” icons to learn more about how ASM defines DOM Interactive, DOM Content Loaded, and DOM Complete:
...
Domains Legend
The Domains Legend window is displayed when you point at a domain url.
...