Quick Summary
Lemwatch estimates grams of CO₂ per page view from available page-weight data and a hosting signal. It is a model, not a direct emissions measurement: use it to compare the same page over time and state the limitations alongside any sustainability claim.
- Per-page CO₂ estimate and page-size input stored with the check
- Hosting-provider signal, not a facility-level renewable-energy verification
- Historical results for comparing a page after optimisation work
- Practical page-weight reduction ideas for images, scripts, fonts and caching
The Internet Has a Carbon Problem
Every website visit transfers and processes data. A modelled estimate can help prioritise page-weight work when its assumptions are kept visible.
use the result to compare changes, not to report measured facility emissions
recent PageSpeed data is preferred; a homepage estimate is the fallback
compare the same page after reducing images, scripts, fonts or other bytes
What We Measure
Estimate Inputs
- • CO2 grams per page view
- • Page-size value used for the estimate
- • Website Carbon API comparison context when returned
- • Hosting-provider signal
Resource Breakdown
- • Page weight in bytes
- • Energy consumption (kWh)
- • Whether PageSpeed or fallback data was available
- • A repeatable result for before-and-after comparison
Reduce Your Carbon Footprint
Reducing page weight can improve both the estimate and page-load performance.
Optimize Images
Use WebP/AVIF formats, proper sizing, and lazy loading
Minimize JavaScript
Remove unused code, defer non-critical scripts
Review hosting evidence
Ask providers for current location and energy documentation rather than relying on a provider-name signal
Enable Caching
Reduce repeat data transfers with proper caching
How Carbon Calculation Works
Page Weight Analysis
Use recent PageSpeed total-byte-weight data when available; otherwise estimate page weight from the homepage HTML.
Energy Calculation
Send the estimated page weight to the Website Carbon API, with a documented local fallback when it is unavailable.
Carbon Conversion
Return an indicative CO₂ figure and a hosting signal; it is not a facility-level emissions measurement.
Complete Carbon Analytics
Inputs, estimates and practical page-weight investigations for a repeatable sustainability workflow.
CO2 Per Page View
Estimate CO₂ per page view from the page-weight data available to the check.
Green Hosting Detection
Flag hosting providers that match Lemwatch's supported green-host provider list.
Comparable Estimates
Use a consistent estimate to compare a page before and after weight-reduction work.
Historical Tracking
Store carbon-check results so you can review changes over time.
Optimization Tips
Get actionable recommendations to reduce page weight and energy consumption.
Clear Method Notes
See the estimated grams, page size and green-host flag behind each result.
Carbon Footprint FAQ
Why website carbon matters — and what actually moves the number
Digital-emissions figures are modelled estimates, not a direct meter reading from a browser, network or data centre. They can still be useful when their inputs and limits are clear. Lemwatch's check uses page-weight data and a hosting signal to produce an indicative figure for one page view; it should not be used as an audited carbon inventory or a facility-level claim.
Page weight is the most actionable input in this estimate. Optimising oversized images, removing unnecessary third-party scripts, reducing unused JavaScript and avoiding unnecessary font files can reduce transferred bytes. The actual environmental impact will also depend on caching, device use, network path and infrastructure energy mix, which this check cannot observe directly.
The green-host result is a provider-name signal, not proof that a particular server or request was powered by renewable electricity. Use it as a prompt to ask a provider for current energy and location documentation rather than as a sustainability certification.
The practical use of repeat checks is directional: record a baseline, make a page-weight change, then compare the same page again under the same model. A change in the estimate is evidence that the modelled input changed; it is not a guarantee of a specific emissions reduction in the physical world.
How the Sustainable Web Design model works
Lemwatch currently uses the Website Carbon API for its primary estimate. The check sends a page-weight value and a green-host flag to that API; where recent PageSpeed byte-weight data is unavailable, it estimates page weight from fetched homepage HTML. Refer to the Website Carbon API and Sustainable Web Design documentation for their model assumptions.
Where most sites actually leak emissions
Start with the bytes you can inspect: oversized images, third-party scripts, unused JavaScript and font payloads. Validate each proposed change with performance tooling and a visual regression check; the size and carbon-estimate impact vary by page and visitor context.
Cited sources
- Sustainable Web Design model v4 — Sustainable Web Design
- Green Web Foundation dataset — Green Web Foundation
- Web Almanac — sustainability chapter — HTTP Archive
Related performance & sustainability pages
Core Web Vitals monitoring
Review LCP, INP and CLS alongside page-weight evidence
Performance budgets
Define page-weight expectations and investigate changes after releases
Image optimization audit
Identify oversized image payloads before deciding on a fix
Font performance
Review font payloads as one possible source of transferred bytes
WordPress monitoring
Carbon tracking for WordPress stacks
Shopify monitoring
Carbon tracking for Shopify storefronts
Start a Repeatable Carbon Estimate
Use the same page and model before and after a page-weight change, then document the estimate's limitations with the result.