Module score
Points from completed checks ÷ sum of those check weights × 100. Fail = 0 for that check, warn = partial weight, pass = full weight. Performance is the exception: since 1 Oct 2026 its score is the Lighthouse score from the lab run.
Methodology
From the server response and rendered page to scores, findings and priorities. See what was measured, what was missing and how to read the report.
Methodology v1.4, Updated: 24 Oct 2026, Changelog
Every finding shows where its signal came from.
Every threshold has a source: Google documentation, WCAG or OWASP.
Scope, device and method version are saved in the report.
Score
Each module uses completed checks. Weight reflects the impact of a problem, while missing data stays visible as N/A.
Example finding
Using a missing HSTS header: where the signal came from, which rule applied and how it changed the module score.
Every finding in the report carries the same fields.
A module score comes from available, completed checks. N/A checks are neither a pass nor a zero and do not enter the denominator.
Points from completed checks ÷ sum of those check weights × 100. Fail = 0 for that check, warn = partial weight, pass = full weight. Performance is the exception: since 1 Oct 2026 its score is the Lighthouse score from the lab run.
A missing signal does not lower the score and is not counted as a pass. We show N/A separately so “not measured” is never confused with “zero”.
Combines measured module scores using the weights of the published methodology version, then applies the risk gate. An N/A module does not enter that aggregation.
One very weak module limits the whole score. When the weakest measured module scores below 50, the overall score is capped at 69; below 40, it is capped at 59. An N/A module does not trigger the gate. A module whose measurement is flagged as unreliable (for example a Lighthouse run that stayed anomalous after a re-measure) keeps its weight in the average but cannot cap the score.
P1–P4 orders the implementation backlog. It does not map 1:1 to score points, because severity, scope and confidence set priority separately.
Checks do not count equally: the weight depends on impact (high > medium > low). A passed check earns its full weight, a warning part of the points, a failure zero. A module score is earned points over maximum points, scaled to 0–100.
A module or check without data is reported as N/A and excluded from the denominator. The score covers only the measured scope and coverage. A deeper scan level adds modules and scope, but does not rewrite verdicts of checks already measured.
Data
Lab measurements, HTTP responses, automated detection and CO₂e estimates have different limits. The report labels each one.
The Performance module score is the Lighthouse score from a lab measurement. CrUX field data sits next to it, with its own source.
Lab measurement
Field data (CrUX)
Lighthouse / PageSpeed API
Source limit: Results may vary between runs
Statuses, headers, redirects, cookies
Source limit: Server state at scan time
Automated, on the rendered DOM
Source limit: Some criteria require manual review
The SWDM v4 model based on data transfer
Source limit: Not an emissions measurement or a certificate
Links, sitemap.xml and a manual list, the page is rendered with JS
Source limit: Page limit per plan; recurring issues are grouped into one finding with its scope
Insight does not install a script on the site. It reads what the browser shows and what the server returns, in one scan session.
A real browser, JS, DOM and what the user actually sees.
Statuses, headers, redirects and cookies at scan time.
No script on the client site
Thresholds
Checks use thresholds from source standards. You can cite those standards in your client report.
A score takes its colour from the band it falls into, and nothing else. The report and the app use the same bands.
The overall score is a weighted average of the measured modules on a shared 0–100 scale. Only the Performance module takes the Lighthouse score as is. No score is a compliance certificate or a legal opinion.
Priorities
P1–P4 is implementation order, not a synonym for severity. Severity comes from the threshold; priority combines severity, scope and confidence. P1 is not always a critical defect. Sometimes it is a wide, high-confidence issue. Estimated effort is only an auxiliary recommendation.
P1–P4 scale
N/A: not enough data. Never zero or success.
Scan levels
A deeper level adds scope, but it does not change verdicts of checks already measured.
No Lighthouse
Adds performance
Security cluster (ZAP)
Competitors + AI Search readiness
Each level runs a defined module set. Credit costs match the pricing page.
Module count = check suites from the published module catalog. Some suites report into a shared module (e.g. accessibility and privacy screening), so a report may show fewer sections than suites. Basic security checks (TLS, headers, cookies) run from Standard; the OWASP ZAP vulnerability cluster is added at Complete.
AI
A generative model does not set the raw measurement result and does not replace source thresholds. It may help group findings and draft recommendation copy.
Measurement layer
No AI
Measurement, thresholds and severity always come from source data.
pass, warn, fail, N/D
Description layer
With AI
Descriptions, grouping and recommendations, labelled, for review.
Explains the result, for review
Scores, thresholds and severity never come from a generative model.
It groups findings, describes impact and drafts recommendations.
AI recommendations are labelled and nothing is applied automatically.
The score and findings list do not depend on the generative layer.
Limits
An automated scan detects some problems. These boundaries explain where its coverage ends and further review is needed.
Replaces neither manual review nor legal opinion.
An SWDM model estimate, not a lab result.
An automated vulnerability scan, not a manual penetration test.
No guarantee of finding every URL on the site.
Shown separately, without treating lab data as field data.
Comparability
Page content, third-party services and network conditions can change between scans. The report records the analysis conditions. Results are compared using the same scale and thresholds.
Scan date and methodology version
Scan level, URLs and device profile
Modules completed and marked N/A
Communicated, never a silent backfill
Sources
Documentation for the thresholds and models used in the report. Refer to it when you need to check a rule or cite a source.
Applies to reports from: 18 Oct 2026
Two model changes that change scores. Since 1 Oct 2026 the Performance module score is the Lighthouse score, with no extra deductions for optimisation suggestions. Since 18 Oct 2026 the Security score uses a new model, and older history points are marked so the trend does not show a jump that never happened. We added this entry late, on 24 Oct 2026.
Risk gate described in the aggregation rules: the 50 and 40 point thresholds and the exception for an unreliable measurement. The rule was already part of the calculation, so the description changes, not the scores.
Table of contents, aggregation and N/A rules, full signal→score example, explicit AI role, versioned sources.
First public methodology: scoring path, sources, thresholds, priorities, scan levels and limits.
The sample report shows the data sources, timing and limits of the analysis. The Free plan then lets you scan one project, no credit card required.