Every page you load consumes electricity. On a server, across the network, and above all on your visitor's device. "Website carbon" is that consumption translated into grams of CO₂. Good news: the levers that bring it down are the same ones that make a site fast.
What exactly is website carbon?
A web page doesn't display itself. Data leaves a data centre, crosses a network, and arrives on a phone or a computer, which then has to decode it and render it. Every step consumes energy, and that energy has a carbon intensity.
Website carbon estimates that energy and converts it into grams of CO₂ equivalent per page view. It's an estimate, not a sensor reading. But it's robust enough to compare two versions of the same page and see whether you're making progress.
The reference model is called the Sustainable Web Design Model (SWDM). Version 4 splits the system into three segments: data centres (22% of the energy), networks (24%) and user devices (54%). Worth remembering: more than half the impact happens on your visitor's device, not in your hosting.
Four figures to put it in perspective
- 0.36 g | CO₂e on average per page view (SWDM v4 model)
- 2.6 MB | median weight of a mobile page in 2025
- +203% | growth in mobile page weight since 2015
- 4.4% | digital's share of France's emissions (ADEME)
A sense of scale
A site with 10,000 page views a month emits roughly 43 kg of CO₂e a year at the average rate. That's not a Brussels–New York return flight. But multiply it by the millions of sites online, add the manufacturing of devices 60% of a device's environmental impact comes from its production, not its use and the total becomes significant. In France, ADEME estimates that the footprint of digital could triple by 2050 if nothing changes.
Why sites keep getting heavier
The median weight of a mobile page has tripled in ten years. Here's where the bytes go today:
Median weight by resource type on mobile (Web Almanac 2025)
Resource | Median weight (mobile) Images | 911 KB
JavaScript | 632 KB
Fonts | 122 KB
CSS | 77 KB
HTML | 22 KB
Two culprits stand out: images and JavaScript. On a median desktop page, roughly 280 KB of JavaScript is downloaded and then never executed. That's dead weight, paid for by your visitors' battery and data plan.
Eight simple actions, in order of payoff
- Compress and resize your images
This is the first lever, by a wide margin. Serve your images as AVIF or WebP, at the right dimensions (not a 3000 px image displayed in a 600 px block), with srcset to match the size to the screen. On a typical brochure site, you'll often cut the weight of your visuals by three or four with no visible difference. - Turn on lazy loading
A simple loading="lazy" on images and iframes below the fold. What isn't seen isn't downloaded. Just don't apply it to the page's main image, which needs to stay a priority. - Clear out the third-party scripts
Live chat, ad pixels, interactive maps, duplicate analytics tools, an oversized cookie banner: list everything that loads and ask yourself what actually earns its place. Every third-party script adds requests, weight and often connections to other domains. A lightweight, privacy-friendly analytics tool weighs a few kilobytes where others weigh hundreds. - Limit your fonts and self-host them
Two font families maximum, two or three weights, in WOFF2, served from your own domain with font-display: swap. And ask yourself the question: a system font stack costs zero bytes and displays instantly. - Move to a host running on renewable energy
It won't reduce the weight of your pages, but it does reduce the carbon intensity of the server side. The Green Web Foundation directory lets you check in one search whether your current host is listed. Check where your servers sit, too: the closer to your visitors, the less network travel. - Cache properly
Long cache headers on your static assets, a CDN if your audience is international, and Brotli compression enabled server-side. A returning visitor should re-download almost nothing. - Keep video under control
Video is the heaviest item on the web. No autoplay, no decorative background video on loop, a clickable thumbnail rather than an embedded player loaded by default. And serve the resolution that matches the display size, not 4K in a 400 px frame. - Delete pages
The most overlooked lever. Obsolete pages, articles nobody reads, 12 MB PDFs dating from 2019: all of it is stored, backed up, indexed. An annual content clear-out lightens the site, improves navigation and concentrates your SEO authority on the pages that matter.
What you actually gain
This is where eco-design becomes easy to defend internally: nearly every benefit is immediate and measurable.
- A faster site. Fewer bytes and fewer requests mean mechanically better Core Web Vitals. LCP and INP improve most on mobile and on average connections.
- Better search visibility. Google uses page experience signals in its rankings. A lightweight site is also easier for crawlers to explore — including those of generative engines.
- More conversions. Every second of waiting costs you visitors. That has always been true, and it's truer still on mobile.
- A more inclusive site. Not everyone has fibre and a recent phone. A lightweight page works on the train, in rural areas, on a five-year-old device.
- Lower infrastructure costs. Less bandwidth, less storage, less server power needed.
- A real sustainability argument. Not greenwashing: a figure before, a figure after, a public methodology. Anyone can verify it.
- A regulatory head start. In France, the RGESN published by Arcep in May 2024 sets out 78 eco-design criteria across 9 themes. It's voluntary today, but it already shapes public tenders.
The trap to avoid: offsetting without reducing. Buying carbon credits for an 8 MB site that takes six seconds to load solves neither the environmental problem nor the experience problem. Reduce first, communicate second.
Where to start this week
- Measure. Run your homepage and your two most-visited pages through a calculator like Website Carbon, and note the result. Add a Lighthouse or PageSpeed Insights audit.
- See where the weight comes from. Open your browser's Network tab and sort by size, largest first. The top three rows will tell you what to do.
- Deal with images and third-party scripts. In 80% of cases, those two jobs alone are enough to move a site into a good grade.
- Measure again and keep a record. A very simple table: date, page weight, grams of CO₂e. That's your proof of progress, and excellent material to publish.
Web eco-design is not an aesthetic sacrifice. The leanest sites I come across are often the cleanest to look at and the most pleasant to use. A useful constraint, in short.
Sources