Site health scan: eco-design, accessibility, security
Loads a page in a real browser to measure its actual weight, estimated CO2 footprint, WCAG accessibility issues and missing security headers.
The tool actually loads the page in a browser to measure its weight, structure and accessibility, the same as a real visitor would. No private data is collected, only what the page publicly loads. Approach inspired by the open source tool nr-analysis-cli from Institut du Numérique Responsable, with metrics computed independently.
How to use this tool
- 1Enter the URL of the page to analyze
- 2A headless browser actually loads the page and measures transferred weight, request count and DOM complexity
- 3An accessibility analysis (axe-core engine, WCAG) and a security headers check run on the loaded page
- 4Scores and key indicators display immediately; the actionable detail (precise violations, missing headers) is sent by email
Why it matters
A page's weight has a real, often underestimated energy cost, and frequently overlaps with accessibility and security issues: an overly heavy page also loads more third-party scripts, often without basic security headers or correctly set accessibility attributes.
A concrete example
Before a redesign or an accessibility audit, get a cross-cutting eco-design / accessibility / security / performance snapshot in a single scan, rather than four separate tools.
Frequently asked questions
How is the eco-design score calculated?
From three measurements taken while the page actually loads in a browser: total transferred weight, number of network requests and number of DOM nodes. Each measurement is compared against thresholds inspired by common green-IT benchmarks (GreenIT.fr), then weighted into a score out of 100. This is not an official EcoIndex score, but an independent measure based on the same logic.
Where does the CO2 estimate come from?
From the Sustainable Web Design model (the open source @tgwf/co2 library from the Green Web Foundation), applied to the page's real measured weight. It's an estimate, not a direct measurement of electricity consumption.
Does the accessibility scan replace a full accessibility audit?
No. It relies on axe-core, an automated testing engine that detects a subset of WCAG non-conformities (contrast, missing attributes, structure...), but cannot judge the relevance of alt text, keyboard navigation coherence, or other criteria that require human review. A full accessibility audit is still needed for a formal conformance statement.
Why is some information only visible by email?
Scores and key indicators display immediately for free. The actionable detail (exactly which WCAG violations, which security headers are missing) is reserved for the emailed report: it keeps a record of the result and, if useful, opens a conversation about the fixes to make.