Analyze transfer, cache, assets and hosting. Insight uses the SWDM v4 model to surface the largest sources of estimated emissions and reduction priorities.
Insight organizes technical digital-footprint signals — before you plan transfer reduction or a hosting change.
Results can support reporting, but they are not an ESG audit or certification. A single score does not say how much energy infrastructure actually uses — it combines emission estimates, transfer weight and external dependencies into one reduction-oriented report.
What the module covers
All CO₂e values are model estimates, not a direct measurement of infrastructure energy.
Four steps from URL to decision — without guessing whether the issue is transfer, media, scripts or hosting.
Sum of HTML, CSS, JS and font weight — every kilobyte means network and device energy.
Hero images, background video and fonts — the most common source of excess transfer.
Analytics scripts, CDNs and widgets from other domains — extra connections and transfer.
You test a specific URL — homepage, landing or article. You see scan context and basic digital footprint signals detected automatically.
Each finding has context: which asset, how heavy it is and how it affects estimated CO₂e. Plain language where jargon is not needed.
Issues are ordered by impact on page weight and estimated CO₂e. You know whether to start with hero images, third-party scripts or unused CSS.
Re-run in the same scenario and compare transfer, cache and estimated emissions — not only the point score.
Remediation plan
Instead of generic “make it lighter” advice, the module orders actions by impact on transfer and estimated emissions. Effects are estimates holding other model parameters constant.
holding other model parameters constant
Emission breakdown
The model covers the data center, network transmission, the user device and embodied emissions. You see each component’s share — not only a file list.
Model scale
We compare the estimate to Sustainable Web Design grade thresholds (A+–F), not an invented “industry median”. That is model context — not a market ranking or certificate.
Goal and hosting
Compare the same page in the same scenario. An example project goal (e.g. under 0.5 g CO₂e / pageview) is your reference — not a universal ESG standard. Renewable hosting may lower the data-center component, but it does not zero network or user-device impact.
Set your own reduction threshold for this URL. The Carbon Badge shows an estimate — not an “Eco-Friendly Site” certificate.
Hosting declares renewable energy (Green Web Foundation: confirmed). It may lower the data-center component — it does not zero network or device impact.
Example goal · model estimate · not an ESG audit0.42 g CO₂e / pageview × 500,000 views / mo ≈ 2.5 kg CO₂e / mo
Scenario under assumed traffic and unchanged model parameters — not an organization emission.
It is estimated from data transfer, the SWDM v4 energy model, grid carbon intensity and the chosen network/device scenario. It is not a direct measurement of server or user-device energy.
It is estimated emissions per pageview in a chosen scenario (e.g. first visit). The functional unit, model version and network/cache assumptions are part of the result — without them the number is incomplete.
It is CometWeb’s internal module score (transfer, estimated CO₂e, hosting, resource optimization) on a 0–100 scale. It is not an eco certificate, ESG conformance or a market ranking.
The model separates first visit and cache return when a second-run measurement is available. Otherwise it uses an explicit fallback — it does not hide missing data as zero.
No. A Green Web Foundation confirmation may lower the data-center component, but it does not zero network, user-device or embodied impact.
A+–F thresholds come from Sustainable Web Design (SWDM v4) benchmarks. That is a model scale, not a percentile in a private CometWeb cohort or an industry ranking.
No. Results can support transfer-reduction conversations and reporting, but they are not an organizational ESG audit, CSRD filing or environmental certification.
Per-pageview estimates are multiplied by assumed traffic (e.g. monthly views). The result depends on those assumptions and model parameters — a scenario, not a measured company emission.
Check page weight, cache and estimated emissions, then start with the change that has the highest reduction potential.
