Email alerts and digests

Alerts are created when a PageSpeed run violates an active performance budget. You do not write a separate “alert rule” for each page — configure the budget, then review what fires under Alerts.

Set thresholds first: Set performance budgets.

View alerts in the panel

1. Sign in at /admin.
2. Open Performance → Alerts.
3. Filter by site, status, or date as needed.
4. Open an alert to see which page and strategy breached which metric.

Alerts — empty until an active budget is violated; all roles can browse the list.

All organisation members can browse alerts. Resolving or deleting alerts requires Manager or Admin.

How digests work

When budget checks find violations, Watcher can send a site-level digest email (subject style: {site name} — PageSpeed Budget Violations Digest). The message summarises failing pages for that run (a capped list of detail rows) rather than one email per page.

Cooldowns and reminders

To reduce noise, Watcher applies a cooldown (default about 60 minutes) per page and strategy before re-notifying the same violation pattern. Unresolved issues can surface again on a cadence aligned with the site’s scheduled test frequency.

If you receive fewer emails than expected, check:

• Budget Active and thresholds realistic vs recent lab scores
• Alert channel allowed on your plan (email vs Slack vs webhook)
• Whether you are an Admin in that organisation
• Cooldown window after a recent digest

If you are a Manager or Admin — configure signal

1. Keep budgets accurate and strategy-specific.
2. Prefer email on lower tiers; enable Slack or webhook only when your plan includes them — see Understand plan limits.
3. Assign at least one Admin who should receive digests for the client workspace.