This glossary defines Apogee Watcher product terms as they appear in the customer panel. Use it when onboarding teammates or writing client-facing notes. For LCP, INP, and CLS, see Core Web Vitals definitions.
These entries are definitions, not how-to guides. Each term links to the procedural article when one exists.
Organisation
An organisation is the multi-tenant workspace boundary in Watcher: team members, plan limits, sites, budgets, and shared history. Agencies often use one organisation per client; solo operators may keep a single organisation with many sites.
See First organisation and site and Manage multiple organisations.
Site
A site is one monitored property inside an organisation—usually one production hostname. Sites hold pages, schedules, strategies (mobile/desktop), and site-level API usage.
Page
A page is a specific URL tracked under a site. Pages can be added manually or found by discovery. Each page has priority and test frequency settings.
See Add and discover pages and Page priority and test frequency.
Admin, Manager, and Viewer
Organisation roles control what someone can change:
| Role | Typical access |
|---|---|
| Admin | Full control of the organisation, including settings, billing-related actions where available, and invites |
| Manager | Run tests, manage sites/pages/budgets, invite Viewers (and often Managers, depending on plan policy) |
| Viewer | Read results, reports, and alerts; cannot run tests or change configuration |
Lab data and field data (CrUX)
Lab data comes from a single Lighthouse-based PageSpeed Insights run under controlled conditions. Field data comes from the Chrome UX Report (CrUX)—real Chrome users over Google’s rolling window—when enough samples exist for that URL or origin.
See Lab data vs field data. Metric names (LCP, INP, CLS) are defined in Core Web Vitals definitions.
Performance budget
A performance budget sets pass/fail thresholds for a site on one device strategy (mobile or desktop)—for example Performance score, LCP, INP, or CLS. When a run exceeds a limit, Watcher can raise an alert.
Page discovery and priority
Page discovery finds candidate URLs (for example from sitemaps or crawls) so you do not have to paste every path by hand. Priority steers how often Watcher tests a page: important templates get more frequent checks; low-value URLs can stay on a lighter schedule.
See How page discovery works and Page priority and test frequency.
API quota and test limit
Watcher runs PageSpeed Insights through its own Google integration. Your plan caps how many tests you can consume (organisation and site usage views show remaining capacity). Hitting the cap pauses or blocks further runs until the period resets or you upgrade—not a failed site.
See Site API usage and quotas and Understand plan limits.
Read-only mode
When a paid subscription ends without renewal, the organisation can enter read-only mode: you can still view history, but you cannot create sites, run new tests, or change configuration until billing is restored.
See Read-only when subscription ends.
Attention-Free Score
The Attention-Free Score on a domain performance report Summary is the share of completed lab tests that pass Watcher’s attention gates (Performance and category floors plus Core Web Vitals thresholds, with a Total Blocking Time fallback when Interaction to Next Paint is unavailable). 100% means no monitored page needs attention on either strategy in that report.
See Attention-Free Score for gates and how to read Summary, Domain performance reports to generate a report, and the blog post Attention-Free Score.
White-label and domain reports
White-label reports present Watcher output under your agency branding where the plan allows. A domain performance report (including the public Summary) aggregates pages for a hostname so you can triage without opening every URL.
See White-label reports and Domain performance reports.
Mobile and desktop strategy
Each page can be tested with a mobile strategy, a desktop strategy, or both. Lab scores and CrUX field data are strategy-specific—a strong desktop result does not prove mobile health.