Skip to main content

A CO₂e footprint
you can show the client.

For an agency brief or tender you get an estimate with an explicit method (SWDM v4 model) and the changes with the highest reduction potential — a concrete argument in the report instead of a “green site” slogan.

Illustrative product view
74
Ecology module score 74/100 · example · CometWeb scale How we calculate the score →
Estimated emissions
0.42 g CO₂e / pageview
SWDM v4 model · first-visit scenario
First visit
2.8 MB
Cache return: 0.9 MB · example
Requests
68
CometWeb standard scenario

Interactive demo

See the Ecology module in the app

A guided walkthrough: CO₂e estimate, resources, badge and benchmark — sample scenario, no sign-in.

Insight · Ecology — demo

Hover to choose how to start

Try the Insight demo

No sign-in — take the tour or click through the demo modules on your own.

Want the full Insight demo? Take the full app tour — dashboard, audit and report.

0.42 g CO₂e / pageview is not a “green site” badge — it is an SWDM v4 model with disclosed assumptions, before you plan transfer cuts.

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

  • CO₂e per pageview
  • Energy use
  • Transfer and cache
  • Hosting
  • Assets
  • Annual scenarios

All CO₂e values are model estimates, not a direct measurement of infrastructure energy.

From scan to a lighter site.

From URL to a lighter page: transfer, media, scripts and hosting — with an explicit SWDM v4 model, not a “green site” slogan.

Transfer Scan

Sum of HTML, CSS, JS and font weight — every kilobyte means network and device energy.

2.8 MB68 reqHTML
Media

Hero images, background video and fonts — the most common source of excess transfer.

WebPLazyHero
External

Analytics scripts, CDNs and widgets from other domains — extra connections and transfer.

12 domainsGTMCDN

Address analysis

You test a specific URL — homepage, landing or article. You see scan context and basic digital footprint signals detected automatically.

Areas · transfer
First visit 2.8 MB
High
CO₂e est. 0.42 g
Estimate
External 12 domains
Review
Scan · transfer + media

Impact explanation

Each finding has context: which asset, how heavy it is and how it affects estimated CO₂e. Plain language where jargon is not needed.

Ecology priorities
8

Reduction priorities

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.

74
+12
62 before
74 after

Confirm the reduction

Re-run in the same scenario and compare transfer, cache and estimated emissions — not only the point score.

Remediation plan

Three changes with the highest estimated reduction potential.

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.

  • Priorities by transfer and CO₂e impact
  • Estimated effect under fixed model assumptions
  • Shared ground with the Performance module
Remediation plan Estimated effect: −0.9 MB · −0.12 g CO₂e / pageview

holding other model parameters constant

1 Convert images to WebP/AVIF (18 files) Images −38% transfer
2 Drop 210 KB of unused JS JavaScript −0.2 MB
3 Cache headers on static assets Hosting repeat visits

Emission breakdown

What estimated page emissions are made of.

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.

  • SWDM v4 model components
  • Share in g CO₂e / pageview
  • Network and device scenario in the report
Estimate 0.42 g CO₂e / pageview · SWDM v4 · standard network mix
Data center 28% · 0.12 g
Network transmission 22% · 0.09 g
User device 35% · 0.15 g
Embodied emissions 15% · 0.06 g

Model scale

Where your estimate sits on the CometWeb grade scale.

We compare the estimate to our own grade bands (A+–F), not an invented “industry median”. The emissions figure comes from the SWDM v4 model; the letter bands are our presentation scale, not an external standard — which is why we do not call them an industry benchmark or a certificate.

  • Emissions from the SWDM v4 model
  • A+–F bands on the CometWeb scale
  • Same methodology on every scan
g CO₂e / pageview · SWDM v4 model, CometWeb grade bands · lower is better
Your site (example) 0.42 g · B
Grade A threshold 0.30 g
Grade A+ threshold 0.10 g

Goal and hosting

Set a reduction goal for a specific URL.

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.

  • Example / configurable per-project goal
  • Green Web Foundation: hosting confirmation
  • Does not mean zero emissions for the whole site
Project goal Example: under 0.5 g CO₂e / pageview

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 audit

From pageview to traffic scale

0.42 g CO₂e / pageview × 500,000 views / mo ≈ 210 kg CO₂e / mo

Scenario under assumed traffic and unchanged model parameters — not an organization emission.

For agencies and freelancers

Built for client digital-footprint measurements

  • Keep each measurement’s model, scope and date
  • Compare the same subpage before and after optimization
  • Export CO₂e, transfer and hosting data
  • Build annual scenarios from client traffic

/ source and retest

Compare estimates in the same context

Record scope, date, transfer and model assumptions, then repeat the measurement after implementation. The website quality benchmark helps separate an observable signal from a conclusion the estimate cannot prove by itself.

Read the website quality benchmark

Find the first source of excess transfer.

Check page weight, cache and estimated emissions, then start with the change that has the highest reduction potential.

No credit card Report with date and sources Free account in the app