Skip to main content

Overview

The Web RUM Insights dashboard summarizes real-user data for your application by session, performance, resource, and error. It works out of the box. The Insights dashboard includes four main analysis dimensions:

Overview

Key metrics at a glance

Performance Analysis

Comprehensive application experience monitoring

Error Analysis

Quick error identification and diagnosis

Resource Analysis

Fine-grained resource optimization
Besides these four built-in dimensions, the Insights tab bar can also hold custom dashboards: your own boards built from the Explorer’s analytics questions, see Custom dashboards.

Overview

RUM Insights Overview

RUM Insights - Overview

The Overview module focuses on core metrics across multiple dimensions:

Performance analysis

RUM Performance Analysis

RUM Insights - Performance Analysis

The Performance Analysis module focuses on full-chain monitoring of application loading and interaction experience:
  • Page Performance: Monitor trends and sample distribution of page metrics like FCP, LCP, INP, and CLS
  • Long Tasks: Tasks that run on the main thread for more than 50 milliseconds. Shows the share of pages with long tasks and the P75 long-task duration
  • XHR and Fetch Requests: Analyze API loading performance to identify slow endpoints
  • Static Resources: Analyze static resource loading times to identify performance bottlenecks during application loading
For more information about the displayed data, see Data Collection.

Error analysis

RUM Error Analysis

RUM Insights - Error Analysis

The Error Analysis module provides comprehensive error monitoring and diagnosis capabilities:
  • Page Error Rate: Pages with the most errors, helping you prioritize which pages need attention
  • Top Issues: Issues affecting the most users, see Error Grouping for details
  • Code Errors: Categorized display of error types, see Error Tracking for details
  • API and Resource Errors: Monitor which APIs and static resources generate the most errors

Resource analysis

RUM Resource Analysis

RUM Insights - Resource Analysis

The Resource Analysis module helps you identify resources that have the greatest impact on your application:
  • Resource Ranking: Monitor the most frequently loaded and heaviest resources to identify optimization priorities
  • Resource Loading Timeline: Monitor resource timing trends (DNS resolution, TCP connection, loading time)
  • XHR and Fetch Requests: Distinguish distribution trends of different request types, methods, and error status codes
  • Third-party Resources: Resources where the host address doesn’t match the current page host are identified as third-party resources

Traffic distribution

The Traffic Distribution module helps you analyze the request distribution between self-hosted and third-party resources, identifying the impact of external dependencies on application performance. This module contains three parts:
Click the fullscreen button in the resource list to see more detail. Sort the list to find the domains with the longest duration or the most requests.

FAQ

This may occur due to:
  1. Connection Reuse (Keep-Alive): When resource requests use keep-alive to maintain connections, DNS lookups and TCP connection processes only occur on the first request, with subsequent requests reusing the same connection
  2. Cross-origin Resources: If resources are loaded cross-origin without the appropriate headers configured, the browser cannot collect complete performance data (primary cause)
  3. Browser Compatibility: In rare cases, some browsers may not support the Performance API
  1. Cross-origin Resources: If resources are loaded cross-origin without cross-origin access permissions set, the browser cannot obtain resource status information
  2. Browser Compatibility: Some browsers may not support the Performance API (rare)
1. Collect timing data for cross-origin resourcesAdd the following to the HTTP response headers of cross-origin resources:
See MDN documentation Resource Timing API.2. Collect status codes for cross-origin resourcesAdd the following to the HTTP response headers of cross-origin resources:
Add crossorigin="anonymous" to the HTML tags that reference the resource:
See MDN documentation Access-Control-Allow-Origin and crossorigin attribute.
Logged-in User IdentificationFor applications that require user login (such as SaaS products, membership systems, e-commerce platforms), see User Sessions.Device Fingerprint IdentificationFor applications without login (such as corporate websites or marketing pages), report a visitor ID assigned by your own system as the user identifier.