Deployment Impact

Catch regressions
before users do.

Automatically diff Core Web Vitals, JavaScript bundle size, route load time, and error rate between every release. Get alerted in Slack within minutes.

Deployment impact

Every release,
before and after.

PagePulse tags every deployment with version, commit, and environment, then diffs Core Web Vitals, JS size, and error rate automatically. Regressions surface within minutes.

Deployment diff · 4 min ago
v2.8.1·a1b2c3d·production
Beforev2.8.0
Perf score86
LCP2.30s
INP180ms
JS size248KB
CLS0.08
Errors12
Afterv2.8.1
Perf score
94+8
LCP
1.70s-600ms
INP
96ms-84ms
JS size
184KB-64KB
CLS
0.04-0.04
Errors
3-9
Affected routes
/-540ms LCP
/p/[id]-720ms LCP
/search-180ms LCP
/checkout+40ms LCP
Recommendation

Ship it. 4 of 5 affected routes improved. /checkout regressed by 40ms but remains within budget. No rollback required.

How it works

From commit to confidence in four steps.

01

Tag every release

Call PagePulse.deployment from your CI/CD pipeline with version, commit, and environment. PagePulse automatically correlates every RUM sample, every error, and every bundle-size measurement with the release that produced it.

02

Read the diff

For every release, PagePulse generates a side-by-side diff of LCP, INP, CLS, FCP, TTFB, JavaScript bundle size, route load time, hydration time, and error rate. Statistically significant regressions are highlighted automatically.

03

Get alerted in minutes

When a release regresses LCP by more than 10%, INP by more than 20%, or CLS by more than 0.05, PagePulse can alert you in Slack, Linear, Jira, or any webhook within five minutes of going live.

04

Decide: ship or roll back

The deployment diff includes a recommendation: ship it, monitor, or roll back. Every decision is backed by per-route breakdowns and statistical significance, not gut feel.

Ready to ship
faster pages?

Join thousands of frontend teams monitoring Core Web Vitals with PagePulse. Install in 2 minutes, see results today.

No credit card required