Reduce website carbon emissions: 2026 checklist with before/after measurements
- Measure your baseline CO2/page view (Carbon Badge, WebsiteCarbon)
- Switch to green hosting on 100% renewable energy — cuts server carbon 70–90%
- Convert images to WebP/AVIF + add lazy loading — reduces page weight 30–50%
- Audit and remove unused JavaScript (avg. 50% of loaded JS never executes)
- Eliminate non-essential third-party scripts (chat, A/B tools, extra trackers)
- Implement CDN caching to reduce repeated data transfer
- Use system fonts instead of downloaded web fonts where possible
- Re-measure and document the before/after CO2 difference
The internet accounts for roughly 4% of global CO2 emissions in 2026 — comparable to aviation. The difference: website emissions are far more actionable. A handful of targeted changes can cut a site's carbon footprint by 50–80% without degrading the user experience. The steps below include measurement guidance so you can verify actual impact, not just theoretical savings.
Step 0: Establish your baseline (mandatory)
Every other step is guesswork without a baseline. Before changing anything, measure your current CO2/page view:
| Tool | Methodology | What it shows |
|---|---|---|
| Carbon Badge | SWD Model v4 | CO2/page view + hosting energy source |
| WebsiteCarbon.com | SWD Model v4 | CO2/page view + energy label |
| Ecoping | SWD-based | CO2/page view + historical tracking |
| Chrome DevTools | N/A | Page weight (KB) — key proxy metric |
Record: (1) CO2 per page view, (2) total page weight in KB, (3) whether host is flagged green. These three numbers are your benchmark for everything that follows.
The 8 reduction steps — with verified before/after ranges
1Switch to green web hosting
A conventional fossil-fuel host emits ~600g CO2/kWh from its data centre; a 100% renewable host emits near zero. Switching cuts data centre carbon by 70–90%. Check the verified green hosting providers list for options by region and price.
2Convert images to WebP/AVIF
Images account for 50–80% of total page weight on most sites. WebP delivers 25–35% smaller files than JPEG/PNG at equivalent quality; AVIF cuts 40–50%. Tools: Squoosh (free, browser-based), ImageOptim (Mac), or automated via WordPress plugins (Imagify, ShortPixel).
3Add lazy loading to below-fold images
The loading="lazy" attribute on <img> tags prevents browsers from loading images the user may never scroll to. For a page with 10 images, only the 2–3 in the viewport load immediately — the rest wait until needed.
4Audit unused JavaScript
Chrome DevTools → Coverage tab → reload page. The Coverage tool shows what percentage of each JS file actually executes. Industry average: 50–60% of loaded JS runs zero times. Identify the largest unused files and either remove, replace with a lighter library, or defer with async/defer attributes.
5Remove non-essential third-party scripts
Open DevTools → Network tab → filter by domain. Every external script adds page weight, DNS lookups, and connection overhead. Most sites run 15–30 third-party scripts; 5–8 are usually sufficient. Live chat, heatmaps, unused A/B tools, and legacy tracking pixels are common candidates for removal.
6Implement CDN caching
A CDN caches pages on servers geographically close to users. Cached responses skip the origin server, reducing both server compute and data transmission distance. Cloudflare's free tier covers most small/medium sites. The SWD model accounts for CDN use — verified CDN reduces the network transmission carbon component.
7Switch body text to system fonts
Google Fonts and Adobe Fonts add 80–400 KB per page view plus external DNS lookups. System fonts — -apple-system, BlinkMacSystemFont, 'Segoe UI', Helvetica Neue, Arial — load from the user's device with zero data transfer. For headings where brand identity matters, use one font loaded with font-display: swap and subset to only needed characters.
8Re-measure and document results
After completing each step, re-measure CO2/page view with the same tool used for your baseline. Document before/after for each change. This gives you auditable evidence for CSRD Scope 3 reporting, shows which changes had the biggest impact, and lets you embed a Carbon Badge showing your verified progress to site visitors.
Expected impact by step
| Optimisation | Typical CO2 reduction | Effort |
|---|---|---|
| Green hosting switch | 30–50% of total CO2 | Low (1–2 hours) |
| Image WebP conversion | 15–25% of total CO2 | Medium (half day) |
| Lazy loading | 10–20% of initial load | Low (2–4 hours) |
| JS audit + removal | 10–30% of total CO2 | High (1–2 days) |
| 3rd-party script removal | 5–20% of total CO2 | Medium (1 day) |
| CDN implementation | 5–15% of total CO2 | Low (2–4 hours) |
| System fonts | 5–10% of total CO2 | Low (2–4 hours) |
Combined potential: 55–80% reduction from baseline for a site that implements all 7. The internet averages 1.76g CO2/page view in 2026; optimised sites reach under 0.5g.
Priority order: what to do first
If you can only do three things:
- Measure baseline — you cannot manage what you don't measure
- Switch to green hosting — single highest-impact, lowest-effort change
- Optimise images — addresses the largest data transfer source on most sites
Sites that complete only these three typically achieve 50–65% CO2 reduction — enough to cross the 'green' threshold (<0.5g) for most site categories, as shown in our 2026 industry benchmarks.
Get your baseline CO2 score, check your hosting energy source, and see your industry benchmark in seconds.
Check your website carbon footprint →
Frequently Asked Questions
What is the fastest way to reduce website carbon emissions?
Switch to a green web hosting provider on 100% renewable energy. This single change cuts data centre carbon by 70–90% with no code changes needed. Measure baseline first, then re-measure after switching to verify impact.
How much CO2 does an average website emit?
Approximately 1.76g CO2 per page view in 2026 (SWD Model v4). A green, optimised page emits under 0.5g. Heavy e-commerce/media pages reach 4–8g. Multiply by monthly page views for total monthly emissions.
How do I measure website carbon emissions?
Use Carbon Badge, WebsiteCarbon.com, or Ecoping — all implement SWD Model v4. For accurate before/after comparisons, test the same URL and record both page weight (KB) and CO2 score at each stage.
Does image optimisation actually reduce CO2?
Yes. Images are typically 50–80% of page weight. WebP/AVIF conversion reduces sizes 25–50%. Add lazy loading and you typically cut CO2/page view by 15–30% from images alone.
What CO2 target should I aim for?
Under 0.5g CO2/page view for 'green', under 0.3g for excellent. Targets vary by industry — see the 2026 benchmarks by sector.
Related: Website carbon footprint benchmarks 2026 · Best green web hosting providers 2026 · How Carbon Badge works