Project dashboard & health score

What it's for

The project home: your latest crawl's health score, issue breakdown by severity, Core Web Vitals and the score trend over time. It is the single place to answer «is my site getting better or worse?».

When to use it

Every time after a crawl finishes, to see the headline result.
Weekly, to watch the trend and catch regressions early.

How to use it

Open a project to land on its dashboard.
Read the health score and the critical/high issue counts.
Click into a severity group or On-page to see the affected URLs.

Reading your results

For each output: is it good, does it need improvement, or is it bad — and exactly what to do next.

Health score (0–100)

Good 90–100: few or only low-severity issues. Maintain it.

Needs improvement 70–89: real issues are accumulating — fix criticals/highs first.

Bad Below 70: significant technical debt hurting crawlability/UX.

What to do next Open the issue list, sort by severity, fix Critical then High; the score is penalty-based so each critical fix moves it most.

Health score trend

Good Rising or flat-high: your fixes are holding.

Needs improvement Flat-low: known issues aren't being worked.

Bad A sudden drop of 25+ points: a regression shipped (also raises a High alert).

What to do next On a drop, use «Compare» against the previous crawl to find exactly which pages/issues changed.

Core Web Vitals (LCP / CLS / INP)

Good LCP ≤ 2.5s, CLS ≤ 0.1, INP ≤ 200ms — passing.

Needs improvement LCP 2.5–4s, CLS 0.1–0.25, INP 200–500ms — needs improvement.

Bad LCP > 4s, CLS > 0.25, INP > 500ms — poor; real ranking/UX risk.

What to do next For LCP: optimize the hero image/server response. For CLS: reserve space for images/ads. For INP: cut long JS tasks.

Next steps

Fix the highest-severity issues first, then re-crawl to confirm the score moved.
Set an Alert so a future score drop notifies you automatically.