The 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. For example, a Scenario Check could have several areas dealing with different aspects of the scenario:

Depending on the type of check, different areas may be available in the view.

Access & Bookmarks

In most cases you can access the Details view by clicking a check wherever it is presented. Depending on the view you are in, the exact method to access the details varies. Whenever you access check Check Details, a bookmark is placed at the top of the window. The results bookmark shows the check url / name:

A similar bookmark is created for Result Details. The results bookmark shows the timestamp:

This allows you to keep a number of checks in the bookmarks bar and move between them by clicking the respective bookmark.

Clicking a bookmark will take you to the appropriate Check Details or Result Details detail view.

Domains

The Domains section displays a table containing the domains accessed in the check. For each, aggregated information about traffic volumes and percentages is shown.

Column	Description
Domain	URL for the domain.
Size	Absolute traffic size and percentage.
Time	Absolute traffic time and percentage.
Count	Number of urls and percentage.
Timeline	Graphical representation of the transactions.

Elapsed Time

The Elapsed Time Per Page section shows the distribution of response times for the pages in a scenario .

View

Column	Description
Step	Name of scenario step.
Avg. Time	Average response time in the step.
Percentage	Time percentage for the step.

Errors

The Errors section displays errors encountered during the scenario run for the check, if any. For each page that has errors, a table is shown which contains information about the errors.

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 Codes, if any.
Error	Error message from the application.
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 about 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.
MIME	MIME Type for the response.
Error log	Log messages for the error.

Jump To URL

The Jump To URL link lets you navigate to the URL in the Waterfall where the error occurred.

Request

The Open link in the Request column allows you to try to send the request manually.

URL

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.

Job Timeout

A job timeout error means that the scenario step running time has exceeded the allowed time.
Causes
- The job timeout error can mean that a single scenario step runs for too long, due to a coding problem, or some other reason.
- There can also be connection issues or very slow - or none at all - responses from the target server.
The default job timeout is 180 seconds.

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 htaccess file 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	HTTP Status Codes.
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 `EventStart` and `EventEnd` timestamps, to allow for JavaScript frameworks waiting DOM Content Loaded before starting execution.
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.

Slowest URLs

The Slowest URLs table shows a list containing the urls with the slowest response times in the check. The information displayed in the table depends on the check type. For example, a scenario check:

Column	Description
	Order of access / order in scenario.
Time	Response time.
Type	Method of access.
Url	Accessed URL.
Timeline	Graphical representation of the transactions. In order to view the legend for the timeline, point the cursor at the url in the table. A tooltip with the legend is displayed.

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.

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.
	Check Details.
	Analyze Metrics.
	Locations Locations.
	Introduction to Apica Check Types.
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.
	Check Details.
	Analyze Metrics.
	Locations Locations.
	Intro Types Check Types.
Test Started	Timestamp for when the test started.

The URL Waterfall Section

The Waterfall section displays a Waterfall Diagram table containing transactions URLs, showing durations for various parts of the transaction process.

Column	Description
	Order of transaction.
Code	HTTP response code.
Method/URL	URL or service method accessed.
Time	Response time.
Size	Size of transaction.
Type	Type of transaction.
Waterfall	Graphical representation of the transaction.

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 `EventStart` and `EventEnd` timestamps, to allow for JavaScript frameworks waiting DOM Content Loaded before starting execution.
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:

Understanding the "Result Details" View

Access & Bookmarks

Domains

Elapsed Time

View

Errors

Jump To URL

Request

URL

Error Types

Job Timeout

Redirect Loop

Page Timeout

URL Timeout

History Information

Legend

Domains Legend

Slowest URL Legend

Waterfall Legend

View

Screenshots

Scroll Bar

Scenario Check Scroll Bar

URL Check Scroll Bar

Slowest URLs

Slowest URL Legend

Details Result Toolbar

Scenario Toolbar

URL Toolbar

The URL Waterfall Section

Waterfall Legend

View

Expanded View

Waterfall History

Websockets

View WebSocket recording