Real user performance
Compare LCP, FID, CLS, TTFB, page load, geography, browser, device, and route across actual user traffic.
Measure real browser performance, find the affected session, replay the sequence of actions, and follow the frontend request into the responsible backend trace without losing time or user context.

RUM is most useful when a slow page, failed action, or frontend error can continue into the same investigation as the API request.
Inspect the ordered navigation, click, request, error, and long-task sequence for an affected browser session.
Reproduce the visual journey around a failure while keeping the event timeline available for verification.
workflow
The investigation starts with the population, narrows to one journey, and ends on the responsible request.
Use Web Vitals, errors, page views, routes, devices, and geography to isolate the population.
Choose a session that matches the timing, browser, version, route, and failure pattern.
See what the user did before the error and which browser request or action changed the experience.
Carry the time and request context into the service dependency and failing span.
proof / shipped
The product includes overview, performance, errors, resources, explorer, session lists, session detail, action timelines, and replay.
Measure real browser performance, find the affected session, replay the sequence of actions, and follow the frontend request into the responsible backend trace without losing time or user context.