Real User Monitoring
Field data from real devices and networks, against the synthetic run that looked fine.
4 to work through
-
beginner
Interaction to Next Paint replaced First Input Delay as a Core Web Vital on 12 March 2024. A site that passed FID comfortably can fail INP badly. What did FID measure, what does INP measure, and why does the change match user complaints better?
3 min answer -
intermediate
A content platform's synthetic tests pass and users report slowness. What monitoring closes the gap?
2 min answer -
advanced
A team's synthetic monitoring is green and users report the site is slow. What is the monitoring missing?
1 min answer -
advanced Multiple choice
Real user monitoring shows p75 largest contentful paint at 2.1 seconds - comfortably inside target - while a marketing analysis shows a real drop in conversion from organic mobile traffic. Which measurement artefact most likely explains the gap?
3 min answer
5 terms in this topic
Beacon Survivorship
The bias in field performance data caused by users abandoning a page before the measurement beacon is sent - so the slowest sessions are excluded and…
conceptField Data Versus Lab Data
The difference between what real users on real devices experience and what a synthetic run measures, and why the second is systematically optimistic.
metricInteraction to Next Paint
A field metric reporting one of the slowest complete interactions on a page - input delay plus handler processing plus the wait for the next paint - …
toolReal User Monitoring
Telemetry collected from actual browser sessions, capturing what real users on real devices and networks experienced.
practiceRepresentative Device Measurement
Measuring performance on the devices and networks the audience actually uses, and on the distribution rather than the median - because a build agent …
Neighbouring topics
Frontend & Experience Architecture
General material on architecting the surface the user actually touches.
Rendering Strategies
Client, server, static and incremental rendering, and what each costs on first paint.
Edge Rendering
Running the render close to the user, and the personalisation and cache trade it implies.
Hydration Cost
The gap between visible and interactive, and the JavaScript that closes it.
Micro-Frontends
Independent deployment of UI slices, and the shared runtime that undermines it.
Module Federation
Loading code from another build at runtime, with versioning and failure to think about.
UI Monorepo Strategy
One repository for many front ends, and the build graph that makes it viable.
Design Systems
Components as a versioned internal product, with adoption and deprecation like any API.
Component Contracts
Props, slots and events as an interface, and the breaking change hidden in a style.
Client State Architecture
Server state, UI state and derived state, and why conflating them causes most bugs.
Client Caching & Data Layer
Stale-while-revalidate, invalidation and optimistic updates on the client.
BFF for Experience
One backend per experience, shaped by the screen rather than by the domain.
API Shapes for UI
REST, GraphQL and RPC judged by over-fetching, round trips and client coupling.
Web Performance Budgets
A number a build can fail against, rather than a performance sprint once a year.
Core Web Vitals
LCP, INP and CLS — what they measure, and the architecture that moves them.
Accessibility Architecture
Semantics, focus management and announcements designed in rather than audited in.
Internationalisation
Locale, direction, pluralisation and dates as structural concerns, not string tables.
Client Feature Flags
Flag evaluation on a device you do not control, and the flicker and staleness it brings.
Frontend Security
CSP, XSS, CSRF, token storage, and the trust boundary that ends at the browser.