RUM and synthetic monitoring configured
Why it matters
Synthetic monitoring (Lighthouse CI, automated browser tests) catches regressions in controlled conditions. RUM (Real User Monitoring) captures what actually happens across your user base — different devices, networks, geographies, and browser versions. ISO 25010:2011 time-behaviour requires measuring real performance; without RUM, you are optimizing against lab conditions that may not match production. Without synthetic monitoring, you lack a baseline to detect regressions before they affect users.
Severity rationale
Low because monitoring is detective rather than preventive — its absence does not degrade performance directly, but means regressions go undetected until user complaints surface them, often after significant impact.
Remediation
Integrate the web-vitals library to collect LCP, CLS, and FID/INP from real users and send to your analytics backend. Pair with Lighthouse CI for synthetic baselines.
// app/layout.tsx — report Web Vitals to your analytics endpoint
import { useReportWebVitals } from 'next/web-vitals'
export function WebVitalsReporter() {
useReportWebVitals((metric) => {
fetch('/api/vitals', {
method: 'POST',
body: JSON.stringify({ name: metric.name, value: metric.value, id: metric.id }),
})
})
return null
}
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the Performance Deep Dive Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
External references
- iso-25010:2011 · time-behaviour — Time Behaviour (performance efficiency)
Taxons
History
- 2026-04-18·v1.0.0·Initial import from performance-deep-dive·automated