RUM Metric Detail


On this page

Each performance metric has a dedicated report, allowing you to deep-dive into trends and segment by various dimensions.

Largest Contentful Paint, segmented by subparts shows what contributes to LCP.

Largest Contentful Paint, segmented by subparts shows what contributes to LCP.

View metric subparts#

Subparts are available for Largest Contentful Paint, Interaction to Next Paint, and Time to First Byte:

MetricSubparts
Largest Contentful PaintTime to First Byte, Image load delay, Image load duration, Render delay
Interaction to Next PaintInput delay, Processing duration, Input presentation delay
Time to First ByteWaiting, Cache, DNS, Connection, Request

To help you identify areas to pay attention to, the metric measurements and the subparts have badges that indicate changes in the metric relative to the previous time period (for example, Time To First Byte is 876 ms, which is +67 ms compared to the previous period).

Check how close measurements are to their thresholds#

Each metric chart can have dashed lines that show good, to-improve, and poor measurement thresholds. Thresholds help you visualise how a metric is performing, and is useful for goal setting, such as getting back to "good" on LCP or keeping INP under "poor". See Core Web Vitals thresholds for the values.

Segment by deployment#

If you track deployments, Metric reports can be segmented by your recent deploys, so a change in a metric can be attributed to the release that caused it.

The LCP by Deployment panel in RUM, listing five releases with their revision, sample count, percentage change and LCP value, the most recent marked Collecting.

Each release, with the measurements collected since it shipped and the change it made.

Each row lists:

  • Deployment: how long ago the release happened and its revision, linking out to the commit.
  • Samples: how many measurements were collected since. A release still gathering data is marked Collecting.
  • Change: the percentage change against the previous release.

The same segment is available on Synthetic metric pages, so releases are visible in both data sources.

Deploys can be created with the CLI or API, or automatically each time your production branch deploys, by connecting a GitHub repository.

Filter metric data#

The Metric reports can be filtered in two ways:

  • Choosing an option within the filter bar at the top of the page. See Filtering RUM reports for every option.
  • Clicking on any of the top five items within the predefined dashboard sections (including attribution targets, top paths, top pages by grouping, top devices, top browsers, top navigation type, and top countries).