Real user experience
Real user experience: measure load, interaction and stability in visitors browsers, count resource and request errors, and read p75 ratings in the console.
What it does
The node injects a one-line same-origin script into sampled HTML pages. The visitor's browser measures real load speed, interaction responsiveness and page stability, and reports resource load failures, navigation failures and fetch and XHR errors. The data is aggregated and shown in the console with p75 ratings.
When to use it
- You want the speed real visitors experience rather than lab measurements.
- Compare the experience before and after a redesign, a line change or turning on caching.
- Locate slow spots by page, country/region and device type.
- Spot a resource or API that keeps failing.
Where to configure it
Enable it: Sites, pick the site, Edit, "Advanced settings", the "Real user experience reporting" switch in the "Other" card, then set the "Sampling rate". View it: Analytics, Real user experience. Nodes must support the feature; nodes that need an upgrade are listed when you publish.
Settings
| Setting | Default | Description |
|---|---|---|
| Real user experience reporting | Off | Site-level switch |
| Sampling rate | 10% | 1% to 100%; about this many of every 100 page requests get the script |
On the report you choose the site and a time range: last hour, 24 hours, 7 days or 30 days.
Report contents
| Metric | Meaning |
|---|---|
| LCP | Largest Contentful Paint |
| INP | Interaction to Next Paint |
| CLS | Cumulative Layout Shift |
| FCP | First Contentful Paint |
| TTFB | Time to First Byte |
Each metric shows its p75 value, a rating of good, needs improvement or poor with shares, and the p75 trend. Below, the tabs Pages, Countries/regions and Devices show the distribution; devices are desktop, mobile and tablet. "Resource and request errors" is grouped by resource, navigation, fetch and XHR, with element, target, status code and count. Data lags by about 1 to 2 minutes.
The script does not collect query strings, IPs or cookies and creates no visitor identifier.
FAQ
The report stays empty after enabling
Data appears once visitors view sampled pages after the setting is published. Pages cached before you enabled it carry the script only after they expire or the cache is refreshed.
Pages are not reporting
If the site sets a Content-Security-Policy, allow 'self' in script-src and connect-src. Pages with Referrer-Policy: no-referrer cannot report.
Some browsers have no LCP or INP
Those two depend on browser support. Browsers without it do not report them, and the report notes that no browser reported the metric for the range.
Are numbers with few samples reliable
With very few samples the report shows "few samples"; look at a longer time range.