CheckRoostCheckRoost
Integrations

PageSpeed Insights

Run the Lighthouse check through your own Google API key, so its quota is yours and not shared.

The Lighthouse check scores a site through Google’s PageSpeed Insights, which runs Lighthouse for you and answers with the result. Google limits how often a key may ask. Connecting your own key means your sites are scored on your allowance.

What it does in CheckRoost

  • Each site with a Lighthouse check is scored once a day: performance, accessibility, best practices and SEO, on mobile.
  • Each site with an Accessibility check is scanned once a week: up to ten pages at two widths, so up to twenty requests.
  • The timings behind each score are kept, so a drop has a date rather than just a number.
  • Quota is counted against your key. On a shared one, every organization competes for the same allowance.
  • A rate limit is reported as a rate limit, never as a bad score.

Leaving it disconnected

Lighthouse still runs on whatever quota is available, and says so when it is rate limited.

Hooking it up

  1. Step 1. Turn on the PageSpeed Insights API

    In the Google Cloud console, for any project of yours: APIs & Services→Library→PageSpeed Insights API, then Enable.

  2. Step 2. Create an API key

    APIs & Services→Credentials→Create credentials→API key. Restrict it to the PageSpeed Insights API, so the key is worth nothing to anybody who finds it.

  3. Step 3. Paste it into CheckRoost

    Settings→Integrations→PageSpeed Insights, as an owner or admin.

Why it is not checked when you paste it

Google only validates a key by running Lighthouse, which takes tens of seconds and spends the quota the key was connected to protect. So the shape of the key is checked, it is stored, and the first scheduled Lighthouse run confirms it. A problem appears on the integration page within a day.

Disconnecting

Removes the key; Lighthouse goes back to whatever quota is available. Delete the key in the Google Cloud console as well.