Skip to main content

Real User Page Speed Monitoring

Real user monitoring (RUM) allows you to collect data on how real users experience your website. DebugBear measures Core Web Vitals metrics and provides additional data to optimize them.

RUM data stands in contrast to lab data which is collected by loading a page in controlled test environment.

This article explains how you can use real user data in DebugBear. Learn about setup and configuration here.

Real user Monitoring Demo Video

Watch this video to learn more about how to work with the Core Web Vitals data in DebugBear RUM.

The Trends tab provides a high-level view of your website performance and how it has changed over time.

DebugBear collects data for these metrics:

RUM trends tab

View individual user experiences

The Experiences tab shows you how specific visitors have experiences your website. This detailed data can help you replicate page speed issues and identify ways that a specific user experience could have been faster.

RUM experiences tab

Metric-specific tabs

DebugBear also offers specific tabs to help you track and optimize the 6 performance metrics mentioned above.

Even on a slow website some users will have a fast experience. Some pages will be fast and some pages will be slow. The top of this tab shows a histogram that breaks down the total number intro groups of fast experiences, ok experiences, and slow experiences.

We also show percentile trends. Changes that you make on your website may not improve the average experience, but the 10% of users with the slowest connection may still benefit. This is measured by the p90 (90th percentile) line.

High-level summary of metric

Next the report shows how fast the pages with the most traffic are. If you are looking for places to improve your website you can also choose to view the slowest pages on your site.

You can click on each of the bars in the charts to view data for just that specific page

Slowest pages selected via dropdown

Finally a map shows how page speed varies across the world.

Global page speed map

Page element breakdown

For metrics that are related to a specific page element we also provide a breakdown of what this page element is. This applies to the LCP, CLS, INP, and FID metrics.

For example, for the LCP metric you can see what piece of content is the largest content element. This can vary on the devices size and initial scroll position when opening the page.

LCP Element breakdown

For Interaction to Next Paint and First Input Delay the element that the user clicked on or otherwise interacted with will be shown. When investigating CLS the element that moved around on the page is indicated.

Filtering RUM data

At the top of the report pages you can select whether you want to see all data or only Desktop/Mobile data.

You can also click on Edit Filters to define what pages and visits you want to see data on.

DebugBear RUM filters