Performance budgets v3 with SLO burn-rate tracking
Promote any performance budget to a full SLO. PagePulse now tracks 30-day burn rate, error budget remaining, and projected breach date so you can share objective performance data with leadership.
Every PagePulse release, improvement, fix, and deprecation in chronological order. Filter by type to see exactly what changed.
Promote any performance budget to a full SLO. PagePulse now tracks 30-day burn rate, error budget remaining, and projected breach date so you can share objective performance data with leadership.
Join RUM data with your UTM parameters, referrer, and landing page to see which marketing campaigns and traffic sources bring the slowest experiences. Available on Growth and Scale plans.
The before/after deployment diff now ships with hydration time, route load time, and time-to-interactive in addition to LCP, INP, CLS, and JS bundle size. Statistically significant changes are highlighted automatically.
Safari 17 reports interaction timing slightly differently than Chrome and Firefox, which produced false-positive INP regressions in the deployment diff. The diff now applies a Safari-specific adjustment factor.
New projects default to cookie-free RUM collection. Existing projects can opt in from Settings > Privacy. Cookie-free mode requires no consent banner in most jurisdictions.
Every outbound webhook is now HMAC-signed and timestamped. Failed deliveries retry with exponential backoff for up to 24 hours. The new /webhooks/events endpoint lets you replay any past event.
When a performance budget is breached, PagePulse can now auto-file a Linear issue or Jira ticket with the offending route, the delta, and a deep link into the dashboard. Available on Growth and Scale plans.
Parallel routes (slot files) were previously tracked as separate pageviews, inflating route counts. The Next.js adapter now correctly attributes parallel route interactions to the parent route.
The Monday morning PDF report now ships with 4 prioritized recommendations per week, ranked by estimated conversion impact. Each recommendation links to the slow route and the offending resource.
The v1 inp field in the /v1/events API is now deprecated and will be removed on October 1, 2025. Use the v2 inp_p75 field instead, which returns the 75th percentile INP per route.