Docs / MonitoringBrowse

Changes, expiry and slowdowns

Most outages give a warning first: a DNS record that moved, a certificate that changed, a page that got slower. Heedery watches for these and tells you before your users notice.

On this page
  1. Turn on change monitoring
  2. Review changes
  3. PageSpeed on desktop and phone
  4. Certificate and domain expiry
  5. Slowdown warnings

Turn on change monitoring

Change monitoring is set per site, for websites, APIs and browser flows with an http or https address. PageSpeed is for web pages only.

  1. 1.
    Open the site and go to Settings.
  2. 2.
    In Change monitoring, switch on what to watch.
  3. 3.
    Under Alert on, choose Warnings and critical, Critical only or Never, then save.
WhatWhat it watches · plan
DNS records
A, AAAA and CNAME of the host; NS, MX, SPF and DMARC of the domain. Hourly. Pro and up.
TLS certificate
Issuer, names, key and fingerprint. A renewal by the same issuer is only noted. Hourly. Pro and up.
Page content
The text of the page, hourly; at most one alert every 6 hours while it keeps changing. Team and up.
PageSpeed
Google PageSpeed Insights on a desktop and a phone, once a day: the score, LCP, CLS and INP. Team and up.

New sites watch DNS records and TLS certificate from the start. For page content, you can watch only the text inside a CSS selector and ignore text that matches a pattern, such as a date or a counter.

Review changes

Every change lands on the Changes page, with the newest first. Each one has Before and after and an Acknowledge button. To review shows those nobody has acknowledged yet.

The Changes page with content, PageSpeed and certificate changes to review
Changes, filtered to those waiting for review.

Each change is info, warning or critical. Info is only recorded. A name server change, a certificate that no longer covers the name, or a self-signed one is critical. A new address, an early renewal or a new issuer is a warning.

Alerts for changes go to the site’s email list and the chat channels that cover it. Phones are only pushed for critical ones. A change never opens an incident. Content alerts come at most once every 6 hours while a page keeps changing.

PageSpeed on desktop and phone

Plan/Team and up

Once a day, Heedery runs Google PageSpeed Insights on the site for a desktop and for a phone. It keeps the score and the Core Web Vitals: LCP, CLS and INP.

Find the results on the site’s Performance tab. Switch between Desktop and Phone, or press Run now. You are warned when a score drops sharply or a vital turns poor, on each device separately.

Heedery keeps the full Lighthouse report of each run on each device for 30 days. The panel lists every audit that failed, grouped the way Lighthouse groups them (insights first, then diagnostics, then accessibility, best practices and SEO). Open one to see the scripts, images and styles it names, with their sizes and the time a fix would save.

Open full report
The official Lighthouse report of that run, opened from our copy: nothing runs again. Anyone with the link can open it, without an account, for 30 days after the run (or until the site is deleted), so you can send it to your developer or a client. The link is not tied to you: it keeps working for its 30 days even if you leave the workspace.
Download
The same report as an HTML file, the Lighthouse JSON (the Lighthouse Viewer opens it too), or the prompt below as a Markdown file.
Copy prompt
A ready task for a coding agent such as Cursor or Claude Code: the page, the device, the scores and real-user data, and every failing audit with its savings and the exact files, in the order to fix them, with rules not to break anything. Paste it into the agent in your site’s code. No AI is involved.
How to speed it up
An AI plan written from the report: what to fix first, what it should bring, how to do it on the platform the report detected, and what to leave alone. Each step names the audits it comes from. It is kept with the report, so opening it again costs nothing; the next run starts a new one.

The full report, Copy prompt and How to speed it up come with PageSpeed, on Team and up. In the phone app, the PageSpeed card has Open full report, Copy prompt and How to speed it up too.

Certificate and domain expiry

Heedery reads the certificate and the domain’s expiry date once a day. Switch these in the site’s settings under Warnings and regions.

Certificate
30, 14, 7, 3 and 1 days before, and once it has expired. On every plan, with Check the SSL certificate on.
Domain
60, 30, 14, 7 and 1 days before, and once it has expired. On Team and up, with Check domain expiry on.

Each warning goes once, to the site’s email list, its channels and phones. A renewal starts the count again.

Slowdown warnings

Plan/Pro and up

Heedery learns how fast each site usually answers, from the last 7 days. It warns you in two cases:

Slower than usual
For the last hour the site answers at least 2 times slower than usual and 300 ms slower, checked three times in a row. At most once every 6 hours.
Getting slower
This week is at least 1.5 times slower than last week and 100 ms slower. At most once a day.

A site needs a day of one-minute checks, or three days of 15-minute ones, before it is judged. You also get a note when it is back to its usual speed. Switch it under Performance warnings in the site’s settings.

Note“Slower than usual” needs at least five good checks an hour. A site checked every 15 minutes only gets “Getting slower”.

Still stuck? Write to us.