Scoring methodology (v1)

The SkySiteAudit score summarises measured check results. It is not a prediction of Google rankings — no tool can truthfully claim that.

Formula (v1)

1. Every check has a severity weight: critical 10, high 6, medium 3, low 1, info 0.
2. For each check we compute a pass rate over every page where it was actually measured: pass = 1, warning = 0.5, fail = 0. On a single-page audit the pass rate is simply 1, 0.5 or 0.
3. Checks that could not be measured ("Not measured") are left out completely — they never count as passed and never as failed.
4. Each category score = Σ(weight × pass rate) ÷ Σ(weight) × 100.
5. The overall score combines category scores using these weights: Crawlability & indexing 30, On-page SEO 25, Links 10, Performance 15, Mobile & accessibility 10, Security 10. Categories with nothing measured are left out and the remaining weights are re-normalised.
6. If less than 50% of the total category weight could be measured, the overall score is withheld and shown as "n/a".
7. On a single-page audit, if the page itself returns an HTTP error (4xx/5xx), the score is withheld too — there is no page content to evaluate. The findings are still listed.

Each report stores the score version, so comparisons over time are only made between audits scored with the same version.

Headline counts

• Critical issues = failed checks with critical or high severity.
• Warnings = all warnings plus failed checks with medium or low severity.
• Passed = passed check results. Not measured = checks that could not be evaluated. On site crawls these are counts of check results across pages, so one problem on 10 pages counts 10 times.

Lab performance thresholds

Lab metrics are measured once per page in this environment: Headless Chromium, mobile emulation 412×823 @2.6x, 4× CPU slowdown, simulated 1.6 Mbps / 150 ms RTT network.

INP (Interaction to Next Paint) requires real user interactions, so SkySiteAudit always reports it as unavailable instead of estimating it. Lab values vary between runs; network distance between SkySiteAudit's server and the website affects timings.

Deterministic vs heuristic checks

Deterministic checks are objectively verifiable (e.g. "the page returned 404"). Heuristic checks are rules of thumb (e.g. word count, title length) and are labelled as such in reports.

All checks