The Browser Result Details view contains information about check results in a number of charts, graphs and tables. This view is most useful for analyzing browser results for scenarios. The type of information displayed in the view depends on the check type. For a scenario, several aspects of the check are shown in different areas.
Result Message
The Result Message of a Browser Check contains useful summarizing information. The following message is an example of a result message:
6 steps, 6 pages, 76 urls, 32902/857026 sent/received bytes
6 steps - Obsolete data point. The number of steps will always equal the number of pages.
6 pages - Of course, pages organize Browser Check URL calls into logical functions (such as navigating to a certain page). The number of pages in the scenario can be altered using the custom command insertPageBreak.
76 urls - the number of URLs which were loaded throughout the entirety of the check.
32902/857026 sent/received bytes - the number of uncompressed bytes sent to and received by the web server throughout the duration of the scenario.
Metrics Section
The Metrics Section contains useful information regarding browser metrics.
Total browser render time is the response time from the start of the navigation until the last request is completed.
Total response time is the sum of the response time of all the objects that were loaded during the execution. Total response time is calculated serially.
Total page size is the sum of the response sizes of all loaded objects in bytes.
DOM content loaded is the time it took for the check to reach the DOM content loaded event after navigation started.
DOM complete is the time it took for the check to reach the DOM complete event after navigation started.
DNS lookup is the time the check took to perform DNS lookup for the scenario.
Click on the arrows to the left and right of the metrics to access the previous and next Check Result.
Domains
The Domains section displays a table containing the domains accessed in the check. For each, aggregated information regarding traffic volumes and percentage is shown.
Column | Description |
|---|---|
Domain | URL for the domain |
Size | Absolute traffic size and percentage of the total number of received bytes (as seen in the sent/received portion of the result message and the Metrics section) |
Time | Absolute traffic time and percentage of the time it took all pages to load |
Count | Number of urls and percentage |
Timeline | Graphical representation of the transactions. Colored bars correspond to the timings indicated in the Legend. |
10 Slowest URLs
The Slowest URLs table shows a list containing the urls with the slowest response times in the check:
Column | Description |
|---|---|
# | Order of access / order in scenario. |
Time | Response time of the URL |
In this unnamed column, you will see an icon. Hover over the icon to see the type of the URL in question. Example types include | |
Url | Accessed URL and the HTTP method used to request the URL |
Timeline | Graphical representation of the transactions. Colored bars correspond to the timings indicated in the Legend. |
Slowest URL Legend
The Slowest URL Legend window is displayed when you point at a url in the table. It explains the colors used in the diagram, reveals information about the URL timing, and displays the Server IP address for the domain which is accessed:
This information can be very valuable when diagnosing timing issues with individual URLs within a scenario. See the Legend for more information on DNS Lookup, Connection, SSL Handshake, etc.
Errors
The Errors section displays errors encountered during the scenario run for the check, if any exist. For each page that has errors, a table is shown which reveals pertinent information about each error:
Column | Description | Comment |
|---|---|---|
# | ID number for accessed page | The Jump To URL link lets you navigate to the URL in the waterfall where the error occurred. |
HTTP Code | Returned HTTP Status Code |
|
Error | Error message from the application, if any |
|
Time | Elapsed time for the step where the error occurred |
|
Url | Access HTTP Methods and URL where the error occurred | When you click a particular URL in the table, detailed information regarding the response is shown. |
Request | Outgoing request message | The Open link in the Request column allows you to try to send the request manually. |
Response | Incoming response for the request | In the above screenshot, no responses were returned and all columns contain the response “N/A”. That will not always be the case. |
MIME | MIME Type for the response |
|
Error log | Log messages for the error | In the above screenshot, no errors were logged; all columns contain the response “N/A”. That will not always be the case. |
The Jump To URL link lets you navigate to the URL in the Waterfall where the error occurred:
The Open link in the Request column allows you to try to send the request manually:
If the request can be sent, you will see data in the “Headers” section.
When you click a particular URL in the table, detailed information about the response is shown:
Error Types
There are a number of error types that can be reported for a step.
Request Timeout
If a URL in your scenario does not return a response within X seconds after the DOM complete is sent, you will see an error informing you that the URL timed out:
The number of seconds which the check will wait for request resolutions after DOM complete can be configured in the Edit Check settings:
Altering the request activity timeout can help in situations where a certain URL is simply taking a long time to return a response. However, if the URL is not returning a response at all, the URL will fail regardless of the value you enter in the Request Activity Timeout input above.
Redirect Loop
The Redirect Loop error typically indicates that the there isa circular redirection happening with the request.
Causes
The typical cause of this error is a page that redirects to another page which in turn (possibly via multiple other pages) redirects back to the original page.
Redirect loop errors can also occur when the page redirects to itself, possibly due to a programming error or misconfiguration of an
htaccessfile or the web server.Additionally, and more rarely, the error can be trigged if there is no actual loop, but there are too many HTTP redirects before a page is reached that does not also issue a redirect.
Page Timeout
A Page Timeout error happens when the total load time for a single page exceeds the threshold value.
Causes
The page timeout happens after a page has started loading, but no new events are received, and no other page has started loading.
The timeout occurs if a DOM has not been received (
page timeout while waiting for DOM Complete event).It can also occur if there is at least one response missing for one of the sent HTTP requests (
page timeout while waiting for resources).This means that the page is reachable, but for some reason takes a very long time to load, and there is no transfer to a different page.
The default threshold value is 80 seconds.
Changing the value
The Page Timeout value can be changed from the check configuration. Changing the URL Timeout will affect the Page Timeout value. The URL Timeout value is added to 40 to generate a new Page Timeout value.
URL Timeout
The URL Timeout error is triggered whenever the response time for a single URL request exceeds the threshold value.
Causes
Url timeout is setup separately for every URL to track debugger notifications it receives. If no events are received for a URL in urlTimeout seconds then it will be reported as timed out.
Setting
The default threshold value is 40 seconds. This can be configured in the advanced section of the check configuration.
Changing the value
Changing the URL Timeout (Error Types) will affect the Errors Types Page Timeout value. The URL Timeout value is added to 40 to generate a new Page Timeout value.
History Information
The History Information table shows information about the check run.
This information is available if the full browser result information is not relevant for the check type or has been purged.
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 | |
Message | Test Result Message. |
Legend
The Legend section shows explanations for the colors used in a diagram. The legend varies slightly depending on which graph or table it relates to. For example, the legend for page information:
Domains Legend
The Domains Legend window is displayed when you point at a domain url.
It shows explanations for the colors used in the diagram. It also shows the actual time for each of the categories.
Item | Description |
|---|---|
DNS Lookup | Time for DNS query and receive the response. |
Connecting | Time to establish a connection. |
Sending Request | Outgoing request message processing. |
Waiting for Response | Time it took for the target system to return the first response which is the Response Headers. |
Receiving Data | Time to complete response from the URL/method. |
Slowest URL Legend
The Slowest URL Legend window is displayed when you point at a url in the table.
Shows explanations for the colors used in the diagram. It also shows the actual time for each of the categories.
Item | Description |
|---|---|
Offset | Time until start of processing. |
DNS Lookup | Time for DNS query and receive the response. |
Connecting | Time to establish a connection. |
Sending Request | Outgoing request message processing. |
Waiting for Response | Time it took for the target system to return the first response which is the Response Headers. |
Receiving Data | Time to complete response from the URL/method. |
Waterfall Legend
The Waterfall Legend section shows explanations for the colors used in the waterfall diagram.
View
Item | Description |
|---|---|
Queued by Browser | Time spent in browser before executing DNS Lookup or or Connect. |
DNS Lookup | Time for DNS query and receive the response. |
Connecting | Time to establish a connection. |
Sending Request | Outgoing request message processing. |
Waiting for Response | Time it took for the target system to return the first response which is the Response Headers. |
Receiving Data | Time to complete response from the URL/method. |
Dom Content Loaded | DOM Content Loaded point. The render tree can be constructed: the DOM is ready and there are no stylesheets blocking JavaScript execution. This measure calculates duration between the |
Dom Complete | DOM Complete point. The resource loading and processing is complete. |
Screenshots
The Screenshots section displays screenshots captured during a scenario run, if any.
The screenshots are shown as a timeline with an indicator displaying when the image was taken.
Scroll Bar
The scroll bar shows basic information about the check and allows you to navigate between checks runs.
Scenario Check Scroll Bar
The scroll bar for a Scenario Check run shows aggregated information for all the loops and requests.
##
Item | Description |
|---|---|
| Back to previous data point / check run. |
No. Request Roundtrips | Number of full request/response cycles. |
Response Time | Response time for the entire check. |
Total Throughput | Data throughput. |
Total URL/s | Number of URLs visited per second. |
Total Loops | Number of scenario loops. |
| Forward to previous next data point / check run. |
URL Check Scroll Bar
The scroll bar for a URL Check run shows aggregated information for requests and responses.
##
Item | Description |
|---|---|
| Back to previous data point / check run. |
Response Time | Response time for the entire check. |
Sent Size | Size of request(s). |
Received Size | Size of response(s). |
| Forward to previous next data point / check run. |
Details Result Toolbar
The Toolbar is always available at the top, allowing you to perform different task relating to the check.
Scenario Toolbar
The Scenario toolbar contains basic information about the test run, and a number of buttons to access other features.
Item | Description |
|---|---|
Name of the check. | |
| Opens the Check Edit view. |
| |
| |
| |
| |
Test Started | Timestamp for when the test started. |
URL Toolbar
The URL toolbar contains basic information about the test run and a number of buttons to access other features.
Item | Description |
|---|---|
Name of the check. | |
| Opens the Check Edit view. |
| |
| |
| |
Test Started | Timestamp for when the test started. |
The URL Waterfall Section
Understanding the Waterfall Section for a Browser Check Result
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.
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. |
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, 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 from the browser. |
11 | Wait duration ms | The time it took for the target system to return the first response, 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 + content. |
13 | Response time ms | The total network response time for this URL. ( |
14 | Received bytes | The amount of uncompressed bytes received from the server. |
15 | Content mime type | MIME type of the response content. |
16 | Blocked url offset ms | The offset of the Blocked timing relative from when the URL was started (timestamp). |
17 | DNS lookup URL offset ms | The offset of the DNS Lookup timing relative from when the URL was started (timestamp). |
18 | Connect URL offset ms | The offset of the Connect timing relative from when the URL was started (timestamp). |
19 | Send URL offset ms | The offset of the Send timing relative from when the URL was started (timestamp). |
20 | Wait offset ms | The offset of the Wait timing relative from when the URL was started (timestamp). |
21 | Receive URL offset ms | 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.
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 URL offset ms | Not applicable. |
Started UTC ISO 8601 | The timestamp when the URL was initiated inside of the browser, according to ISO 8601 format. |
Understanding the Waterfall Section for a ZebraTester Check Result
The following diagram explains the different metrics which are displayed in the waterfall for a ZebraTester Check result. These metrics, of course, are also pulled from the ASM API.
Number on Diagram | Metric Name |
|---|---|
1 | URL Number |
2 | URL |
3 | Header Name (Key) |
4 | Header Value |
5 | HTTP Status Code |
6 | HTTP Method |
7 | DNS lookup duration (ms) |
8 | Connect duration (ms) |
9 | Send duration (ms) |
10 | Wait duration (ms) |
11 | Receive duration (ms) |
12 | Elapsed Time |
13 | Received Bytes |
Waterfall Legend
The Waterfall Legend section contains explanations for the colors used in the waterfall diagram.
View
Item | Description |
|---|---|
Queued by Browser | Time spent in the browser before executing DNS Lookup or Connect. |
DNS Lookup | Time for DNS query and receive the response. |
Connecting | Time to establish a connection. |
Sending Request | Outgoing request message processing. |
Waiting for Response | The time it took for the target system to return the first response which is the Response Headers. |
Receiving Data | Time to complete the response from the URL/method. |
DOM Content Loaded | DOM Content Loaded point. The render tree can be constructed: the DOM is ready and there are no stylesheets blocking JavaScript execution. This measure calculates duration between the |
DOM Complete | DOM Complete point. The DOM Complete point is when the resource loading and processing is complete. |
Expanded View
For each row in the waterfall table, further details are available. To expand the row for a page:
Click the expand button
Messages
When available, headers for the request and response are shown:
Waterfall History
You can compare the recent check result for a transaction with the History of Previous Results list of recent results.
Websockets
When the check records Websockets, you can get a detailed view of the recorded data by expanding the relevant result Waterfall row.
The WebSockets frame shows all recorded events for the selected URL.
When WebSocket recording data is available, this is indicated by a button in the waterfall row:
View WebSocket recording
For each row in the waterfall table, further details are available.
To expand the row for a page:
Click the expand button
The WebSocket recording is shown next to the result history:
