Sustainable Websites: Impact, Measurability, Implementation

Sometimes you notice it first in everyday life: The new campaign is live, the ads are running – yet everything feels sluggish. It takes too long on the phone for something to happen. Some users drop off. The team questions whether “the website is just heavy”.

This is where sustainability on the web begins. Not with a green badge in the footer, but at that moment you realize: We’re wasting resources – time, money, and attention simultaneously.

The context is clear: The digital sector contributes about 2.8–4 percent to global greenhouse gas emissions. <cite data-type="source" data-url="https://theshiftproject.org/en/article/unsustainable-use-online-video/">The Shift Project (2019)</cite> More recent estimates suggest about 3.4 percent. <cite data-type="source" data-url="https://www.lemonde.fr/en/pixels/article/2025/02/07/climate-annual-use-of-digital-media-is-equivalent-to-a-3-500-kilometer-road-trip_6737909_13.html">Le Monde (2025)</cite> And while data centers become more efficient, data volumes continue to grow – especially due to video, tracking, and increasingly heavy websites.

We notice in projects: Many organizations invest heavily in sustainability in their core business, but the website runs “on the side”. Often with a theme from back then, a plugin collection as a stopgap – and a design that falls apart a little more with each update.

Our first “secret ingredient” is therefore not technology, but clarity: Sustainable websites emerge from priorities. When content, user path, and technology are focused on the essentials, the result is almost automatically faster – and usually much more resource-saving.

And one more thing: Sustainability on the web is not about doing without. It’s a quality promise. For you, for your users – and for the system in which everything runs.

When we talk about sustainable websites, we don’t mean “eco-looks” or just “green hosting”. Sustainability on the web has three dimensions – and it rounds out only when combined.

1) Ecological: less energy per use

Every page view moves data, has servers compute, and end devices render. The larger and more complex the page, the higher the energy demand – and the higher the emissions if the power mix is not renewable. That websites are getting heavier is well documented: The average page size today is about 2 MB and continues to grow long-term. <cite data-type="source" data-url="https://www.pingdom.com/blog/webpages-are-getting-larger-every-year-and-heres-why-it-matters/">Pingdom</cite>

2) Economic: durable instead of throwaway relaunch

Sustainable also means: You don’t rebuild every other year because the system became fragile. In practice, this is the underestimated part. We often see that the greatest “digital waste” doesn’t occur from a large header but from short-lived decisions: dependencies that no one can maintain or structures that make every small change expensive.

3) Social: access for all

For us, accessibility is not an extra that you tack on but a quality standard. If a website works on old devices, with slow connections, or with assistive technologies, it is often automatically leaner, clearer, and more robust.

Our second “secret ingredient” is a simple heuristic we use in projects: Planet–People–Profit as check in review.

When we make a decision (animation, video, tracking, framework), we briefly ask:

1. Does it decrease or increase data and computational load (Planet)?
2. Does it become usable for more or fewer people (People)?
3. Does it make the website more maintainable and economically viable long-term (Profit)?

If two out of three answers are “worse”, we look for an alternative. This small routine prevents sustainability from becoming a vague feeling – and turns it into a design discipline.

A page view feels like a moment. Technically, it’s a small journey.

First, a server goes to work: It delivers HTML, CSS, images – sometimes it has to query databases, assemble templates, or execute scripts. Then these data travel through the network, over nodes, cell towers, routers. In the end, the device computes: It unpacks, renders, executes JavaScript.

What often gets underestimated are third-parties. In many audits, we see that a large portion of requests doesn’t come from “your website”, but from tracking, A/B testing, embedded maps, video players, social widgets. These are all individual small decisions that accumulate.

A practical image we like to use: Imagine your website as a small digital ecosystem. Each additional script is like an animal that needs feeding – CPU time, network, storage. Some are useful. Many are only there because they “have always” been there.

A hard reality check comes through usage behavior: If a mobile page takes more than three seconds to load, many users drop off. <cite data-type="source" data-url="https://scientiamobile.com/53-of-mobile-site-visitors-abandon-if-it-takes-more-than-3-seconds-to-load-page/">ScientiaMobile</cite> Ecologically, this means we’ve used energy without creating impact. Economically, it means you pay for campaigns but lose people halfway. Socially, it means people with weaker devices or connections are excluded first.

Our third “secret ingredient” is therefore a very concrete method from our projects: Request diet instead of feature diet.

We don’t remove anything because it sounds “eco”. We first reduce requests and payload: fewer external calls, fewer heavy assets, less unnecessary JavaScript. Often the experience remains the same – just quieter, faster, more stable.

If you take away just one thought: Sustainability rarely comes from a big statement but from many small reductions along the visit chain.

If you want to get started right away, you don’t need a fundamental debate. You need a few actions that quickly make an impact.

We almost always proceed in this order because it brings the greatest effect with little risk: media, fonts, scripts, caching.

Images are often the biggest chunk. Modern formats like WebP or AVIF are a quiet gamechanger without users seeing “loss of quality”. In many projects, we save hundreds of kilobytes per page – and suddenly everything feels lighter. If you want to get hands-on: Squoosh is a good start because you can directly compare quality and file size.

Then come fonts. Several font styles, loaded externally, blocking – that sounds harmless but costs requests and render time. Often it’s enough to use fewer styles or preload fonts cleanly.

The third area is tracking. We often experience that over the years “another tool” was added, and no one ever questioned it again. Here our principle “avoidance before compensation” also applies digitally: reduce first, then – if necessary – compensate.

And finally caching: A website that reloads everything every time is like a store that rearranges all the shelves every morning. Clean caching saves not only energy, but also nerves.

A small step-by-step mini-routine you can do today:

1. Measure a page in PageSpeed Insights and note LCP and transferred weight.
2. Check the same page in Website Carbon for a CO₂ estimate.
3. Optimize the largest image (hero) first and remove an unnecessary third-party script.
4. Measure again and document the difference.

Sustainability here doesn’t feel like morality, but rather like a clean, professional appearance: faster, clearer, calmer.

Most emissions we see on the web aren’t caused by a single large image. They result from repetition: a relaunch, then another, a hectic plugin update, then a migration because the system no longer fits.

That’s why longevity is one of the strongest sustainability levers.

We like to think of websites like good products: They need to be able to grow without being reinvented every time. It starts with structure and ends with documentation.

Our method: “Stable core, flexible shell”

In projects, we separate as early as possible the stable part (content, data, information architecture) from the flexible part (presentation, interaction). This has two effects:

First: A redesign later becomes an exchange of the facade rather than a teardown. Content remains, URLs remain, SEO suffers less.

Second: Teams can maintain content without fearing side effects.

Technically, this often leads to an architecture where content is neatly structured in a CMS while the frontend remains sleek. Organizationally, it means: We define components, determine a small design system, and document decisions. Not because documentation is sexy – but because it prevents someone from saying in two years, “We no longer know why this was built this way.”

Sustainability also means: fewer dependencies

Every dependency can be useful. But too many make you inflexible. We try to reduce complexity where it has no impact on users. This is our “anti-fast-fashion” thought on the web: Better few, robust parts that you can repair and extend instead of shiny disposable setups.

If you ask the 5-year question (“Will this still hold if we grow?”), you’re already thinking sustainably. And you’ll notice: Many decisions that protect you long-term feel like “more work” in the short term – until they save you the next complete relaunch.

When we talk about sustainability, we quickly end up at CO₂. That's important. But a website can be ecologically ‘green’ and still exclude people.

Accessibility is therefore not a separate topic next to sustainability but part of it. Because a robust and accessible website often inherently possesses three properties that have ecological impact: It is clearly structured, it is less overloaded, and it works on more devices.

We experience this very concretely: If content is cleanly built with headings, lists, semantic HTML, and meaningful focus states, not only does screen reader usage improve. The site often becomes technically cleaner as well. Less chaos in the DOM, fewer “workarounds”, fewer fragile layout tricks.

And there is a social dimension that is rarely voiced: Heavy websites are not just a performance problem. They are a form of inequality. People with older smartphones or in regions with unstable connections experience the web in poorer quality – or not at all. This is a genuine information and participation problem.

The discussion around “page weight” and the growing divide in the web also becomes visible in technical analyses. <cite data-type="source" data-url="https://almanac.httparchive.org/en/2024/page-weight">HTTP Archive Web Almanac (2024)</cite>

If you take sustainability seriously, accessibility is a nice, practical place to start: It forces you to get clear. What is content? What is decoration? What is really necessary?

And by the way: Accessibility reduces legal risks and improves SEO comprehensibility because content is structured cleanly. This is one of those rare instances where “right” pays off in multiple directions.

Sustainable websites are sometimes treated as “nice to have”. Our experience is: For many organizations, it’s more of a way back to a healthy digital foundation.

The business case doesn’t arise from a moral bonus, but from effects you already feel.

First: Performance reduces drop-offs. If users drop off with more than three seconds of loading time, you lose impact – whether it’s about leads, donations, or sales. <cite data-type="source" data-url="https://scientiamobile.com/53-of-mobile-site-visitors-abandon-if-it-takes-more-than-3-seconds-to-load-page/">ScientiaMobile</cite>

Second: Leanness reduces ongoing costs. Less data means less traffic, often less hosting pressure, fewer “firefighting operations” during operation. On large sites, this is directly noticeable in euros. On smaller sites, you feel it as calm in everyday life: fewer bugs, less update panic.

Third: Longevity reduces relaunch cycles. This is the part seldom in blog posts, but huge in budgets. If you build a website to be modularly expandable, further development becomes more planable. And planability is a form of sustainability – also financially.

Fourth: Credibility. For purpose-driven brands, a silent contradiction arises if one’s website is unnecessarily heavy, loud, and inaccessible. A sustainable website then isn’t a marketing claim but consistency.

We rarely calculate ROI with a “magical” percentage, as it depends heavily on the context. But we do something else: We translate technical improvements into impact logic.

If a landing page becomes faster, bounce rate decreases. If users understand faster, inquiries increase. If less tracking is loaded, trust often increases. And if the system is stable, there’s more budget for content instead of repairs.

Here, sustainability is not the cherry on top. It’s often how a website does what it’s supposed to: reach people – without unnecessary ballast.