What Is a Website Carbon Footprint and Why Should You Care?

Ever wondered how much CO₂ your blog generates every time someone reads it? Not a hypothetical. Every page load transfers data across physical infrastructure — servers, cables, routers, mobile towers, screens — all of it powered by electricity, most of which still comes from fossil fuels. The CO₂ released in that process is your website carbon footprint.

It sounds abstract until you run the numbers. The average web page weighs about 2.5 MB. Using the methodology that most carbon tools rely on, that single pageview emits roughly 0.5 grams of CO₂. Multiply that by a site with 10,000 monthly pageviews and you get about 5 kilograms of CO₂ per year — equivalent to driving a petrol car roughly 20 kilometres. Scale that up to a mid-size e-commerce site with 500,000 monthly visits and you are looking at emissions in the hundreds of kilograms annually. From a website.

This is not a fringe concern any more. The internet as a whole consumed an estimated 416 terawatt-hours of electricity in 2023 — comparable to the UK's entire national electricity consumption. Digital infrastructure now accounts for roughly 3.7% of global greenhouse gas emissions, a figure comparable to the entire commercial aviation industry. And unlike air travel, most people have no idea they are contributing to it just by browsing.

Understanding what drives your website's carbon footprint is the first step to doing something about it. Let's get into the mechanics.

How the Internet Actually Emits Carbon

The internet is a physical thing. When you load a webpage, photons travel through fibre-optic cables, radio waves bounce between antennas, and spinning hard drives or solid-state chips retrieve and send your files. All of this requires electricity. And electricity generation — globally — emits CO₂ as a byproduct of burning natural gas, coal, and oil.

The path data takes from server to screen involves three distinct energy-consuming segments. The Sustainable Web Design Model v4 (SWDM v4) — the methodology used by Carbon Badge and most credible carbon tools — breaks them down as follows:

• Data centres: 0.055 kWh per gigabyte — the energy used to store, process, and serve your files from the server side. This includes cooling systems, which account for a surprisingly large share of data centre energy use.
• Network transmission: 0.059 kWh per gigabyte — the electricity consumed by core network equipment, internet exchange points, mobile base stations, and the last-mile infrastructure that delivers data to your users. Mobile networks are significantly less efficient than wired connections per byte.
• End-user devices: 0.080 kWh per gigabyte — the power drawn by laptops, phones, tablets, and desktop monitors to receive, render, and display your content. This is often the largest segment and the one most under-estimated.

Combined, those three segments add up to 0.194 kWh per gigabyte transferred. That is the energy cost of moving one gigabyte of data from server to screen, averaged across the entire global internet infrastructure.

The SWDM v4 Formula: How CO₂ Gets Calculated

Once you have the energy figure, you need to convert it to CO₂. That conversion depends on the carbon intensity of the electricity grid — how many grams of CO₂ are emitted per kilowatt-hour of electricity generated. The world average, based on Ember Climate data, is 494 gCO₂/kWh.

Put it all together and the SWDM v4 formula looks like this:

CO₂ (grams) = page_weight_GB × 0.194 kWh/GB × 494 gCO₂/kWh × (1 − green_factor)

The green_factor is 0.243 if your hosting provider uses verified renewable energy (certified by the Green Web Foundation), and 0 otherwise. In plain terms: switching to a green host gives you a 24.3% automatic reduction in calculated CO₂, without touching a single line of code.

Working through a concrete example: the average web page at 2.5 MB (0.0025 GB):

0.0025 GB × 0.194 × 494 × (1 − 0) = 0.240 gCO₂ per pageview (non-green host)
0.0025 GB × 0.194 × 494 × (1 − 0.243) = 0.181 gCO₂ per pageview (green host)

The real-world average is closer to 0.5g because many popular sites run significantly heavier than 2.5 MB — JavaScript frameworks, unoptimised images, and third-party tracking scripts pile on fast. The deep-dive on SWDM v4 covers the methodology and its assumptions in more detail if you want to understand where those coefficients come from.

Real Numbers: What Does a Website Carbon Footprint Actually Look Like?

Numbers are easier to grasp when they connect to something tangible. Here are a few worked examples at different traffic scales:

A Personal Blog — 500 pageviews/month

At 0.5g CO₂ per pageview (average), that is 250 grams of CO₂ per month, or about 3 kilograms per year. That sounds small — and it is, in isolation. For context, a tree absorbs roughly 21 kilograms of CO₂ per year at maturity. So your blog's annual emissions require about one-seventh of a tree's yearly absorption capacity to offset. Not enormous, but not zero.

A Small Business Website — 10,000 pageviews/month

5,000 grams (5 kg) of CO₂ per month, or approximately 60 kg per year. That is roughly the equivalent of driving a petrol car 240 kilometres. Or one short domestic flight per year — just from people loading your website.

A Mid-Size E-Commerce Site — 500,000 pageviews/month

At 0.5g average: 250 kg CO₂ per month, or 3 tonnes per year. If this site runs heavier pages — say, 1.2g CO₂ each due to unoptimised product images and JavaScript — that climbs to 7.2 tonnes annually. That is the annual carbon footprint of an average European citizen from all sources combined.

A Major News Site — 50 million pageviews/month

At even a below-average 0.3g per pageview: 15,000 kg (15 tonnes) of CO₂ per month, or 180 tonnes per year. The scale changes the calculus entirely. For high-traffic sites, carbon optimisation is not just an environmental act — it is an infrastructure cost problem.

You can measure your own site's actual footprint using the Carbon Badge scanner, which applies SWDM v4 directly and checks your hosting provider's green status automatically.

What Makes a Website Heavy? The Anatomy of Page Weight

Page weight is the primary lever. A lighter page emits less CO₂ — simply because less data needs to travel from server to screen. So what is making pages heavy?

According to HTTPArchive's Web Almanac — which crawls the top 8 million websites monthly — median desktop page weight in 2024 is around 2.3 MB. The breakdown by resource type looks roughly like this:

• Images: ~50% — the single biggest contributor. Uncompressed JPEGs, hero images served at full desktop resolution on mobile, missing lazy loading for below-the-fold content.
• JavaScript: ~25% — the most energy-intensive per byte, because it must be parsed, compiled, and executed by the user's device, not just transferred. A 300 KB JS bundle costs energy in transfer and again in CPU cycles.
• CSS and fonts: ~10% — less impactful in weight terms, but fonts add DNS lookups and potential render-blocking behaviour that increases the energy cost of the first load.
• HTML and data: ~15% — usually the lightest category, though API-heavy single-page apps can push this up significantly.

The practical implication is that image optimisation alone — converting to WebP or AVIF, using responsive srcset attributes, adding loading="lazy" to below-the-fold images — can cut page weight by 30–50% on most sites. That is the biggest single lever available. For the full optimisation playbook, the complete reduction guide covers each technique with real numbers.

Why Businesses Should Care: Four Concrete Reasons

Environmental responsibility is a reason. But if you need to convince a sceptical stakeholder, here are four business-level arguments.

1. CSRD Regulation Is Coming for Digital Emissions

The EU's Corporate Sustainability Reporting Directive (CSRD) entered force in 2024 and phases in reporting requirements for large companies, then mid-size companies, through to 2028. CSRD requires organisations to report on their full environmental impact — including Scope 3 emissions from their supply chain and digital operations. Website emissions sit in Scope 3.

Right now, most companies have no idea what their websites emit. As mandatory ESG reporting expands, that gap becomes a liability. Early adopters who can already report digital carbon metrics — and demonstrate a reduction trajectory — will be ahead of the compliance curve rather than scrambling to catch up.

France went further with its REEN law, which specifically targets digital sobriety for large French companies and public bodies. Similar legislation is being discussed in Germany and the Netherlands. The direction of travel is clear: digital sustainability will become a compliance requirement, not a nice-to-have.

2. Customer Perception Is Shifting

A 2023 Deloitte global survey found that 64% of consumers consider environmental sustainability an important factor in purchasing decisions, up from 49% in 2019. That shift is particularly pronounced among under-40 buyers.

A carbon badge on your website — particularly a grade A or B — is a concrete, verifiable signal. Unlike vague "we care about the planet" statements, it says: here is a specific metric, here is the tool we used, here is the result. That kind of specificity builds trust in a way that marketing copy cannot. The website carbon footprint guide covers what the grades mean and how they are calculated, which is useful context when communicating your score to customers.

3. Carbon Optimisation and SEO Share the Same Levers

This one is underappreciated. Google's Core Web Vitals — which directly influence search rankings — are driven by the same factors that drive carbon emissions. Page weight, JavaScript execution time, render-blocking resources: these are things Lighthouse flags for both performance and SEO reasons. A site that earns a carbon grade A is almost certainly also scoring well on LCP, TBT, and CLS.

In other words, optimising for carbon is optimising for SEO. The two goals are not just compatible — they are largely identical in terms of the technical actions required. A developer who reduces page weight from 3 MB to 800 KB makes the site faster, greener, and more likely to rank. There is no conflict.

4. Lower Page Weight Means Lower Hosting Costs

Many hosting plans charge for bandwidth consumed. A site that transfers 50% less data per pageview (through image optimisation, Brotli compression, and proper caching) pays proportionally less in bandwidth fees. At significant traffic volumes, that saving is real money. A site moving 500 GB per month that reduces to 250 GB through optimisation saves directly on infrastructure costs — while also emitting less CO₂. The economics and the ethics point the same direction.

The Internet's Carbon Problem in Context

The 3.7% of global emissions figure deserves some unpacking, because it is often cited without context.

Commercial aviation accounts for about 2.5% of global CO₂ emissions, though its total climate impact (including contrails and high-altitude effects) is closer to 3.5%. The comparison to the internet is therefore roughly accurate — and deliberately chosen by researchers to make the number feel concrete. Flying across the Atlantic is something people understand as carbon-intensive. Loading websites is not. The numbers say they are in the same league.

The trajectory matters too. Internet traffic roughly doubled between 2018 and 2022, and is projected to double again by 2027. Energy efficiency improvements in hardware are partially offsetting that growth, but not fully. The detailed statistics on internet carbon emissions breaks down the numbers by sector, geography, and projection — useful context if you are building a case internally for sustainability investment.

What is striking is how concentrated the problem is. A relatively small number of high-traffic websites account for a disproportionate share of total internet carbon. The top 10,000 websites by traffic generate more emissions than the bottom 500 million. Optimising a major platform is therefore far more impactful than optimising a personal blog — though both matter.

How to Measure Your Website's Carbon Footprint

Measurement comes before action. You cannot improve what you cannot see.

The Carbon Badge scanner takes a URL and returns a full SWDM v4 analysis: page weight (in KB and GB), CO₂ per pageview in grams, a letter grade from A to F, and whether your hosting provider is verified as renewable by the Green Web Foundation. It takes about 10 seconds and requires no account creation for a one-off scan.

The grade scale works like this:

• A (under 0.15g CO₂) — Excellent. Your page is among the cleanest 10% on the web.
• B (0.15–0.30g) — Good. Better than average, meaningful effort has clearly been made.
• C (0.30–0.50g) — Average. This is where most sites sit. Room for improvement.
• D (0.50–0.75g) — Poor. Your page is heavier than most. Significant optimisation opportunity.
• E (0.75–1.00g) — Bad. This page is in the worst 20% by emissions.
• F (over 1.00g) — Very bad. Immediate attention needed.

For ongoing monitoring — which is where the real value is, since pages change over time — the pro tier allows you to schedule monthly or weekly scans and receive alerts when a deployment pushes a page's score into a worse grade. That kind of automated regression detection is what makes carbon monitoring practically useful rather than just a one-off badge generator.

Pair the Carbon Badge scanner with Google Lighthouse for a complete picture. Lighthouse does not measure carbon directly, but its Performance score correlates strongly with emissions — the same image and JavaScript bloat that drives up CO₂ also drives down your Lighthouse score. Both tools point you toward the same fixes.

What a Good Carbon Footprint Strategy Actually Looks Like

Carbon measurement without action is just a number. Here is what a credible strategy looks like in practice, from someone who has implemented this across multiple sites.

Start with a baseline scan of your most-trafficked pages — not just the homepage. Product pages, blog posts, landing pages. They often differ dramatically in weight. A homepage that scores B might have product pages sitting at D or E due to unoptimised product photography.

Then prioritise by impact. The pages with the most traffic and the worst scores are where optimisation delivers the most total emissions reduction. A 50% weight reduction on a page with 100,000 monthly visits reduces emissions 200x more than the same reduction on a page with 500 monthly visits.

Address images first — they are almost always the biggest lever and the fastest to fix. Then audit JavaScript for dead code and deferrable third-party scripts. Then verify your compression settings (Brotli, not just Gzip). Then check caching headers. Finally, assess your hosting provider's green status.

Set a target grade. If you are at D, target C within three months, B within six. Make it measurable. The SWDM measurement guide explains how to interpret your scores and set realistic improvement targets based on your page type and traffic profile.

Then embed the badge. A visible carbon grade on your site creates accountability — internally, because teams can see the score change with each deployment, and externally, because users can verify the claim themselves. That is what distinguishes a genuine commitment from a marketing statement.

The Bigger Picture

The web was built for communication, knowledge, and commerce. It has delivered on all three at a scale nobody in 1995 could have imagined. But it was not built with energy efficiency as a design constraint, and the accumulated weight of that oversight is now measurable in terawatt-hours and megatonnes of CO₂.

The encouraging part is that most of the fixes are not exotic. Compress your images. Trim your JavaScript. Cache aggressively. Choose a green host. These are good software engineering practices that improve performance, reduce costs, and lower emissions simultaneously. The only thing that has been missing, for most organisations, is the measurement to make the problem visible.

Now you have the measurement. The rest is engineering.