What we measure
We estimate the carbon impact of the homepage's declared resources using CO₂.js 0.19.0 and the Sustainable Web Design Model v4. A scheduled HTTP audit downloads the public homepage HTML and supported resources referenced in that HTML and its CSS, including stylesheets, scripts, images, fonts and full declared desktop videos. Only resources on the same origin as the homepage are requested. This is a resource-based estimate of a visit, not a browser recording, a direct electricity measurement or a carbon offset certificate.
A regular, comparable measurement
The audit runs once per month without a browser installation. It sends anonymous GET requests without account credentials or visitor cookies and requests gzip compression. The estimate uses the actual downloaded response-body bytes, including compressed bytes where the server supports gzip. Each distinct resource URL is requested once. Inline data is already included in its containing document; HTTP headers, TLS and other protocol overhead are excluded.
Scope and limitations
JavaScript is not executed. External-origin resources, frames, resources discovered only at runtime, responsive image alternatives and later interactions are outside this audit. The primary declared image URL is used; CSS references are collected without evaluating media queries. Full declared desktop videos and lazy image sources may be counted even when an actual visit would transfer less. Browser caching, screen size, playback time and user choices can change the real transfer. The result can therefore be higher or lower than an individual visit and is not a complete website traffic or organisational carbon footprint.
Default electricity assumptions are used. We do not assume verified green hosting. The HTTP resource audit replaces the earlier proposed browser method; readings from different methods are not directly comparable.
How updates are reported
The last successful value and its measurement date are shown below. A failed resource is reported as a partial estimate. External or unsupported references are counted separately as outside the audit scope. The audit has request, time and transfer limits; if a limit is exceeded or the homepage cannot be retrieved, no new reading is saved. A failed update retains the previous successful reading from the same method and its original date. A missing result is reported as pending, never as zero emissions.