Website carbon footprint benchmarks 2026: what counts as 'green' by industry

Updated April 2026 · 13 min read · By the Carbon Badge team

The concept of a "green website" has existed for years, but 2026 is the first year where it has real regulatory teeth. The EU's Corporate Sustainability Reporting Directive now requires Scope 3 emissions disclosure for larger companies — and digital infrastructure, including websites, falls squarely in that scope. Thousands of companies are measuring their website carbon for the first time this year, often discovering numbers that surprise them.

But measuring against the global average misses the point. A news site and a static portfolio page serve fundamentally different purposes and have structurally different carbon profiles. The right benchmark is your industry peer group — and then the top 10% of that group as your target.

Here are the 2026 benchmarks, methodology, and the fastest paths to getting below your sector's "green" threshold.

2026 Website Carbon Benchmarks by Industry

Industry	Avg CO₂/page view	"Green" threshold	Worst offenders
Blogs / editorial	0.8g	<0.3g	Video-heavy, unoptimised images
E-commerce	2.4g	<1.0g	Product image carousels, ad tech
SaaS / tech tools	1.2g	<0.5g	Live chat widgets, heavy JS frameworks
Media / news	3.1g	<1.5g	Auto-play video ads, real-time feeds
Financial services	1.0g	<0.4g	Heavy JS dashboards, fraud scripts
Healthcare	0.9g	<0.4g	Cookie consent overlays, portal JS
B2B services	0.7g	<0.3g	Marketing video embeds, chatbots
Non-profit / education	0.5g	<0.2g	Donation platform iframes, maps

Benchmarks based on analysis of 50,000+ URLs using the Sustainable Web Design Model v4. "Green" threshold = top 10% for each sector.

How These Benchmarks Are Calculated

The Sustainable Web Design (SWD) model, now in version 4, is the methodology underlying most reputable website carbon calculators including Carbon Badge, WebsiteCarbon.com, and Ecoping. It calculates emissions from three components:

Data transfer energy: The total page weight — every byte of HTML, CSS, JavaScript, images, fonts, video, and third-party resources — multiplied by the energy intensity of internet transmission infrastructure (approximately 0.06 kWh per GB after CDN caching adjustment).

Data centre energy: Server-side energy consumption based on the hosting provider's infrastructure. This is where the renewable energy mix of your hosting provider has the most direct impact. A host running on 100% renewable energy contributes near-zero carbon from this component.

End-user device energy: The energy consumed by the visitor's browser and device rendering the page. This component scales with page complexity — JavaScript-heavy pages require significantly more CPU processing than simple HTML pages.

The model produces a result in grams of CO₂ equivalent (g CO₂e) per page view, accounting for a global average electricity carbon intensity. If your hosting is on renewable energy, the calculation adjusts accordingly.

Why Media and News Sites Are the Worst Offenders

Media and news sites average 3.1g CO₂ per page view in 2026 — more than six times the emissions of a well-optimised SaaS page. The drivers are structural:

Auto-play video: A single embedded video player loads 2–4 MB of resources before the user even sees the first frame. Many news sites load video assets on every article page regardless of whether the article contains video content, because the player is part of the template.

Ad tech cascade: Programmatic advertising triggers a cascade of JavaScript requests from dozens of third-party domains. An average news page makes 80–120 external requests for advertising alone. Each request adds latency, data, and energy consumption.

Real-time content systems: Breaking news tickers, comment systems, and push notification infrastructure maintain persistent connections that keep consuming resources even when the page is idle.

Unoptimised images at scale: A typical news homepage loads 15–25 article thumbnail images plus a large hero image. Many sites serve the same oversized source image to both mobile and desktop users, because responsive image infrastructure was never implemented properly.

The path to the "green" threshold for a news site (under 1.5g) requires: eliminating auto-play video (or replacing it with a poster image that loads the player only on click), reducing programmatic ad stack complexity, lazy-loading images with proper responsive sizing, and reviewing whether all real-time features are genuinely serving user needs or just adding carbon without corresponding value.

E-Commerce: Where Carbon Meets Revenue

E-commerce sites average 2.4g CO₂ per page view, and the primary driver is product imagery. A standard product page loads 8–15 product photos at various angles, zoom levels, and lifestyle contexts. Product listing pages display 24–60 thumbnails, many of which are loaded regardless of whether the user ever scrolls to them.

The good news: the interventions that reduce e-commerce carbon footprint are the same interventions that improve page performance and conversion rates. Faster pages load more reliably on mobile, convert better, and have lower bounce rates. This is one of the rare cases where the business case and the environmental case align perfectly.

Optimisation	Carbon saving	Also improves
Convert product images to WebP/AVIF	~35% reduction	Page load speed, Core Web Vitals
Implement lazy loading for product images	~20% reduction	Initial page load time
Reduce ad/tracking scripts to essential only	~15% reduction	Privacy, page speed
Switch to green hosting	~70–90% of server carbon	CSRD Scope 3 reporting
Implement responsive images (srcset)	~25% reduction mobile	Mobile conversion rate

SaaS and Tech Tools: Leading But Not Enough

SaaS and tech tool sites average 1.2g CO₂ per page view — better than most sectors but still above the "green" threshold of 0.5g for this category. The gap is explained by specific patterns common in SaaS marketing sites:

Live chat widgets: Intercom, Drift, Zendesk Chat, and similar tools load 300–600 KB of JavaScript on every page view, maintain persistent WebSocket connections, and contact external servers continuously. For a SaaS site with modest traffic, the cumulative carbon impact of a live chat widget can exceed the carbon cost of all static content combined.

Heavy JavaScript frameworks: Marketing sites built on Next.js, Nuxt, or similar frameworks often ship much more JavaScript than a static site needs. A company blog or pricing page served as static HTML with minimal JS can be 80% lighter than the same content served through a full React application.

Video backgrounds and demo videos: Auto-playing product demo videos on landing pages are common in SaaS. Each visitor to a homepage with an auto-playing video receives that video's full data transfer before they have indicated any interest in watching it.

Financial Services: Invisible Heaviness

Financial services websites average 1.0g per page view — higher than their clean visual design might suggest. The culprit is not images but JavaScript. Financial service pages carry:

• Fraud detection and behavioural analytics scripts (PerimeterX, Akamai Bot Manager, etc.)
• Regulatory compliance overlays and cookie consent frameworks
• Client-side loan calculators, currency converters, and portfolio tools
• Multiple A/B testing platforms running simultaneously
• Live market data feeds and ticker widgets

To reach the "green" threshold of under 0.4g, financial services sites need to: audit and consolidate their JavaScript inventory (three analytics tools is two too many), defer non-critical scripts until after interaction, replace heavy calculation libraries with lightweight alternatives, and review whether live data features are genuinely adding user value on every page or just on specific pages that actually need them.

Healthcare: The Cookie Consent Carbon Tax

Healthcare websites average 0.9g per page view. The somewhat surprising finding from our dataset is that cookie consent overlays contribute meaningfully to this figure. Healthcare sites typically run extensive consent management platforms due to HIPAA, GDPR, and ePrivacy requirements. These consent platforms load 150–400 KB of JavaScript before any page content, and they block rendering while they execute.

The fix is not to skip consent management — it is to choose a lightweight consent management platform designed for performance and to cache consent decisions properly so returning visitors do not re-download the full consent framework on every page.

How to Get Below Your Industry's "Green" Threshold

Regardless of your sector, the fastest paths to reducing website carbon follow the same prioritisation:

1. Switch to verified green hosting (biggest immediate impact)

Switching your hosting provider to one running on 100% renewable energy eliminates 70–90% of your site's data centre carbon component. The Green Web Foundation directory lists verified providers. This is a one-time infrastructure change with no negative impact on your site's content or performance.

2. Audit and eliminate unused JavaScript

Open Chrome DevTools, run Coverage analysis, and look at what percentage of your loaded JavaScript is actually executed. Industry average is 50–60% unused code — you are downloading, parsing, and executing JavaScript that serves no user. Remove unused libraries, replace heavy frameworks with lighter alternatives where possible, and defer third-party scripts that are not critical to page rendering.

3. Optimise images

Convert all images to WebP (or AVIF for highest compression). Implement srcset so mobile users receive appropriately sized images. Lazy-load all images below the fold — only the viewport content should load on page open. Run your image library through Squoosh or Imagemin before upload. For most sites, images account for 50–80% of total page weight.

4. Remove non-essential third-party scripts

Audit every third-party script on your site. List what it does, who requested it, whether it is still active, and what it costs in page weight and connection overhead. A typical site runs 15–30 third-party scripts; 5–8 are usually sufficient. Remove duplicates, consolidate analytics platforms, and eliminate tools that are no longer actively used.

5. Consider system fonts

Custom web fonts (Google Fonts, Typekit) add 80–400 KB of data transfer per page and require external DNS lookups. System fonts (Arial, Georgia, Helvetica, -apple-system) load from the user's device with zero data transfer. For body text especially, system fonts often improve perceived performance without meaningful design regression.

CSRD and Website Carbon: What's Changing in 2026

The EU Corporate Sustainability Reporting Directive (CSRD) requires companies to disclose Scope 3 emissions starting with fiscal year 2025 reports. Digital infrastructure — including websites, cloud services, and SaaS tools — falls under Scope 3 Category 1 (purchased goods and services).

This means companies subject to CSRD need a methodology for measuring and reporting their website's carbon footprint as part of their annual sustainability disclosure. The Carbon Badge calculator, which implements the SWD Model v4, provides the metrics and methodology documentation needed for CSRD-aligned reporting.

If you are not yet in scope for CSRD (mandatory for large companies from 2025, expanding to listed SMEs from 2026 onwards), measuring now gives you baseline data before the requirement kicks in — which is always the preferred position for auditors.

Frequently Asked Questions

Related: Best green web hosting providers 2026 · How to reduce your website's carbon footprint: 7 steps