Website carbon footprint calculator

Measures how many bytes one visit to the page transfers and converts that into grams of CO2 per view using the Sustainable Web Design model. You get a grade from A+ to F, how the page compares with the rest of the web, and the heaviest things on it.

Any public page. Try .

Next step

What to do about it

The check found it. These are the ways to fix it, keep it fixed, or run the same check for every business you serve.

Fix it

TagFrog Pro

$75/mo per store

Server-side tracking, consent and every ad platform API, proven with a real test order and kept current. Watch included when it launches.

See TagFrog Pro
Watch this

Watch

Coming soon
$19/mo per site

Re-runs this check every week and emails you the moment the answer changes: site down, tag gone, score dropped, certificate expiring.

Join the waitlist
For agencies

OpsBlu

Territory from $49/mo

This same check, run for every local business in a territory. Leads with a reason to call, as CSV, API and MCP.

Go to opsblu.com

What we check

  • Total bytes transferred for one page view (HTML, CSS, JS, images, fonts)
  • Grams of CO2 per view and per 10,000 monthly visits
  • Grade from A+ to F against the web-wide distribution
  • Whether the host is on a known green-energy provider list
  • The heaviest resources and what they weigh

Cost of one run: 1 fetch + byte count. Results for the same URL are kept for a few minutes, so running twice is free and instant.

Questions

How is the CO2 figure calculated?

Bytes transferred are multiplied by the energy used per gigabyte across data centres, networks and devices, then by the carbon intensity of electricity. It is the Sustainable Web Design model that websitecarbon.com and ecograder use, so numbers are comparable.

What is a good score?

Under about 0.5 g per view is better than most of the web and lands an A. The median page is around 0.8 g. Pages over 2 g are usually carrying uncompressed hero images or video.

What is the fastest way to improve it?

Images. Serve them in WebP or AVIF at the size they are displayed, lazy-load the ones below the fold, and drop any autoplaying video. That alone usually halves the page weight.