Performance glossaryReal-browser monitoring is synthetic testing that loads a site in actual browsers on a schedule to check that pages and key journeys work and load quickly.
Real-browser monitoring (RBM) is a form of synthetic monitoring: a service loads a website in a real browser engine, such as Chrome, on a schedule and from several locations, and records what happens. A basic uptime check only asks whether the server returned a response. A real browser downloads and runs everything the page needs, including CSS, JavaScript, fonts, and third-party scripts, just as a visitor's browser would.
The name is easily confused with real user monitoring (RUM). RBM uses real browsers driven by scripts; RUM collects data from real people visiting the site. They answer different questions, and many sites use both.
What it checks
- Availability of the full page, not just the server. A page can return a 200 status and still be blank because a script failed.
- Load timing, such as Time to First Byte, Largest Contentful Paint, and full load time, often with a waterfall chart of every request.
- Content: whether expected text or elements appear, which catches pages that load but show an error.
- JavaScript errors and failing third-party resources.
- User journeys: scripted steps such as logging in, searching, adding to cart, and starting checkout.
Most services capture screenshots or video when a check fails, which makes intermittent problems much easier to diagnose.
Real-browser monitoring vs real user monitoring
| Real-browser monitoring | Real user monitoring | |
|---|---|---|
| Who loads the page | Scripted browsers | Actual visitors |
| When | On a schedule, even with no traffic | Only when people visit |
| Conditions | Controlled and repeatable | Every real device and network |
| Best for | Alerts, baselines, and catching breakage before visitors do | Knowing what visitors actually experience, including Core Web Vitals |
Using it on a WordPress or WooCommerce site
For most sites, a handful of checks covers the main risks: the home page, a key landing page, and, for a store, the path from product page to checkout. Running them every few minutes from the regions where customers are means a broken payment script, a failing third-party embed, or a plugin update that breaks the cart triggers an alert rather than costing orders.
A few practical points:
- Stop scripted checkout journeys before payment, or use test products and coupons, so they do not create real orders.
- Exclude monitoring traffic from analytics.
- Compare results before and after deployments and plugin updates to see whether performance changed.
RBM sits alongside website monitoring for uptime and application performance monitoring for what happens on the server.