MetricRaven

Performance

What is real user monitoring (RUM)?

Real user monitoring (RUM) measures how your site performs for actual visitors, from their own browsers, devices and networks. It produces field data, as opposed to lab data from a test tool that loads the page once under fixed conditions.

Updated

What real user monitoring is

A RUM script runs in each visitor's browser. While the page loads and is used, it reads the browser's performance APIs and sends the results to a server: how long the main content took to show, how quickly clicks were answered, how much the layout moved. Aggregated over thousands of visits, that tells you how the site really performs for the people using it.

Google uses the same idea for the Core Web Vitals. Its own field dataset, the Chrome UX Report (CrUX), is collected from real Chrome users. Google's documentation says field data and RUM data are the same thing under two names.

Lab data vs field data

Lab dataField data (RUM)
Where it comes fromA test tool such as LighthouseYour real visitors' browsers
Devices and networksOne preset device and connectionEvery device and network your visitors use
Good forDebugging and testing a change before releaseKnowing what visitors actually experience
InteractionsNone, so no INP; TBT stands inReal clicks and taps, so INP is measured
Lab-only metricsSpeed Index, TBTNot available

The two often disagree. A page can score well in Lighthouse on a fast laptop and still fail at the 75th percentile because a third of its visitors use mid-range phones on mobile networks. Use lab data to find the cause and field data to judge the result.

How to set up real user monitoring

  • Add a RUM script or Google's open-source web-vitals library to every page and send the values to your analytics.
  • Report percentiles, not averages. Google judges LCP, INP and CLS at the 75th percentile.
  • Split by page, device and country. A site-wide number hides the slow checkout page on phones.
  • Join it to outcomes. Speed matters when it changes what visitors do, so compare it with bounce rate and conversion rate on the same pages.

Common RUM mistakes

  • Relying on CrUX alone. Pages need enough Chrome traffic to appear in it, so small sites and new pages are often missing.
  • Comparing RUM with a lab score. They measure different visits; a gap between them is normal.
  • Sampling only fast pages. If the script loads late or is blocked, the slowest loads go missing and the numbers look better than they are.

How MetricRaven does real user monitoring

MetricRaven's Page speed feature is RUM for the web vitals. When you turn it on (it's off by default, on every plan), the tracker loads a small add-on built on Google's web-vitals library and sends one snapshot per page load with LCP, INP, CLS, FCP and TTFB from the real visitor. Pages and entry pages show LCP and INP at the 75th percentile next to each page's purchase rate, with the rest on hover. Traffic → Pages → Details, the API, CLI and MCP server also list pages where visitors with slow loads paid less often than visitors with fast ones.

It isn't an application performance monitoring tool: there are no server traces or backend timings. Two related browser features are available. JavaScript errors records errors your scripts throw and how many of those visitors didn't pay, and session replay (Growth plan) records chosen pages. Serving the tracker through your own domain helps the add-on avoid ad blockers. See Page speed vs conversion.

Questions

What is the difference between RUM and synthetic monitoring?
RUM measures real visitors on their own devices and networks. Synthetic (lab) monitoring loads your pages from a test tool on a schedule or on demand, under fixed conditions. Synthetic catches regressions before users do; RUM shows what users actually got.
Is field data the same as RUM data?
Yes. Google's web.dev documentation says field data is also commonly known as real user monitoring data, and treats the terms as interchangeable.
Why does my RUM data differ from Lighthouse?
Lighthouse tests one load on one simulated device and network. RUM covers every visitor, including slow phones and networks, and is usually read at the 75th percentile, so it is often worse.
Does RUM slow down my site?
A well-built script is small and sends its data when the visitor leaves or hides the page. MetricRaven's web vitals add-on is about 3 KB compressed and only loads when Page speed is on.
Full glossary

Measure speed from the visitors who pay

MetricRaven's Page speed records Core Web Vitals from real visitors and shows them next to each page's purchase rate.

14-day free trial, no card required.