A Lighter, Lower-Carbon Website: A Practical Guide
A lighter website loads faster, costs visitors less mobile data and asks less of servers, networks and phones. W3C now publishes guidelines for building sites with that in mind. This guide covers what those guidelines are, where most of a page's weight comes from, and the practical changes that make a business site lighter, without inventing carbon figures nobody can check. Checked on 5 November 2026.
What the W3C guidelines are
The Web Sustainability Guidelines (WSG) come from W3C's Sustainable Web Interest Group. They "provide actionable recommendations to help digital teams make informed, sustainable decisions", and cover user experience design, web development, hosting and infrastructure, and business and product strategy. Each guideline has success criteria you can test against.
Check the status before you lean on them. The current version is a W3C Group Note Draft dated 16 October 2026, and W3C states that "Group Note Drafts are not endorsed by W3C nor its Members" and that "this is a draft document and may be updated, replaced, or obsoleted by other documents at any time." The WSG is a useful checklist written by practitioners. It is not a W3C standard or a legal requirement, and the conformance section is marked as a work in progress.
The guidelines also say "pragmatism and progress over perfection should be considered paramount". Most of their web development advice is the same work that makes a site fast, so you can start with speed and get the sustainability gain with it.
How heavy pages are
The HTTP Archive measures millions of pages each year. Its 2024 Web Almanac page weight chapter reports that in October 2024 the median desktop page weighed 2,652 KB and the median mobile page 2,311 KB, both up from 2022. The same chapter found that JavaScript had overtaken images as the most requested file type, with the median page loading 24 JavaScript files on desktop and 22 on mobile.
Google's Lighthouse documentation says "large network payloads are highly correlated with long load times" and that "they also cost users money", for example on mobile data. It advises: "Aim to keep your total byte size below 1,600 KiB." Lighthouse flags pages whose requests add up to more than 5,000 KiB. You can see the total for any page in Chrome DevTools or in a Lighthouse report, which is a better starting point than any estimate.
Why we do not quote a CO2 number
Website carbon calculators give a grams-per-visit figure, and it is tempting to put one in a report. The 2024 Web Almanac sustainability chapter explains why to be careful. Many calculators use the Sustainable Web Design Model, which "uses data transfer as a proxy", and the authors write that "accurately estimating impacts is still an important topic and no consensus has been reached yet." When the model was updated, the chapter's authors had to recalculate their 2022 results.
Data transfer also misses part of the picture. The same chapter notes that JavaScript is "usually quite impactful on memory, CPU, and GPU", which the model does not yet count, and that this can shorten the life of older phones. The WSG itself lists data gaps and warns against "carbon tunnel vision" that ignores e-waste and water use. So measure what you can measure exactly, such as page weight, number of requests and third-party scripts, and treat any CO2 figure as a rough estimate tied to a named model and date.
Images, video and fonts
Media is usually the easiest place to save weight. WSG guideline 2.9 starts with "include media only when it supports user needs", then asks for media resized and compressed for different screens, lazy loading, and playback the user controls. In practice:
- Size images for their slot. web.dev's image performance course shows how
srcsetandsizeslet the browser pick the right file, and says "WebP and AVIF may provide better compression than PNG or JPEG". Our image optimization guide covers the details. - Lazy-load below the fold only. web.dev's lazy loading article says "use loading=lazy only for images outside the initial viewport", because lazy-loading the main image slows it down.
- No autoplay. The WSG says to "disable autoplay for audio, video, and other media by default" and to offer lower-bandwidth options. For background and hero videos, see our video on websites guide.
- Fewer fonts. Guideline 2.11 suggests system fonts "to reduce font downloads and improve performance", and otherwise fewer font files, with unused weights and character sets removed.
Code and third-party tools
The WSG asks developers to minify and remove unused code, defer non-critical resources, use dependencies sparingly and keep them maintained. On a WordPress site that often means fewer plugins; our plugin guide covers how to choose them.
Third-party tools get their own guideline, "treat third parties the same as first parties". It names "plugins, widgets, feeds, maps, carousels, tracking scripts, and similar components" and asks you to use as few as possible. Two of its suggestions are easy wins for a business site: "load third-party content only when the user interacts with it", and "offer simple alternatives, such as linking to a form instead of embedding a widget." A map, chat widget or video embed that loads only when clicked saves weight on every visit where nobody clicks.
Hosting, caching and CDNs
For hosting, the WSG says to "favor providers that publicly and transparently disclose their environmental policies and related performance indicators", such as energy and water efficiency figures and renewable energy use. The Web Almanac notes that the Green Web Foundation keeps a dataset of providers that meet its "green" criteria, and found that only 14% of mobile sites in its 2024 crawl ran on such hosts. Check what your current host publishes before you assume either way.
Caching means visitors and servers do less repeated work. The WSG asks for client-side caching of files that rarely change, with versioned filenames, plus server-side caching where it clearly helps. On CDNs it is more nuanced than most advice: "when serving an exclusively local audience, evaluate whether a CDN is necessary, and prefer geographically close hosting instead." Our caching and CDN guide helps you decide.
Set a budget and keep it
Sites get heavier one change at a time: a new tracking tag, a larger hero image, another font. The WSG recommends performance budgets "to cap the size and complexity of digital products or services", together with a baseline measurement and evidence for any improvement you claim. A simple budget for a business site might set a maximum page weight, a maximum number of third-party scripts and a target for Largest Contentful Paint. Check it when the site launches and again whenever something is added. Our Core Web Vitals guide explains the speed metrics, and a maintenance routine is the natural place to review the budget.
Making claims without greenwashing
If you want to tell customers your site is lighter or greener, the WSG's own rules are a good guide. Conformance claims "are optional", and a claim should give the date, the guidelines' title and address, and exactly which success criteria are met. To avoid greenwashing, the WSG says: "Do not claim WSG conformance as evidence of achieving total sustainability", avoid presenting partial improvements as proof of sustainability, and communicate transparently, "only making verifiable claims alongside supporting evidence." A dated before-and-after page weight is a claim you can back up. A vague carbon-neutral label with no method or date behind it usually is not.
Frequently asked questions
Are the W3C Web Sustainability Guidelines a standard?
No. The current version is a W3C Group Note Draft from the Sustainable Web Interest Group. W3C says Group Note Drafts are not endorsed by W3C or its Members and may be updated or replaced at any time. They are a useful checklist, not a legal requirement.
How heavy should a web page be?
Google's Lighthouse documentation advises keeping the total byte size below 1,600 KiB and flags pages above 5,000 KiB. For comparison, the 2024 Web Almanac put the median mobile page at 2,311 KB in October 2024.
Can I measure my website's carbon footprint exactly?
Not exactly. Calculators estimate it from data transfer using models such as the Sustainable Web Design Model, and the 2024 Web Almanac says no consensus has been reached on accurate estimates. Page weight and request counts can be measured precisely, so track those.
Is a lighter website also a faster one?
Usually. Less data to download means less waiting, especially on mobile. Lighthouse notes that large payloads are highly correlated with long load times, and most WSG web development advice overlaps with performance work.
Can I say my site follows the WSG?
You can make a dated claim listing exactly which success criteria you meet. The WSG says not to present conformance or partial improvements as proof of total sustainability, and to back claims with evidence.
Want a lighter, faster site? See how we handle website development and website maintenance, see all our services, or email [email protected].