What Is a Website's Carbon Footprint, and How to Measure & Reduce It

The internet feels weightless, but it runs on electricity — and electricity still has a carbon cost. Every time someone loads a page, energy is consumed in data centres, across networks, and on the visitor's device, producing a small amount of greenhouse gas. Multiplied across the billions of page views happening right now, the web's footprint is significant. This guide explains what a website's carbon footprint is, how it is measured, and the most effective, practical ways to make your site lighter and greener — which, happily, also makes it faster.

It overlaps closely with performance, so it pairs naturally with Core Web Vitals explained.

Why websites have a carbon footprint

A website's emissions come from the energy used at every stage of delivering it. Data centres run the servers that store and process your site, drawing electricity to compute and to stay cool. Networks — the routers, cables and cell towers between the server and the user — consume energy moving the data. And the visitor's device uses power to download, render and display the page. Because much of the world's electricity is still generated partly from fossil fuels, all of that energy translates into carbon emissions. The more data a page sends and the more work it asks devices to do, the more energy it uses, and the larger its footprint. In short: heavier, busier pages emit more than lean ones.

How big is it, really?

The numbers surprise people. According to the Website Carbon Calculator (built by Wholegrain Digital), the average web page produces around 4.61 grams of CO2 per page view. That sounds tiny until you scale it: a site averaging 10,000 page views a month emits on the order of half a tonne of CO2 a year — and large sites with millions of views emit far more. The footprint is also unevenly distributed: a bloated, media-heavy page can emit many times more than a lean one, which means the difference between a thoughtfully built site and a careless one is substantial in aggregate. Small per-view savings, multiplied across a site's traffic and lifetime, add up to real reductions.

How a website's carbon footprint is measured

Carbon calculators do not measure emissions directly; they estimate them from a model with a few key inputs. The first and most important is page weight — how many kilobytes the page transfers, which the tool measures by loading the page like a browser. The second is the energy intensity of moving and processing that data through the system. The third is the carbon intensity of the electricity involved, which depends on the energy grid. And the fourth is whether the hosting is powered by renewable energy, which can substantially lower the figure. Combine these and the tool produces a CO2-per-view estimate, often with a rating and tips. Different calculators use slightly different models, so treat the exact gram figure as an informed estimate and focus on the trend and the relative comparison rather than a single precise number.

Tools to measure it

Several free tools make this easy. The Website Carbon Calculator gives a quick per-view estimate and a clean/dirty rating for any URL. Ecograder (by Mightybytes) produces a score out of 100 with a detailed report covering performance, efficiency and user experience as well as emissions. Digital Beacon breaks down the footprint by first visit versus repeat visit and by the resources that contribute most. The Green Web Foundation maintains a check for whether a site is hosted on green (renewable) energy. Broader site audits, StackOptic among them, fold a carbon or efficiency estimate into a wider report so you can see it alongside performance, SEO and security rather than as a standalone number.

How to reduce your website's carbon footprint

Because page weight is the dominant driver, most of the highest-impact reductions are the same moves that make a site fast.

Optimise images, which are usually the largest contributor. Compress them, size them correctly for their display dimensions, use modern formats (WebP, AVIF), and lazy-load images below the fold so they only download when needed.

Tame video and animation. Video is enormously heavy; avoid autoplay, do not use video purely as decoration, and host it efficiently. The same caution applies to large animated assets.

Trim and defer JavaScript. Excess JavaScript is heavy to download and expensive to run on the device, costing energy at both ends. Ship less, code-split, defer the non-critical, and audit third-party scripts ruthlessly — they are a common source of bloat.

Subset and limit fonts. Each custom font weight is a download; use modern formats (woff2), subset to the characters you need, and avoid loading many weights you barely use.

Cache aggressively and use a CDN. Effective caching means repeat visitors re-download far less, and a CDN serves data from closer to the user, reducing the energy spent moving it. Repeat-visit footprint can be a fraction of the first visit when caching is done well.

Write efficient code and queries. Server-side efficiency matters too — fewer, faster database queries and less wasted computation mean less energy per request.

Green hosting and renewable energy

Where your site is hosted changes its footprint even before you optimise a byte. Hosting that runs on renewable energy — or providers that match their consumption with renewable purchases — substantially lowers the carbon intensity of the electricity behind every page view. Many cloud and specialist hosts now publish their renewable commitments, and the Green Web Foundation's directory lets you check whether a given host is recognised as green. Switching to a green host is one of the few footprint reductions you can make without touching your code at all, and it compounds with every optimisation you layer on top.

The performance and SEO overlap

Here is the part that makes sustainability an easy sell internally: the work that reduces carbon is almost exactly the work that improves performance. Lighter pages, optimised images, less JavaScript, good caching and fast hosting all reduce emissions and improve Core Web Vitals, which improves user experience and feeds Google's page-experience signals. So a carbon-reduction project doubles as a performance and SEO project, and a performance project doubles as a sustainability win. You rarely have to choose between them — optimise for one and you advance all three, which makes the business case straightforward even for teams without a green mandate.

Why it matters beyond the environment

The environmental case stands on its own, but there are practical reasons too. Brand and values: a measurably efficient, low-carbon site signals genuine commitment to customers and staff who increasingly care. ESG and reporting: digital emissions are part of an organisation's overall footprint and are starting to feature in sustainability reporting. User experience and cost: lighter sites load faster, work better on slow connections and older devices, and can cost less to serve. And regulation and expectations around digital sustainability are only tightening. Reducing your footprint is increasingly something to do because it is good practice on several fronts at once, not only because it is the right thing to do.

Common mistakes and greenwashing

A few pitfalls are worth avoiding. Treating one calculator's gram figure as gospel — models differ, so use the number to track direction and compare, not as an exact truth. Carbon offsetting without reducing — buying offsets while shipping a bloated site is the digital version of greenwashing; reduce first, then consider offsets for the remainder. Optimising the homepage only — emissions come from all your traffic, so the heavy template behind thousands of deep pages may matter more than the homepage. And the dark-mode myth — switching to a dark theme saves a little energy only on certain (OLED) screens and is no substitute for cutting page weight. Honest reduction beats cosmetic gestures every time.

Where to start if you only do one thing

If the full list feels like a lot, start with images, because they are the single largest contributor to page weight on most sites and the easiest to fix without touching functionality. Run your heaviest pages through a calculator, find the images that dominate the transfer, and compress them, size them correctly and convert them to a modern format. That one pass typically removes a large share of a page's weight — cutting its carbon and speeding it up — for very little effort and no design compromise. Once images are handled, the next-best single move for most sites is auditing third-party scripts, which quietly add weight and energy cost out of all proportion to the value many of them provide. Two focused afternoons on images and third parties will take most sites a long way, and they are a far better use of time than chasing marginal gains elsewhere before the obvious wins are banked.

A quick checklist

• Measure your footprint with a calculator and note the page weight.
• Optimise and lazy-load images; use modern formats.
• Remove autoplay video and decorative heavy media.
• Trim, defer and code-split JavaScript; audit third-party scripts.
• Subset fonts and limit weights.
• Cache well and serve via a CDN.
• Host on renewable energy and verify it.
• Re-measure, and check the deeper pages, not just the homepage.

Go deeper

• The performance twin: Core Web Vitals explained.
• Fonts and weight: how to find what fonts and colours a website uses.
• The full picture: how to find out what a website is built with.

Want your site's efficiency measured alongside performance, SEO and security? Analyse any URL with StackOptic — one report, free, no sign-up.