The internet feels weightless because you can’t see the warehouses, cables, cooling equipment, network hardware, and user devices behind a page load. The bill still arrives. It shows up as electricity use, equipment demand, data charges, slow pages, and devices doing work they didn’t need to do.

That makes website sustainability useful even if your company never publishes a climate report. A lighter, simpler site is usually cheaper to serve, faster to load, easier to maintain, and more usable on an older phone or weak connection. Those are business outcomes, not slogans.

This resource brings together 31 current data points for web professionals and business owners. It also explains what the numbers can and can’t prove, because a carbon calculator result is an estimate, not a utility meter attached to one web page.

The Numbers That Frame the Problem

  1. 6.12 billion people were using the internet at the start of April 2026. That represented 73.8% of the world’s population, according to DataReportal’s global digital overview. Small inefficiencies become large when repeated across billions of people and visits.

  2. Data centers consumed about 415 terawatt-hours of electricity in 2024. The International Energy Agency’s central case projects 945 TWh in 2030, more than double the 2024 total (IEA). Websites are only one part of data-center demand, so don’t assign the whole number to the web. It does show why digital efficiency is no longer a niche infrastructure concern.

  3. Data-center electricity demand is projected to grow about 15% per year from 2024 to 2030. That is more than four times the rate for electricity consumption in other sectors (IEA).

  4. Data centers represented about 1.5% of global electricity consumption in 2024. The same IEA analysis expects them to account for more than one-fifth of global electricity-demand growth through 2030 (IEA).

  5. At least 10,852 large, publicly known data centers operate in 174 countries. Green Web Foundation cites the Data Center Map count and warns that definitions vary and many private facilities are not captured (State of the Fossil-Free Internet 2026).

  6. At least 7,250 new data-center projects are planned. About two-thirds are in North America, according to the sources assembled in the Green Web Foundation’s 2026 report.

  7. There are at least 1,297 hyperscale data centers worldwide. Their number tripled over seven years, and Amazon, Microsoft, and Google control about 58% of operational hyperscale capacity (Green Web Foundation).

  8. Ireland’s data centers used 22% of the country’s metered electricity in 2024. The figure comes from Ireland’s Central Statistics Office and is linked in the Green Web Foundation report. It is a sharp example of why location and grid conditions matter.

Website Weight Statistics for 2026

Page weight is not a complete environmental measure. It is still one of the easiest variables a web team can control and audit.

  1. The median desktop home page weighed 2.9 MB in 2025. That was up 7.3% from 2024 (HTTP Archive Web Almanac).

  2. The median mobile home page weighed 2.6 MB. It grew 8.4% in one year (HTTP Archive).

  3. Median home-page weight grew 7.8% year over year to 2.7 MB across device types. Bigger network pipes did not cause teams to hold the line. Pages expanded to fill the available capacity (HTTP Archive).

  4. The median mobile home page grew from 845 KB in July 2015 to 2,362 KB in July 2025. That is a 202.8% increase in a decade (HTTP Archive).

  5. Median desktop home-page weight rose 110.2% over the same decade. Desktop growth was slower than mobile growth, but the payload still more than doubled (HTTP Archive).

  6. Inner pages grew 9.5% year over year. Median mobile inner pages reached 1.8 MB, while desktop inner pages reached 2 MB in 2025 (HTTP Archive).

  7. A median mobile home page transferred 911 KB of images. Images were the largest named content category in HTTP Archive’s breakdown (HTTP Archive).

  8. That same median mobile home page shipped 632 KB of JavaScript. JavaScript also requires the user’s device to parse, compile, and execute it, so transferred bytes don’t capture all of its cost (HTTP Archive).

  9. Fonts added 122 KB, CSS added 77 KB, and HTML added 22 KB to the median mobile home page. These categories are smaller than images and JavaScript, but they still belong in a page budget (HTTP Archive).

  10. Median mobile inner-page image weight was 354 KB, compared with 911 KB on home pages. That gap is a warning about oversized hero media and visual clutter on the front door of a site (HTTP Archive).

  11. Home pages were about 45.8% heavier than inner pages on average. HTTP Archive connects that difference to the accelerating growth in home-page weight (HTTP Archive).

What Carbon Calculators Actually Measure

There is no carbon sensor inside Chrome. Most public tools estimate impact from transferred data, an energy-intensity model, grid carbon intensity, repeat-visit assumptions, and an allocation for the data center, network, and user device.

  1. The Sustainable Web Design Model separates operational and embodied emissions. Operational emissions come from energy used while the system runs. Embodied emissions cover producing and disposing of equipment (Sustainable Web Design).

  2. The model divides system energy among data centers, networks, and user devices. Its published method allocates operational energy intensity across those three parts instead of treating hosting as the entire footprint (Sustainable Web Design).

  3. The method uses 494 grams of CO2e per kWh as its global-average grid factor. A site served and viewed on a cleaner grid may have a lower estimate. A fossil-heavy grid may produce a higher one (Sustainable Web Design).

  4. The model assumes 75% of visitors are new and 25% are returning by default. Returning visits may use cached assets, which reduces repeat transfers (Sustainable Web Design).

  5. Public calculators often miss CPU, GPU, memory, animation, and full user journeys. HTTP Archive’s sustainability research says tools commonly rely on transferred data, request counts, and DOM size, which cannot represent every source of device work (2024 Web Almanac).

  6. There is not yet a consensus method for estimating all digital impacts. HTTP Archive recommends treating greenhouse-gas estimates as one indicator and also considering water, minerals, equipment, and product lifespan (2024 Web Almanac).

The practical lesson is simple: label estimates honestly. Record the calculator, model version, tested URL, location or grid assumption, page state, and date. Never turn a modeled result into a claim that the business has directly measured emissions.

Hosting and Standards Statistics

  1. 950,718 unique websites were checked with Green Web Checks during one 24-hour period in December 2025. A green result means the provider supplied evidence of green energy use. An unverified result means evidence was not found, which is not necessarily proof that the host uses only fossil energy (Green Web Foundation).

  2. Between 7 million and 15 million Green Web Checks run each day. The volume shows that customers and web teams are actively checking hosting claims (Green Web Foundation).

  3. The Software Carbon Intensity specification became ISO 21031:2024. The standard provides a method for calculating the rate of carbon emissions for a software system (Green Software Foundation).

  4. W3C’s Web Sustainability Guidelines cover three impact areas: planet, people, and prosperity. The guidance treats sustainability as more than electricity use and gives teams recommendations for design, development, hosting, business strategy, and product management (W3C).

  5. The 2024 Web Almanac found that fewer than 0.01% of tested pages used the prefers-reduced-data media query. Support for respecting a user’s request to reduce data transfer remained extremely rare (HTTP Archive sustainability chapter).

  6. Only 0.18% of mobile pages and 0.22% of desktop pages used the Save-Data request header in the 2024 dataset. The feature can help sites serve smaller assets when users ask for reduced data usage, but adoption was tiny (HTTP Archive).

A Practical Website Sustainability Framework

You don’t need a perfect carbon number before you remove obvious waste. Use this order because it starts with work the business can verify and control.

1. Measure real journeys, not just the home page

Pick the five paths that matter most: finding a service, reading a product page, submitting a quote request, completing checkout, and getting support. Record transferred bytes, request count, Core Web Vitals, video behavior, third-party calls, and whether a second visit uses the cache.

Use analytics to weight the result. A 4 MB page viewed 50 times has a different priority from a 2 MB page viewed 100,000 times. Keep bots separate where possible because crawler traffic can distort the picture.

2. Set a page-weight budget

For a standard small-business marketing page, a practical starting target is 1.5 MB or less on mobile, with 2 MB as a warning line. Those are house targets, not universal standards. They put the page below the 2.6 MB median mobile home page measured by HTTP Archive.

Give images, JavaScript, fonts, and third parties their own budgets. A total-only limit lets one category consume everything. Make exceptions visible and tie each one to a business outcome.

3. Remove before you optimize

Ask whether an asset or feature earns its cost. A background video nobody watches should be removed, not compressed for two hours. Retire duplicate analytics tags, old A/B testing scripts, unused chat widgets, abandoned pixels, and plugin features loaded site-wide for one page.

Then optimize what remains. Resize images to their rendered dimensions, use modern formats, lazy-load offscreen media, subset fonts, cache stable files, and avoid shipping client-side JavaScript for content that can arrive as HTML.

4. Verify hosting claims

Ask a hosting provider for the facility location, electricity evidence, renewable-energy accounting method, power usage effectiveness, hardware-lifecycle policy, and reporting boundary. Run a Green Web Check, but keep the answer in context. A verification badge doesn’t cancel an unnecessarily heavy product.

5. Design for less capable devices

A page that forces a customer to replace an older phone is not sustainable. Test on a low-powered device, a throttled connection, keyboard navigation, and reduced-motion settings. Make core tasks work without autoplay, giant images, or continuous client-side processing.

Support user preferences where the platform allows it. Reduced data and reduced motion are also good reminders that the user, not the design team, pays part of the computing and bandwidth cost.

6. Report reductions without greenwashing

Publish what changed: page weight fell from 3.1 MB to 1.4 MB, requests fell from 94 to 47, and third-party JavaScript fell by 210 KB. These are measurements a team can reproduce.

If you publish a carbon estimate, include the model and assumptions. Say “estimated with Sustainable Web Design Model version X” instead of “this page emits exactly X grams.” Avoid broad labels such as “carbon neutral website” unless the company can document the boundary, reductions, residual emissions, and any credits.

A Quarterly Audit Checklist

  • Export the 25 highest-traffic pages and five most important user journeys. Record first-load and repeat-load transfer size, requests, and Core Web Vitals.
  • Find the ten heaviest images, scripts, fonts, videos, and third-party resources. Assign an owner and a keep, replace, defer, or remove decision.
  • Check hosting evidence, cache behavior, old redirects, duplicate tags, unused plugins, autoplay media, and user preference support. Publish measured reductions with the date and method.

Sustainable web work is not a separate coat of green paint. It is disciplined product work: fewer wasted bytes, fewer pointless requests, clearer journeys, longer device life, and honest measurement.

If you want a web team to cut waste while improving speed, usability, and lead generation, start a conversation with Your Web Team.

Frequently Asked Questions

How much carbon does a website produce?

There is no universal number. The estimate changes with page weight, traffic, caching, hosting energy, network energy, user devices, and the model used. Report a range and name the method.

Is a lightweight website automatically sustainable?

No. Low page weight helps, but hosting energy, hardware, accessibility, content lifespan, user behavior, and business practices also matter. Think of weight as a controllable indicator, not a complete verdict.

What should a business measure first?

Start with transferred bytes, request count, Core Web Vitals, third-party scripts, and the five user journeys that generate the most traffic or revenue. Those measurements are repeatable and lead directly to specific fixes.