The hidden carbon footprint of your website

You recycle. You drive electric, or at least fuel-efficient. You only print when you absolutely have to. But have you ever thought about the carbon footprint of your website?

Probably not. And that makes sense — you can’t see it. No smoke comes out of your laptop. But every time someone visits your site, it uses energy. And for most websites, that energy consumption is many times higher than necessary.

What happens with every click

Every time a visitor opens your website, the following happens:

1. The server receives the request and has to assemble the page (for dynamic sites)
2. The database is queried to retrieve content
3. Dozens of scripts are loaded — plugins, analytics, fonts, widgets
4. Megabytes of data are transmitted via network cables, cell towers and routers
5. The visitor’s device has to process and render all that code

Each of these steps consumes electricity. In data centres, in the network, and on your visitor’s device.

It’s like starting up an entire factory production line every time a customer asks about a product — to make that one thing from scratch. While the product could simply have been sitting ready on the shelf.

The numbers

The average web page produces approximately 0.36 grams of CO2 per pageview. (Website Carbon, 2026) That sounds like very little. But multiply it:

• A site with 1,000 visitors per month: 4.3 kg CO2 per year
• A site with 10,000 visitors per month: 43 kg CO2 per year
• A heavy, unoptimised site can reach up to 1.76 grams per pageview — five times the average

And that’s just your site. Globally, there are nearly 2 billion websites. Data centres now consume 2% of all electricity on earth — and that percentage grows every year. (IEA/IDC-A, 2026)

Why dynamic sites consume so much more

The difference lies in the architecture. A dynamic website (WordPress, Wix, Squarespace) works like this:

• With every visit, the page is reassembled from a database
• Dozens of plugins are loaded — each with their own scripts and external connections
• Heavy frameworks (jQuery, React, Angular) are sent along, even if you don’t use them
• The average dynamic page is 2.5 MB or more of data

A static website works fundamentally differently:

• The page is already prepared as a ready-made file
• There’s no database that needs to be queried
• There are no plugins loading scripts
• An optimised static page is often less than 200 KB — a factor of 12 lighter

That’s the difference between a lorry and a leaflet. The same information, a fraction of the energy.

Why it matters

“It’s just a website.” That’s true — for you alone. But multiply it by millions of businesses all running unnecessarily heavy sites, and you understand the scale.

And it doesn’t just affect the climate. It affects your business too:

Speed. A lighter site loads faster. Faster loading = more customers who stay. Sustainability and conversion are the exact same metric here.

Cost. Less data = less bandwidth = lower hosting costs. A static site on a modern platform costs a fraction of what a WordPress host charges.

Reputation. More and more customers — both consumers and businesses — pay attention to sustainability. A website that demonstrably runs green is a trust signal.

What you can do about it

The most effective way to reduce your website’s carbon footprint isn’t offsetting by planting trees. It’s tackling the source:

• Send less data. Optimise images, remove unnecessary scripts, minimise code.

• Don’t use a database if you don’t need one. 70% of all websites are purely informational — they don’t need a database.

• Distribute green and efficiently.

  Choose a platform that runs on renewable energy and serves data from the ’edge’ — close to the visitor. The shorter the digital path the data travels through network cables and cell towers, the less electricity the network consumes.

• Build static. A site that doesn’t execute server-side code uses virtually no energy when serving pages.

The combination of green hosting and a lightweight static site is the most effective thing you can do. Not offsetting after the fact — preventing at the source.

Curious how your website performs? Try the free website check.