A website feels weightless, but it is not: every single view uses electricity. Data travels from the server across the network to the visitor's device, and each of those steps costs energy. An average page is reckoned at around 0.8 grams of CO2 per view (Website Carbon) — that sounds like nothing, yet it adds up quickly across thousands of visits a month. For a trade business, a law firm or a restaurant the individual contribution is tiny, and still it is worth a look: almost everything that makes a page more climate-friendly also makes it faster and cheaper to run. This article explains, without jargon, why a website causes emissions at all, what pushes the footprint of a page up and which levers bring both down: the data load and the electricity use. And it shows how to present sustainability credibly on your own site without slipping into empty promises.
Why a website causes CO2
Behind every view sits a chain of devices that need power: the server the page lives on, the networks and data centres the data passes through, and finally the phone or computer that displays it all.
Where the electricity is not fully generated from renewable sources, greenhouse gases arise. An average page accounts for around 0.8 grams of CO2 per view (Website Carbon). Taken on its own that is nothing — but at 5,000 visits a month it is already several kilograms a year, and across millions of websites it adds up to a meaningful figure.
Exactly how large the digital share of global emissions is cannot be pinned down to the decimal; common estimates sit around 2 percent of global greenhouse gas emissions (EXPERTE.de) — roughly the order of magnitude of global aviation. A large part of that falls to data centres, which currently use about 1.5 percent of the world's electricity (IEA); with the growth of streaming and compute-heavy applications their power demand could more than double by 2030 in the agency's assessment (IEA). The single business website is a tiny dot in this picture. That is precisely why this is not about saving the world, but about a double benefit: what makes the page lighter almost always makes it faster and cheaper to run as well.
What drives a page's footprint
The electricity use of a view depends above all on one thing: how much data is transferred. The heavier a page, the more bytes travel across the network, the longer processors work and the more energy flows.
And pages have grown markedly heavier over the years: an average page today weighs around 2.5 MB at the median (Web Almanac 2024) — ten years ago it was a fraction of that. Most visits now come from a phone, around 60 percent of web traffic worldwide (Statcounter), often over mobile networks with a limited data allowance. Cutting the data load therefore helps the climate, the speed and the visitor's data allowance at the same time. These factors drive the weight most:
Full-size images
Uncompressed photos are the most common ballast. A single image can weigh more than the entire rest of the page content.
Auto-playing videos
Background videos and embedded clips often load several megabytes before the first line of text is visible.
Too many typefaces
Every embedded font family with several weights loads additional files that delay rendering.
External embeds
Maps, social widgets and chat windows pull in code from third-party servers that nobody in the business controls.
Heavy scripts and trackers
Bulky builder scripts and many counting pixels run on every view and cost processing time.
Server location and power mix
Where the page is hosted and where the electricity comes from help decide how much CO2 falls on each transferred byte.
The media almost always weigh heaviest: on typical business sites images and video make up the largest share of bytes (Web Almanac 2024) — and that is exactly where the biggest lever sits. How to slim images down without visible loss of quality is shown in the article on images on the website; which hidden loads maps, videos and fonts from third-party servers bring along is set out in the article on external content.
Lean delivery: the biggest lever
The most effective step towards a climate-friendly website is at the same time the least spectacular: deliver less and lighter.
A page that arrives at the visitor as finished, static HTML does not have to be assembled from a database on every view. That saves processing time on the server, lowers the amount of data and makes the page faster. Lean, statically delivered pages can reduce the data load considerably compared with a heavy, script-laden build — depending on the starting point, savings of up to 70 percent are possible (EXPERTE.de). Why static delivery also wins on load time along the way is explored in the article on PageSpeed through static websites.
- Slim images down: modern formats, suitable dimensions and compression instead of full-size photos.
- Use media sparingly: start videos only on request and do not load them automatically in the background.
- Review external embeds: load maps, widgets and fonts only where they are genuinely needed.
- Deliver lean: static HTML instead of heavy scripts that recompute on every view.
- Use caching: keep already-loaded files in the browser so follow-up views cost hardly any data.
Scroll table sideways
| Aspect | Heavy, dynamic page | Lean, static page |
|---|---|---|
| Data load per view | Many megabytes from media and scripts | A few hundred kilobytes for the core content |
| Energy per view | Server rebuilds the page every time | Finished page is simply delivered |
| Load time | Noticeable wait, especially on mobile | Page appears almost instantly |
| Server needs | Processing power and a database required | Simple delivery is enough |
| Running costs | Higher through compute load and upkeep | Lower through lean operation |
Climate and speed pull the same way
Images and media: the largest single item
Because images and video make up the lion's share of the data load, the most is decided here. A photo straight from the camera can weigh several megabytes — yet on the page it is often shown only a few hundred pixels wide.
The solution is unspectacular: bring images down to the size actually needed, save them in a modern format and compress them sensibly. That alone takes a substantial part of the weight off many pages without any visible difference. Videos belong only where they genuinely explain something, and should not start automatically. It pays off especially on the phone, where data allowance and reception are limited — what matters for usability on mobile is set out in a separate article.
- Scale images to the size at which they are shown instead of embedding photos at full resolution.
- Use a modern, strongly compressing image format that keeps the file small.
- Load images only when they enter the visible area rather than all of them at once.
- Start videos only on click, not as an automatically playing background element.
- Avoid decorative large images that weigh a lot and say little.
Showing sustainability — without empty promises
A small footprint is a good selling point — but only if it is communicated honestly. Customers increasingly pay attention to who they work with, and a credible approach to sustainability builds trust.
What matters is being able to back it up: anyone advertising the climate advantage of their website should be able to show what they claim. Instead of vague labels like "climate-neutral website", verifiable statements work better — for example the result of a public CO2 calculator for your own site, or a note about renewable electricity in the hosting. Exaggerated or unprovable environmental promises are legally risky and, in case of doubt, damage precisely the trust they were meant to build. How to anchor trust cleanly on a website in the first place is shown in the article on seals, certifications and guarantees.
A lighter website is not a compromise — it loads faster, costs less and uses less electricity. The climate is the bonus, not the price.
Built lean once, economical for good
Green electricity and server location
Alongside the data load a second question comes into play: where does the electricity that delivers the page come from? A server run on renewable electricity causes considerably less CO2 per transferred byte than one on a fossil grid.
For businesses that already value data protection and short paths, hosting in Europe is a natural fit — it keeps the data nearby and can be combined with renewable energy. What matters is that the two complement each other: the cleanest electricity helps little if the page is needlessly heavy, and the leanest page only unfolds its full advantage with an efficiently run server. Both levers together produce a website that draws little power in operation — and keeps the running costs low along the way. How to plan those running costs in the first place is set out in the article on the website budget.
How XICflow delivers lean, climate-friendly pages
With a website, sustainability is rarely a single setting — it sits in many small decisions about the weight of every page.
XICflow takes those decisions on from the outset: every page ships as lean, static HTML, images are generated automatically at a suitable size and in a modern format, and heavy scripts in the background are kept out. Because the finished page is only delivered rather than reassembled on every view, less compute load arises — which lowers the amount of data, the load time and the electricity use in one go. Which building blocks are part of that is shown in the XICflow service overview; how a page is assembled step by step is described in how XICflow works.
Whether a page is genuinely light can be checked without any expertise: a public CO2 calculator shows the weight and the estimated emissions per view, and the result can be shown on your own site with a clear conscience. How finished, lean pages look in practice can be explored in the example sites in the demo gallery, and what the build costs is shown in the pricing overview. So the page stays reliably reachable after launch, a watchful eye on availability belongs with it — what that involves is set out in the article on downtime monitoring.