How to Reduce Your Website's Carbon Footprint: 12 Practical Steps

Q: What is the average carbon footprint of a website?

The average web page produces 0.5g CO2 per page view, according to the Website Carbon Calculator 2024 data. Pages with heavy video, large unoptimized images, or excessive JavaScript produce 2-8g per view. A website with 10,000 monthly visitors and 3 pages per session generates approximately 150kg CO2/year — equivalent to driving 370 miles. High-traffic e-commerce sites can emit 5-10 tonnes CO2/year.

Q: Does switching to green hosting actually reduce carbon?

Yes, but with important caveats. Green hosting providers use renewable energy for data center operations, which is the largest single source of website carbon emissions. Switching from conventional to verified renewable hosting can reduce server-side carbon by 70-90%. However, user devices (running browsers to view your site) account for 50-70% of total website carbon — green hosting alone addresses only the server portion.

Q: How do images affect website carbon footprint?

Images account for 50-80% of web page weight for media-heavy sites, making them the largest optimization target. Converting JPEG/PNG to WebP reduces file size 25-35% with identical visual quality. Converting to AVIF reduces size 50-60% versus JPEG. Implementing lazy loading prevents off-screen images from loading — saving bandwidth (and carbon) for content users never scroll to see. A page reducing image weight from 2MB to 500KB cuts per-view carbon emissions by 35-40%.

12 steps to cut your website's CO2 emissions 40-80%. The most impactful changes — switching to green hosting, optimizing images, and enabling aggressive caching — require no visual redesign and most can be implemented within a week. Start with the highest-impact items: hosting switch (potential 70-90% server-side reduction) and image optimization (30-40% total page weight reduction).

Green data center with renewable energy wind turbines in background

Steps 1-4: The High-Impact Changes (Do These First)

Switch to verified green hosting — Server energy is the largest controllable carbon source. Move to a host with verified renewable energy (Green Web Foundation directory, not just "carbon neutral" marketing claims). Top verified providers in 2026: Infomaniak (Swiss, 100% hydro), GreenGeeks (wind energy RECs), Hetzner (Germany, 100% renewable), Cloudflare (Edge Network running on 100% renewable since 2021).
Convert images to WebP or AVIF — Images are 50-80% of page weight on media-heavy sites. WebP saves 25-35% vs JPEG at equivalent quality. AVIF saves 50-60%. Use Squoosh, Cloudflare Image Resizing, or server-side conversion tools. Set up format negotiation: serve AVIF to supporting browsers, WebP as fallback, JPEG/PNG as last resort.
Implement lazy loading for images and videos — Native loading="lazy" on image tags prevents off-screen content from loading until needed. For videos, replace YouTube/Vimeo embeds with a static thumbnail and load the player only on click. A page with 15 images below the fold saves 70-85% of those images' transfer weight per average visitor session.
Enable aggressive caching via CDN — Static assets (CSS, JS, fonts, images) cached at edge locations near users reduce both server load and data transfer distance. Set Cache-Control headers with long max-age values for versioned assets. Cloudflare free tier or AWS CloudFront handle this for most sites. CDN caching reduces server energy consumption 60-80% for returning visitors.

Steps 5-8: The Performance Layer

Eliminate render-blocking JavaScript — Unused JavaScript is the second-largest carbon waste category after unoptimized images. Run a Lighthouse performance audit and remove or defer scripts that aren't used on the current page. Third-party tag bloat (analytics, chatbots, advertising scripts) often adds 200-500KB of JavaScript that users download but don't benefit from.
Use system fonts instead of web fonts — Each web font file is 50-300KB downloaded per new visitor. System font stacks (Arial, Helvetica, Georgia, system-ui) have zero download weight. If brand fonts are required, subset them to only the characters used and limit to 1-2 font families maximum.
Reduce DOM complexity — Deeply nested HTML requires more processing energy on user devices. Simplify DOM structure where possible. Target under 1,500 DOM elements per page. Remove legacy CSS frameworks that add unused utility classes.
Implement server-side rendering or static generation — Single Page Applications (SPAs) with heavy client-side JavaScript generate 3-5x more device energy than server-rendered pages. Static HTML pages are the lowest-carbon option. For CMS-driven sites, pre-generate static HTML where content changes infrequently.

Steps 9-12: The Carbon-Aware Optimizations

Host in the user's geographic region — Data transferred shorter distances uses less network energy. If 60% of your users are in Europe, host your origin server in Europe rather than US-East. Use CDN edge nodes to serve other regions from cache.
Optimize for Core Web Vitals — Google's Core Web Vitals correlate with page efficiency: fast LCP means less processing time, low CLS means fewer repaints, good INP means efficient JavaScript execution. Improving CWV reduces device energy consumption 15-25%.
Audit and remove unused pages — Every indexed page is crawled by search engines monthly. Pages with zero organic traffic consume crawl budget and server resources. Use Google Search Console to identify pages with no clicks in 12 months and either consolidate, redirect, or remove them.
Monitor with Website Carbon Calculator — Establish a baseline carbon score, implement changes, and measure improvement. Target under 0.09g CO2 per page view (the "cleaner than 90% of websites" threshold). Publish your score with a carbon badge to demonstrate commitment and build user trust.

Expected Results by Category

Optimization	Carbon Reduction	Implementation Effort
Green hosting switch	70-90% server-side	Low (1-2 days)
Image optimization (WebP/AVIF + lazy load)	30-40% total page	Low-Medium (1-5 days)
JavaScript audit + removal	10-20% total page	Medium (1-2 weeks)
CDN + caching optimization	15-25% total transfer	Low (hours)
Video load optimization	20-60% (video-heavy sites)	Low (hours)

Measure your current score at our website carbon footprint calculator, then compare green hosting options in our green hosting guide.

FAQ

What is the average carbon footprint of a website?

0.5g CO2 per page view on average. Heavy video/image sites produce 2-8g. A site with 10,000 monthly visitors generates ~150kg CO2/year.

Does switching to green hosting actually reduce carbon?

Yes — 70-90% server-side reduction. But devices browsing your site account for 50-70% of total emissions, so hosting alone isn't enough.

How do images affect website carbon footprint?

Images are 50-80% of page weight. Converting to WebP/AVIF + lazy loading cuts 35-40% of per-view carbon. The highest single-action impact after hosting.