Scheduled Testing and Priorities
Coverage you can reason about
Schedule PageSpeed-style tests on a cadence that matches each site’s risk and client expectations (hourly, daily, weekly, or monthly by plan) instead of hoping someone runs PSI by hand. Priority-aware queueing keeps critical pages from starving when the portfolio grows.
Why it matters
Predictable ops, fair queueing, plans that match reality.
Set it and trust it
Automated runs replace one-off manual checks; history becomes meaningful.
Priorities that stick
Important URLs keep getting tested when queues fill up.
Plan-aware limits
Cadence and volume align with subscription, so quota limits are easier to explain.
Cadence per site
Each site gets its own schedule. A run uses the mobile and desktop strategies you configure. Usage rolls up to organisation quota so you can explain coverage versus limits to finance and clients.
How priority shows up in the queue
| Concept | Behaviour |
|---|---|
| Star / priority pages | Get attention before long-tail URLs when the queue is busy |
| Starvation avoidance | Lower-priority URLs still advance instead of waiting forever |
| Failures | Backoff and retries stay predictable (see product behaviour) |
Results feed dashboards and alerts
Completed tests roll into historical series and budget checks. Dashboards & trends and Alerts & digests build on the same runs.