Health scores explained
Every site in Field has a health score — a single number from 0 to 100 that reflects the overall condition of the site based on scan findings. The score updates with each scan and gives both operators and clients a clear picture of where things stand.
How scores are calculated
The health score is a weighted composite derived from active findings across all seven scan domains. Each finding deducts points from a perfect 100, weighted by both the domain's importance and the finding's severity. A critical security finding pulls the score down more than a low-severity SEO issue.
Seven domains
Findings are organized into seven domains, each contributing to the composite score with its own weight:
Security
Authentication, file permissions, exposed secrets, known vulnerabilities, SSL configuration. Highest weight — security issues have the largest score impact.
Performance
Page speed, asset optimization, caching configuration, database query efficiency. Core Web Vitals alignment.
Technical debt
Outdated software versions, deprecated APIs, unmaintained plugins, PHP compatibility. The backlog that compounds over time.
SEO
Meta tags, structured data, canonical URLs, crawlability, sitemap health. Factors that affect search visibility.
Accessibility — labeling
Alt text, form labels, ARIA attributes, link text. The content-level accessibility work.
Accessibility — structural
Heading hierarchy, landmark regions, focus management, keyboard navigation. The architectural accessibility work.
Content structure
Broken links, missing pages, orphan content, redirect chains. The information architecture layer.
Score ranges
Scores map to four conditions:
- • 90 – 100 — Excellent. Minimal findings, well-maintained. The goal for active stewardship.
- • 70 – 89 — Good. Some issues present but nothing critical. Normal operating range for most sites.
- • 50 – 69 — Needs attention. Accumulating issues that should be addressed before they compound.
- • Below 50 — Critical. Significant problems across multiple domains. Likely requires a focused remediation sprint.
Score changes over time
Each scan produces a new score snapshot. Field tracks the trend — the score from the previous scan is compared to the current one, and the delta is shown alongside the score. A rising score means findings are being resolved faster than new ones appear. A declining score means the opposite. Monthly reports include the score trajectory for the period.
Relationship to findings and work
The score is a consequence, not a goal. It goes up when you resolve findings through the work pipeline. It goes down when new issues are detected in scans. Operators don't manipulate the score directly — they do the work, and the score reflects reality. This makes it a reliable signal for clients: when the number moves, something actually changed.
Next: Finding types catalog →