PageSpeed Insights

Operationalnormal

Lighthouse scores for the website half of a grader scan.

checked 2m ago

Checks

PageSpeed API reachable

Google is not answering at all — grader reports lose their Lighthouse scores.

100%

24h

100%

30d

GET https://pagespeedonline.googleapis.com/pagespeedonline/v5/runPagespeedexpects 429 or 400 or 403 or 401last 429 · 124ms · 2m ago

PageSpeed audit run

Grader reports lose their Lighthouse scores.

A real probe costs a full Lighthouse run and counts against quota, so it stays off. The liveness check above covers the outage case for free; quota is watched in the Google Cloud console.

What it is

The grader runs a restaurant's site through PageSpeed Insights and pairs the result with its own HTML fetch. The provider version string a scan reports — pagespeed-v1+website-html-v1 — records both halves.

PageSpeed is slow by nature: a cold Lighthouse run can take 20-30 seconds. The grader wraps it in a timeout and reports the website step as degraded rather than failing the whole scan when it does not come back in time.

Failure mode

Quota exhaustion returns a 429 and the website step downgrades its confidence; the scan still completes with the direct HTML fetch alone. A user sees a report with a thinner performance section, not an error — another quiet degradation worth watching from here.

When it breaks

Symptom

Website section of reports is consistently thin

Check

PAGESPEED_API_KEY presence and the API's quota in the Google Cloud console.

Fix

Set or rotate the key. Without a key the audit is skipped entirely rather than run anonymously.

Breaks when this does

Restaurant Growth GraderLead-gen tool: scans a restaurant and returns a scored growth report.

Incident history

No incidents recorded for this system.