This guide takes you from a new account to a Site your whole Team monitors, with Synthetic tests, CrUX and RUM data. Work through the six steps in order.
Questions along the way? Get in touch.
1. Add a Site#
From the Sites list, add a Site with a name, URL and Team. Then choose how Calibre finds the Pages to test:
- Discover pages automatically: Calibre crawls your Site and adds up to 25 of your most important Pages, ranked by how prominently they’re linked. It crawls again every week to pick up new ones.
- Add pages manually: choose exactly which Pages to test. You can add more at any time.
Pick a test location and a test schedule. There’s no limit on Sites or Pages.

As soon as the Site is added, Calibre gets to work:
- It collects your CrUX data from Google. Calibre fetches your Site’s Core Web Vitals from the Chrome UX Report, including at least 6 months of history, so the CrUX Dashboard starts with trends, not an empty chart. There’s nothing to install. Calibre also collects page-level CrUX for up to 100 URLs from its crawl of your Site, plus your Pages and your most visited URLs from RUM, and refreshes it every week.
- It runs your first Synthetic tests. Calibre tests every Page three times on two Test Profiles, Desktop and Mobile, to set a baseline. If Calibre is finding your Pages, tests start once the first crawl finishes. We email you when the results are ready.
2. Install RUM#
Real User Monitoring measures real page views on your Site, in every browser, in near real time. With it you can:
- See your UX Rating and Core Web Vitals from real visits, broken down by Page, country, device, browser and page grouping.
- Find the element behind a slow metric. Element attribution names the element behind a slow LCP, the element that shifted the layout, and the click or key press behind a slow interaction.
- Measure every release. RUM Deploys show whether each Deploy made real visits faster or slower.
- Find slow third parties. See which third-party scripts delay interactions.
RUM also tells Calibre which Pages get the most traffic, so automatic discovery tests the Pages your visitors use most.
Calibre shows the RUM snippet, with steps for common setups, when you create a Site. Add it to the <head> of every page you want to monitor. You can find it later in Site → Real User Monitoring → Settings, along with allowed origins, sampling rate and data retention.
3. Invite people#
Go to Manage → People and select Invite people. Choose each person’s role and the Teams they join. Invitations expire after 7 days.
Teams control who sees which Sites. Split them by product, business area or client.
See Manage people.
4. Connect an AI assistant#
Calibre MCP gives ChatGPT, Claude, Claude Code, Codex, Cursor, GitHub Copilot and other MCP clients read-only access to your RUM, CrUX and Synthetic data. Ask “Why is LCP slow on /checkout?” and get an answer from your own data, then have a coding agent fix it.
Every client connects to https://calibreapp.com/mcp. See Connect an AI assistant for each client’s setup.
5. Track your Deploys#
Record each release as a Deploy, and Calibre compares it with the one before it. RUM Deploys and Synthetic Deploys flag regressions and show which metrics and Pages changed.

Choose how to record them:
- GitHub: go to Site → Settings → Integrations and select Add to a repository under GitHub. Every successful deploy of your production branch is recorded. Render reports its deploys to GitHub, so this covers Render too.
- Netlify: connect Netlify in the same Integrations tab.
- Your CI or deploy script: run one command after each deploy. Find your Site slug and secret in Site → Settings → General.
npx calibre deploy create --site=<site> --revision=<revision>curl -X POST "https://calibreapp.com/api/sites/<site>/deploys?secret=<secret>&revision=<revision>"See Record Deploys for every option.
Connecting GitHub also turns on Pull Request Reviews: Calibre tests each pull request’s preview deployment and posts a speed report on the pull request, before it’s merged and deployed to production.
6. Set Budgets and notifications#
- Budgets: set a limit on any Synthetic metric in Site → Synthetic → Budgets, and get alerted when a Page goes over it. Start with LCP, CLS and Total Blocking Time. Pull Request Reviews check Budgets too.
- Email notifications: subscribe to Budget alerts. Every Team member gets a monthly Team Insights report on all the Team’s Sites, and you can opt in to a weekly or monthly Insights report for each Site.
- Slack and webhooks: send alerts to a channel your team already watches, such as #site-performance.
Next steps#
- Which data source to use when
- Customise Test Profiles for the devices and networks your visitors use
- How UX Rating is calculated