Browser monitoring (real browser)

Browser monitoring loads your page in a real browser (Chromium) exactly as a visitor sees it, including running JavaScript. It catches problems that a plain HTTP check cannot see: the page returns 200, but because of an error in the script the content does not render at all.

When to use it

• SPAs and sites that rely on JavaScript (React, Vue, Angular), where the HTML alone is not enough.
• Pages where the key content is filled in only after loading (dashboards, e-shops, booking systems).
• When you want to be sure the page actually renders, not just that the server responds.

How to create a browser monitor

1. In New monitor, choose the Browser type.
2. Enter the URL of the page you want to track.
3. Save. On each check we open the page in Chromium, wait for it to render, and evaluate the result. From the run we also save a screenshot, which you will find on the monitor detail.

Availability and interval

• Browser monitoring is part of the Business plan (and the trial).
• Since running a whole browser is more demanding than an HTTP request, the shortest interval is 30 minutes. For faster availability checks, use a regular HTTP monitor alongside it.

Difference from visual regression

Both use a real browser, but they address different things:

• A browser monitor answers the question "does the page load correctly?" - it tracks availability and rendering.
• Visual regression compares screenshots over time and alerts you when the appearance of the page changes unexpectedly.