Speed checks say when a page cannot be measured

Page speed monitoring opens one alert when the site itself stops a page being measured, audits that cannot complete wait for their regular slot, and task text reads the same wherever your team sees it.

One monitoring change worth knowing about on Friday.

For our partners

When a page speed check cannot measure a page because of the site itself (the page hangs, never paints, or its domain does not resolve), the campaign now gets one warning alert saying so. Repeat failures bump the same alert quietly rather than opening a new one, and the alert closes itself on the next successful check. A slow day on the measurement side alone never alerts; only a site-side cause does.

Task titles and descriptions now read the same wherever your team meets them, including the digest email.

Behind the scenes

A monitoring audit that fails three times in a row waits for its regular slot: two fast retries, then back to its usual schedule.

Tasks our team files without naming an assignee now go to whoever implements for that client, rather than defaulting to the partner’s team.