Docs

Scores

Every report starts with up to four numbers from 0 to 100. Each is worked out from what the report shows, the same way every time, and lists the three things that lowered it most.

Reading a score

The bands are the same as Lighthouse's, so a number reads the same here and in PageSpeed Insights.

  • 90 to 100, good. Nothing important to fix.
  • 50 to 89, needs work. Worth fixing the reasons listed under the score.
  • 0 to 49, poor. Visitors or Google are losing out today.

An area the audit did not check has no score, rather than a 0. A finding you mark Not an issue, or that our team drops when checking the report, stops counting at once.

Works

Does every page, link and form work. It starts at 100, and each problem found takes points by how serious it is:

SeverityConfirmed issueWorth a look
Critical−40−20
High−20−10
Medium−8−4
Low−4−2

A finding the agent was not sure about, shown under Worth a look, counts half. The score never goes below 0.

Speed

How fast the site is on a phone, from the pages measured on a mid-range phone over slow 4G with an empty cache. Each metric is scored the way Lighthouse scores it: on a curve that gives 90 at the "good" mark and 50 at the median, then weighted. Lighthouse also uses Speed Index, which the audit does not measure, so the other weights are scaled up to make 100. Total Blocking Time weighs half of what Lighthouse gives it: the audit measures a real load on a slowed-down phone, where blocking time differs most from Lighthouse's simulated one, so it counts for less until the two agree.

MetricScores 90 atScores 50 atWeight
Largest Contentful Paint 2.5 s 4.0 s 39%
Total Blocking Time 200 ms 600 ms 17%
Cumulative Layout Shift 0.1 0.25 28%
First Contentful Paint 1.8 s 3.0 s 17%

The score is the average of the pages measured. A page is measured twice and the faster run is kept, so one slow response does not lower it; the same page measured again stays within 5 points. The speed findings below the scores explain the causes; the score itself comes only from the measurements.

SEO

Can Google read and show every page: the share of checks passed, weighted by how much each matters. A check on each page, like a missing title, costs its weight times the share of pages that fail it. A check of the whole site, like a missing sitemap, costs its full weight. Weights add up to 99.

Keeps pages out of Google

  • noindex: 10
  • canonical broken: 10
  • robots blocks all: 10
  • robots blocks search: 10
  • robots error: 6
  • js only content: 6
  • title missing: 6

Makes pages harder to find or rank

  • https redirect: 4
  • robots blocks ai search: 4
  • description missing: 3
  • h1 missing: 3
  • canonical elsewhere: 3
  • duplicate title: 3
  • viewport missing: 3
  • sitemap missing: 3
  • sitemap invalid: 3
  • sitemap broken: 3
  • canonical missing: 2
  • host redirect: 2
  • js only head: 2
  • structured data invalid: 2
  • image alt: 2
  • lang missing: 2

Polish

  • og missing: 1
  • title long: 1
  • title short: 1
  • description long: 1
  • h1 multiple: 1
  • heading skip: 1
  • duplicate description: 1
  • sitemap redirect: 1
  • sitemap missing pages: 1
  • robots missing: 1
  • structured data missing: 1

A site whose robots.txt blocks every search engine, or Googlebot or Bingbot alone, or whose home page says noindex, scores at most 20: Google is told to stay away, whatever else is right.

Overall

The average of the areas checked, and never more than 30 points above the lowest one. A site that works and is fast but is hidden from Google does not score a reassuring 80: one broken area always shows.