In short, the UserView and BrowserView platforms load web pages in real browsers and execute all page components. Monitoring via HTTP(S) uses emulated, synthetic browsers, and only downloading page elements that are requested without rendering.
How to make a choice
One way to check which type of monitoring is most appropriate is to decide if you want to make sure a web page is available for an end user or to check if its content is rendered properly.
If the URL availability is under question, select the HTTP(S) task.
Due to these differences in HTTP(S) Task and tasks of BrowserView and UserView platforms, there is also a difference in the response time measured by each task type.
See below for an example of the differences:
Because a UserView monitoring script emulates the action of a real browser it will perform the following steps: load the page, find the edit field, and input “1”; the final action is a keyword validation that the “Username too short” string is displayed in the HTML:
HTTP(S) monitoring performs this task differently. It emulates low level HTTP(S) requests. For example, if the previous UserView monitoring example is converted to a HTTP(S) monitoring process, the monitoring is conducted as two HTTP tasks with GET requests: