Something shipped, and your site got slower. Which release was it, and what broke?
Deploys shows where it went wrong. Making it easier to find and fix regressions, and track new releases.
Now in Real User Monitoring and Synthetic, it compares every release with the one before it, flags the ones that regressed, and shows which metrics and pages changed.

A month of releases, each measured until the next. Bad deploys are shaded in red.
Select a release to see which metrics got worse, by how much, and which pages were most affected. Improvements are listed too.

Release ce2f181 dropped UX Rating from 80 to 40. LCP rose 925 ms, and /experience/first-class fell from 80 to 35.
Pick a metric (UX Rating by default in RUM, Performance Score in Synthetic), or filter to Regressed to see only the releases that got worse.
- RUM shows how each release changed the experience for your real visitors.
- Synthetic uses your scheduled tests, with a line per Test Profile, so you can see whether mobile, desktop or both got worse. Every test runs on the same device and connection, so any change points to the release itself.
Find it at Site → RUM → Deploys or Site → Synthetic → Deploys. Read more in the RUM Deploys and Synthetic Deploys docs.
Ask your coding agent#
Calibre MCP can check deploys too, using RUM or Synthetic data. Ask “Did yesterday’s deploy make anything slower?” and your agent compares it with the deploy before.
Getting started#
Deploys are included on every plan. Send deploys from your CI, or connect GitHub and Calibre records them for you.





























