DocumentationOpen PingAgain
Browse

Monitoring

Lighthouse audits

Understand mobile lab scores, weekly audits, comparisons, notifications and current availability.

Lighthouse helps you understand a Website's performance, accessibility, best practices and SEO. PingAgain-operated browsers measure Mobile and Desktop separately using Lighthouse. These are lab measurements, not uptime checks or a summary of every visitor's experience.

Availability: Auditing is initially limited to explicitly authorized Websites and accounts. If your Website shows Unavailable, no new audit can be requested; any saved reports remain available. Having an existing uptime monitor does not automatically authorize browser audits.

Enable and schedule audits

When available, open your Website, choose Lighthouse, then Settings. An account member with permission to manage the Website can enable auditing. PingAgain requests initial Mobile and Desktop audits. When scheduling is available, each device is checked every seven days; Settings shows when scheduled audits are paused. Audits run one at a time and can wait when capacity limits are reached; their scheduled time is not a promise of immediate completion.

Run check requests an additional audit. A one-hour cooldown applies, and another audit cannot be requested while one is already pending. A manual audit does not move the weekly schedule. A temporary provider failure may be retried once after a delay. Disabling Lighthouse stops new audits without disabling your other Website checks.

The service supports explicitly authorized public HTTPS Website URLs. URLs with query strings, credentials or nonstandard ports are not eligible. Browser access is restricted to approved public hosts. Sites requiring third-party hosts may produce incomplete results until those dependencies are reviewed. Do not submit private pages or URLs containing confidential information.

Read reports and history

Report shows scores out of 100, loading and layout metrics, and the findings supplied by the audit. A missing value means Not reported, not zero. A Partial report contains useful results but is incomplete or includes a provider warning. Review its limitations before drawing conclusions.

Desktop opens by default; choose Mobile for mobile measurements. Explicit device links preserve your selection across Report, History and Settings. History shows that device's audit attempts and score trends. Open an attempt to see its report. Comparisons require the same device, complete results for the current Website configuration and the same Lighthouse engine version. Missing, failed or incompatible attempts leave gaps rather than implying improvement. A score change alone is not an outage.

History contains up to 52 recent attempts per device, subject to your account's report-retention limit and a maximum age of 365 days. Older records may disappear. Incident summaries can preserve the score evidence used for an alert separately from the report list. Disabling and re-enabling auditing starts a new comparison period; earlier results remain labelled as history.

Full Lighthouse report

New audits can include the original Lighthouse HTML report generated during that exact audit. View embedded report, Open full report and Download HTML require access to the owning Website. The hosted viewer is isolated from PingAgain sessions and cannot load external resources. Some report links and sharing controls are intentionally unavailable in this protected viewer.

Reports can include public resource URLs, page excerpts and diagnostic images. They are stored privately with encryption at rest, a 4 MiB per-report limit and bounded storage capacity. Downloads may contain those details; share them carefully. Browser traces and temporary browser profiles are not retained. The HTML follows the audit's retention and account access rules. An oversized report or storage failure can leave valid scores available without HTML. Older audits without a saved original report show an unavailable message; PingAgain does not reconstruct it or run another audit automatically.

Alerts and Snooze

Score notifications are disabled for the initial authorized accounts. Existing uptime and other monitoring notifications are unaffected. Desktop score notifications are not enabled; Desktop reports and history remain available independently.

Lighthouse builds a comparison baseline from three complete, comparable audits. Two consecutive audits with a qualifying score drop are needed before a Lighthouse incident opens. Recovery also requires confirmation. Provider errors, partial reports and changes to the test configuration do not count as a confirmed score recovery.

In Settings, review email preferences and the link to Website integrations. Email inherits your account and Website preferences unless you choose a Lighthouse override. Webhooks, Slack, Microsoft Teams and Google Chat use their configured destination scopes and event settings; they do not inherit the email checkbox. Delivery also depends on the module's notification setting, recipient or destination eligibility, and any active Snooze.

Use Snooze to pause Lighthouse notifications for a chosen duration. You can cancel it early, and it expires automatically. A Lighthouse-only Snooze does not pause Uptime or certificate alerts. A Website-wide alert Snooze can also affect Lighthouse. Snooze does not stop audits or move the weekly schedule, and expiry does not promise a replay of every suppressed notification.

Troubleshoot an audit

  • Unavailable: Auditing is not enabled for the service or account. Saved results are not a new health check. Contact support if access was previously available.
  • Queued or Checking: The audit has not finished. Avoid repeated recheck requests; inspect History for its eventual outcome.
  • Audit unavailable: The browser may be unable to reach the page, a dependency may be outside the approved public-host scope, or execution capacity may be temporarily unavailable. Check the failure explanation and cooldown before trying again.
  • Previous configuration: The Website address or audit settings changed. Wait for a new comparable report rather than treating old scores as current.
  • No email or chat message: Check the confirmed incident, preferences, Snooze, recipient verification and integration delivery history. A changed score does not always meet the incident threshold.

For help, send the Website name, audit time and visible error to support. Never send API keys, private URLs, authentication cookies or integration secrets. See delivery history for delivery troubleshooting.