Product Spotlight: Performance Budgets and Email Alerts in Apogee Watcher
A performance budget on paper is only a policy. In production it needs thresholds your scheduled tests actually enforce, and notifications people will read without muting the sender. We wrote this spotlight after watching agency teams agree LCP caps in a kickoff deck, then discover breaches only when a client forwarded a screenshot from PageSpeed Insights.
Apogee Watcher connects site-level budgets to email digests tied to each scheduled PageSpeed run. You set separate mobile and desktop rows per site: performance score floors, LCP ceilings, INP, CLS, FCP, TBT, Speed Index. When a run finishes, the product compares stored lab results against those thresholds and records breaches with the metric, threshold, and observed value.
Alerts are digests, not one email per URL. When violations exist and the budget channel is email, each active organisation admin gets one message per site per run: summary counts, a breakdown by metric, and up to ten pages ranked by weakest score first. Cooldown logic limits repeat noise while a page stays broken.
What lands in the inbox after a breach:
How many pages failed and how many individual metric breaches occurred
Which metrics drove the spike (LCP vs INP vs CLS)
Up to ten URL rows, worst scores first, with totals if more pages failed
Timing aligned to your scheduled test cadence, not a real-time CDN push
Pair budgets with a page list that matches what you sell: discovery keeps the inventory honest; budgets judge the URLs you chose to measure. For client retainers, time-stamped breaches after scheduled runs beat arguing from a one-off Lighthouse tab.
Read more: performance budgets and email alerts in Apogee Watcher
