Real-user speed

What this feature is for

Real-user speed collects browser performance signals such as Core Web Vitals and route-level behavior from actual sessions. It complements synthetic uptime with customer context. The important distinction is that PreFlight stores the observation alongside the app, release, provider, or customer path it belongs to. That context is what turns a signal into an operational decision.

Before you open it

The SDK or browser signal installed on the app, a consent decision appropriate to your product, and enough traffic to establish a baseline.

Use a real app in the workspace and start with the smallest useful scope. A narrow, representative check gives you a stronger baseline than connecting every environment and every provider at once.

Run the workflow

Install the signal, wait for real sessions, filter by route or release, and identify the slowest user-facing path before changing infrastructure.

1. Open the feature from the dashboard outcome hub.
2. Choose the app and environment that match the decision you are making.
3. Run or save the configuration, then wait for the evidence state to settle.
4. Assign the next action to an owner before leaving the page.

Read the evidence

The view groups real-user timing by route, device, and period so a team can distinguish a broad regression from a small cohort. A green state means the configured assertion passed at the recorded time. It does not claim that every unconfigured path is healthy. A warning is a useful lead; a failure should have a concrete owner and a verification run.

When the result is not healthy

Sparse data is not a fast result. Check installation, sampling, privacy configuration, and release attribution before interpreting the chart.

Do not erase the failed result after fixing the underlying system. Keep the history, rerun the check, and link the new passing evidence to the deployment or incident that caused the change. This gives the team a useful before-and-after record.

Use it with the rest of PreFlight

Use RUM with Health, Deploy, and Uptime monitors to connect experience to cause. Outcome hubs are deliberately connected: Audit finds risk, Deploy decides whether to promote, Health watches the running system, Revenue verifies the money path, Growth manages discoverability, and Trust publishes safe proof. Use the related links below to move between those decisions without losing context.