Nobody sets out to build a heavy website. That’s why your website’s carbon impact starts with one decision at a time.
An image uploaded straight from a camera. A tracking pixel for a campaign that ended in spring. A font weight the designer specified, and nobody used. A chat widget from a trial that lapsed.
How to reduce your website carbon impact
1. What actually creates it
Three components, and they respond to different actions.
- What you send. Every byte transferred crosses a network and gets processed on somebody’s device. This is the largest portion you control directly, and it is governed entirely by what your pages contain.
- What the device does. Parsing, rendering and executing. JavaScript is expensive here, and on an older phone the cost is felt as heat before it registers as delay.
- Where it is hosted. Servers draw power continuously. Renewable-powered hosting changes the emissions profile of this portion, and it is commonly estimated as the minority share, though the figure varies by methodology and provider.
Design and development govern the first two. Hosting governs the third. Treating hosting as the whole answer, which is the most common shortcut in this market, leaves the majority untouched.
2. The Agnikii Green Performance Method, in order of return
- Measure first. Page weight, request count and Core Web Vitals on your most-visited pages under recorded conditions, plus a carbon estimate from the same pages with a named tool. Without a baseline, you can assert an improvement but not demonstrate one.
- Images. Display dimensions, modern formats, lazy loading below the fold, no autoplay video. Largest single win on almost every site and no design compromise required.
- Third-party scripts. List every external domain your page connects to and find an owner for each. The unclaimed ones are free to remove.
- Fonts. Two families at most, subset to the characters you use.
- Code. Audit dependencies, prefer browser-native solutions, ship less JavaScript. Most effort, so last.
- Content. Archive expired campaigns and consolidate duplication, checking accessibility and record-keeping needs before removing anything.
Re-measure after each step so you know what earned the improvement rather than guessing.
3. Hosting, checked properly
The Green Web Foundation’s hosting check tells you whether your provider appears in its directory of hosts claiming renewable power.
Treat that as a starting point rather than verification. Directory inclusion reflects a claim, and claims vary in rigour. If hosting features in anything you publish, ask the provider what their claim actually covers.
Stop the page weight from creeping back.
This is the step that determines whether any of the above lasts.
Set a page weight budget and enforce it in your build process rather than relying on somebody to check. Give new third-party tools an owner and a review date. Give editors guidance on image sizes, since most regression arrives through the content management system rather than the codebase.
Review quarterly against the baseline. A one-off clean-up buys about a year.
What it is reasonable to expect
A faster website, reliably. Where performance and environmental impact both apply, treat them as the same lever: reducing unnecessary data transfer and processing supports a faster experience while lowering estimated digital carbon, though environmental figures remain modelled rather than directly measured.
Faster pages tend to hold attention better, which is a reasonable expectation rather than a guarantee, and the effect varies with audience and starting point.
What nobody can promise is a ranking improvement from weight reduction alone, or a precise carbon figure. Both claims appear regularly in this market and neither survives examination.
Our website sustainability audits produce the baseline and the prioritised list that follows from it.