Test the speed of a website - Application Real-Time Monitoring Service

Synthetic Monitoring allows you to actively and comprehensively monitor the network status, performance, and user experience of your online services. This topic describes how to create a synthetic monitoring task to test website speed.

Log on to the ARMS console.
In the left-side navigation pane, choose Synthetic Monitoring > Scheduled Tests. On the Synthetic Tasks page, click New Task.
On the Create Synthetic Task page, click Website Speed.

In the STEP1 section, configure the parameters that are described in the following table.

Parameter	Description
Task name	The name of the synthetic monitoring task.
Target Address	The address of the web application on which you want to perform synthetic monitoring. You can enter a URL that starts with `http` or `https`, or an address in the `IP address:Port number` format.
Dialing Frequency	Frequency: the intervals at which the synthetic monitoring task runs. Custom: If you turn on the Custom switch, you can select the time periods during which the synthetic monitoring task is performed.

Select detection points in the STEP2 section.

Parameter	Description
Monitoring point type	Valid values: PC End and Mobile End.
Monitoring Point Group	Recommended Monitoring Point Group: The group contains the common detection points recommend by the system. All Monitoring Point Group: The group contains all detection points supported by Synthetic Monitoring. Custom Monitoring Point Group: The group contains the frequently used detection points. Note You cannot monitor IPv6 web applications in data centers.
Select Monitoring Point	Add the carriers that you want to monitor to the Selected Monitoring Point section on the right. Note You can save the carriers added in the Selected Monitoring Point section to a custom detection point group. This way, you can quickly select detection points when you create a synthetic monitoring task.

In the STEP3 section, configure the advanced settings. The following table describes the parameters.

Parameter	Description
IP Protocol	The IP protocol is used by the servers that access the website. Valid values: Automation: randomly tests the performance of IPv4 or IPv6 servers. IPv4: tests the performance of IPv4 servers. IPv6: tests the performance of IPv6 servers.
Monitoring Related Items	The monitoring settings of the task. Valid values: Disable Cache: If you select this value, the browser history is cleared, the temporary files, historical records, cookies, and saved passwords and HTML forms are deleted, and cached resources cannot be loaded during the page loading process. Redirect: If you select this value, the page to which visitors are redirected from the specified page for monitoring is also monitored. If you deselect this value, the redirected page is not monitored. Instead, the `651 error code` is returned, which indicates that redirection occurred on the page. Disable Compression: If you select this value, files in the compression format are not received during monitoring. Auto Scroll: If you select this value, mouse operations are simulated on the monitored page and the page is automatically scrolled to the end of the scroll bar. Ignore Certificate Errors: If you select this value, certificate errors during certificate verification in the SSL handshake process are ignored and browsing can be continued. If you want to monitor certificate errors during certificate verification in the SSL handshake process, deselect this value.
Monitoring Timeout	The maximum execution duration of the task. If the specified value is exceeded, a timeout error is reported. Default value: 40000. Unit: milliseconds.
Maximum Wait Time	The interval at which ARMS checks the status of the browser. Default value: 40000. Unit: milliseconds.
Slow Element Threshold	The time threshold that is used to define a slow element. Default value: 5000. Unit: milliseconds. If the total time consumed to download an element exceeds 5,000 milliseconds, the element is defined as a slow element.
Custom Header	Specifies whether to add or modify specific field values in the request header. If you turn on this switch, you can select one of the following values: Modify Global Packet: modifies the headers of all packets. Modify First Packet: modifies the header of the first request packet in the browse task.
Customize host	The custom host mode. You can select Polling or Random and then enter the IP addresses of a custom host in the field. You can enter multiple IP addresses. Separate the IP addresses with commas (\|). Example: `192.168.1.11,192.168.1.12:www.a.domain`. Note If a colon (:) is used, a URL before the colon (:) is automatically resolved.
Hijack Parameters - DNS Hijack Whitelist	If the IP address or CNAME record resolved from a domain name, such as www.aliyun.com, is not included in the DNS whitelist, you cannot access the domain name, or an IP address that belongs to a different domain name is returned. If the IP address or CNAME record is included in the DNS whitelist, DNS hijacking does not occur. Format: `<domain name>:<matching rule>`. The matching rule can be an exact IP address, wildcard, subnet mask, or CNAME record. Separate multiple matching rules with vertical bars (\|). Example: `www.aiyun.com:202.0.3.55\|203.3.44.67`. It indicates that all IP addresses resolved from the www.alliyun.com domain name, except for 202.0.3.55 and 203.3.44.67, are hijacked.
Hijack Parameters - Page Tampering	If elements that are not included in the whitelist appear on the monitored page, the page is tampered with. These elements can be pop-up ads, floating ads, and page redirection. Format: `<domain name>:<element name>`. You can specify the elements in the form of wildcards. Separate multiple elements with vertical bars (\|). Example: `www.aliyun.com:\|/cc/bb/a.gif\|/vv/bb/cc.jpg`. It indicates that if elements other than basic documents, /cc/bb/a.gif, and /vv/bb/cc.jpg appear on www.aliyun.com, the website page is tampered with.
Hijack Parameters - Traffic Hijacking	The classification statistics for the HTTP status code 302 on the browsed page. Important You must check the elements for which the HTTP status code 302 is returned on the page. In most cases, the synthetic monitoring task monitors the status of the basic documents after the HTTP status code is returned. Identify Elements: the total number of elements on the page. Hijack Identification: the keyword that is used to identify hijacking. Asterisks (*) are allowed.
Verify String Blacklist	An arbitrary string in the source code of the page for verification. If the source code returned by the client contains a string that is in the blacklist, the `650 error code` is returned, which indicates that the string fails to be verified. Separate multiple strings with vertical bars (\|).
Verify String Whitelist	An arbitrary string in the source code of the page for verification. If the source code returned by the client contains a string that is not in the whitelist, the `650 error code` is returned, which indicates that the string fails to be verified. Separate multiple strings with vertical bars (\|).
Element Blacklist	The elements that are not loaded in the page loading process. Important Do not add basic documents to the element blacklist.
Availability Assertion	The conditions that are used to determine whether monitoring is available. The monitoring is available only if the response to the monitoring points of the synthetic monitoring task meets all specified conditions.
Resource Group	The resource group to which the task belongs. For information about how to create a resource group, see Create a resource group.

Click Create Task.
After you create a task, you are redirected to the Synthetic Tasks page.