After you create a website speed test task in ARMS Synthetic Monitoring, the dashboard aggregates availability, page load timing, and error data collected from monitoring points across cities and carriers. Use the dashboard to identify availability drops, compare regional performance, and pinpoint slow-loading pages.
Open the dashboard
-
Log on to the ARMS console.
-
In the left-side navigation pane, choose Synthetic Monitoring > Scheduled Tests. On the Synthetic Tasks page, click the name of the task.
On the Synthetic Tasks page, click the name of the task.
Summary metrics
The top of the dashboard displays the following aggregate metrics for the task.
| Metric | Description |
|---|---|
| Availability | Percentage of successful monitoring actions. Availability = number of successful monitoring actions / total number of monitoring actions x 100%. A monitoring action is successful only if it meets the conditions defined in Availability Assertion. |
| First package time | Time from the beginning of page browsing to the first packet received. First package time = blocking time + DNS time + TCP time + (SSL) time + request time + response time + (3XX jump time). |
| First screen usage | Time from URL input to the moment the rendered area reaches the specified height. The default height threshold is 600 pixels. |
| Full page load time | Time from the beginning of page browsing to the last packet received. |
| Number of tests | The number of synthetic tests in the task. |
| Number of errors | Total failed synthetic tests within the selected time range. A test execution fails if it does not meet the conditions defined in Availability Assertion. |
City-based test overview
Performance metrics broken down by city for cross-region comparison.
| Metric | Description |
|---|---|
| Availability | Success rate for the city. |
| First package time | Average time to receive the first packet in the city. |
| First screen usage | Average time to load the first screen in the city. |
| DOM Ready time | Time from HTML document load to a fully parsed DOM that can run JavaScript. A shorter DOM Ready time means faster page initialization and quicker user interaction. |
| DOM Complete time | Time from HTML document load to full rendering of all resources, including images, stylesheets, and scripts. A shorter DOM Complete time means the complete page is visible and interactive sooner. |
| Fully loaded | Time for the browser to load the page and all directly referenced resources such as images and stylesheets, excluding asynchronous and lazy-loading resources. |
| Overall time | Time to load all page resources, including asynchronous and lazy-loading resources. |
| Number of tests | Total number of synthetic tests initiated from the city. |
Availability trends
The trend charts plot the following metrics over the selected time range:
Availability: Success rate over time.
First package time: Time from page browsing to the first packet received from the server.
White screen time (First Paint): Time from the page request to the first visible content rendered by the browser. A shorter value means initial content appears sooner.
First screen usage: Time from the URL request to the rendered area reaching the specified height threshold.
DOM Ready time: Time until the DOM is fully parsed and JavaScript can run.
DOM Complete time: Time until all resources are loaded and the page is fully rendered.
Fully loaded: Time to load the page and all directly referenced resources, excluding asynchronous and lazy-loading resources.
Overall time: Time to load all resources, including asynchronous and lazy-loading resources.
Trend charts by city and carrier
Per-city and per-carrier trend charts for the following metrics:
| Chart | Description |
|---|---|
| Full page load time (city) | Full page load time trend for each city. |
| Full page load time (carrier) | Full page load time trend for each carrier. |
| First package time (city) | First package time trend for each city. |
| First package time (operator) | First package time trend for each operator. |
| First screen usage (city) | First screen usage trend for each city. |
| First screen usage (operator) | First screen usage trend for each operator. |
Top 5 rankings
The dashboard highlights the worst-performing dimensions to help you prioritize investigation:
| Chart | Description |
|---|---|
| Slowest cities (top 5) | Five cities with the longest full page load time. |
| Slowest operators (top 5) | Five operators with the longest full page load time. |
| Error types (top 5) | Five most common error types in test responses. |
Task analysis
Task analysis provides custom filtering and aggregation across all test execution data. Use it to drill down beyond the predefined dashboard views by combining filter conditions and aggregate dimensions for real-time analysis.
For details, see Task analysis.