Sustainable Websites: Impact, Measurability, Implementation

Lightweight is more than a performance goal

Sometimes you notice it first in everyday life: The new campaign is live, the ads are running – and yet everything still feels sluggish. On mobile, it takes too long for anything to happen. A few users drop off. The team starts asking whether “the website is simply too heavy”.

That’s exactly where sustainability on the web begins. Not with a green badge in the footer, but with the moment when you realize: We’re wasting resources – and at the same time, time, money, and attention.

The context is clear: The digital sector accounts for around 2.8–4 percent of global greenhouse gas emissions. The Shift Project (2019)↗ More recent assessments put it at around 3.4 percent. Le Monde (2025)↗ And while data centers are becoming more efficient, data volumes continue to grow – especially due to video, tracking, and increasingly heavy websites.

What 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 collection of plugins as a stopgap – and a design that falls apart a little more with every update.

Our first “secret ingredient” is therefore not technology, but clarity: Sustainable websites are built on priorities. When content, user journey, and technology are focused on what matters, the result is almost automatically faster – and usually significantly more resource-efficient.

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

Three perspectives always belong together

When we talk about sustainable websites, we don’t mean “eco-look” and not just “green hosting”. Sustainability on the web has three dimensions – and only together do they make the whole picture.

1) Ecological: less energy per use

Every page view moves data, makes servers compute, and makes end devices render. The larger and more complex the page, the higher the energy demand – and the higher the emissions if the electricity mix is not renewable. The fact that websites are getting heavier and heavier is well documented: The average page size is now around 2 MB and continues to grow over the long term. Pingdom↗

2) Economically: long-lasting instead of throwaway relaunches

Sustainability also means: You don't rebuild every other year because the system has become fragile. In practice, this is the underestimated part. We often see that the biggest „digital waste“ is not caused by a large header, but by short-lived decisions: dependencies that no one can maintain anymore, or structures that make every small change expensive.

3) Socially: access for everyone

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

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

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

1. Does it reduce or increase the data and computing load (Planet)?
2. Does it make it usable for more people or for fewer (People)?
3. Does it make the website more maintainable and economical in the 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.

Every visit sets a small data journey in motion

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

First, a server works: It delivers HTML, CSS, images – sometimes it has to query databases, assemble templates, or execute scripts to do so. Then this data travels through the network, via nodes, mobile phone masts, routers. And finally, the end device computes: It unpacks, renders, and executes JavaScript.

What is quickly underestimated in this process are Third-Parties. In many audits, we see that a large part of the requests does not come from „your website“, but from tracking, A/B testing, embedded maps, video players, social widgets. These are all individual small decisions that add up.

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

A hard reality check comes from usage behavior: If a mobile page takes longer than three seconds to load, many users abandon it. ScientiaMobile↗ Ecologically, this means: We have consumed energy without creating an impact. Economically, it means: You pay for campaigns, but lose people halfway through. Socially, it means: People with weaker devices or connections are excluded first.

That is why our third “secret ingredient” is 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 stays 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 visitor journey.

Numbers only become useful with a baseline

Sustainability without measurement is well-intentioned, but difficult to steer. At the same time, scores are tempting: One number, one traffic-light system, done.

We use measurement more like a compass. Not as a grade, but as a common language within the team.

Three levels that make sense together

First: Data volume and requests. If a page delivers only 800 KB instead of 2.5 MB, that is almost always a real gain – for load time, energy and users.

Second: Core Web Vitals. They show what performance feels like for real people: LCP, INP, CLS. Here, tools like PageSpeed Insights are helpful, but we always interpret them in context: What is “the largest element” for your content? What is really blocking interaction?

Third: CO₂ estimators such as Website Carbon or EcoIndex. They calculate using models (traffic, transfer, electricity mix) – this is not perfect, but very useful for before-and-after comparisons.

An example we like to use as an order of magnitude: An average website can reach around 211 kg of CO₂ per year with 10,000 visits per month. GreenByDefault↗ Whether your site is above or below that depends heavily on weight, hosting and third parties.

Our measurement heuristic: Baseline, then budget

When we start, we first establish a baseline: homepage, most important landing pages, a typical content article. Then we define a “performance and weight budget”: not as a rigid requirement, but as a guideline. For example: “New landing pages must not exceed the homepage” or “Videos only on click”.

That is the difference between optimization as a one-off project and sustainability as a practice: You don't measure to justify yourself – you measure to make decisions easier.

Four levers make pages lighter immediately

If you want to get started right away, you don't need a fundamental debate. You need a few interventions that quickly make a noticeable difference.

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

Images are often the biggest chunk. Modern formats like WebP or AVIF are a silent game changer, without users seeing any „loss of quality“. In many projects, we save hundreds of kilobytes per page this way – and suddenly everything feels lighter. If you want to get hands-on yourself: Squoosh is a good starting point because you can compare quality and file size directly.

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

The third area is tracking. We often see that over the years „one more tool“ was added, and nobody ever questioned it again. Here, too, our principle „avoidance before compensation“ applies digitally: First reduce, then – if necessary – compensate.

And finally caching: A website that reloads everything on every visit is like a shop that rearranges all the shelves every morning. Proper caching not only saves 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. First optimize the largest image (Hero) and remove an unnecessary third-party script.
4. Measure again and document the difference.

Sustainability doesn't feel like morality here, but like a clean, professional presence: faster, clearer, calmer.

Longevity begins with a robust system

Most of the emissions we see on the web don't come from a single large image. They come from repetition: a relaunch, then another one, then a rushed 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 as good products: They need to be able to grow without being reinvented every time. That starts with structure and ends with documentation.

Our method: „Stable core, flexible shell“

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

First: A redesign later won't be a demolition, but an exchange of the facade. Content stays, URLs stay, SEO suffers less.

Secondly: Teams can maintain content without having to worry about side effects.

Technically, this often leads to an architecture in which content is cleanly structured in a CMS, while the frontend remains lean. Organizationally, it means: We define components, establish 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 unable to move. We try to reduce complexity where it has no impact on users. That is our „Anti-Fast-Fashion“ idea for the web: Better a few robust parts that you can repair and extend than shiny disposable setups.

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

The right stack follows the task

At the latest when it comes to the tech stack, sustainability readily becomes a matter of belief. WordPress or Headless? SPA or classic site? A framework or Vanilla?

We believe: There is rarely „the one right“ answer. But there are a few patterns that repeat.

If a website primarily conveys content, an approach with Static Site Generation or server-side rendering is often more efficient than purely client-side rendering. The reason is simple: You send the browser finished HTML faster instead of large JavaScript packages that first have to assemble what you actually just want to read.

In our projects, we often use Astro, because it is very consistent about delivering only what is really needed: By default, it delivers HTML, and interactivity is added selectively as „islands“. This is not only fast, it is also a philosophy: Interaction where it has an impact – not everywhere just because it is possible.

A second building block is a CMS that makes editorial work easy without bloating the frontend. Headless systems can help here because they decouple content and presentation. For example, we like to work with Payload, when structure, permissions, and scalability are important.

Our practical heuristic for stack decisions is called „JS only with justification“: Every larger JavaScript library needs a sentence explaining why it has to be on the site – from the user's perspective. If the sentence is difficult to come up with, that is a signal.

And one more unpopular truth: Sustainability is rarely just „Framework A versus B“. It is the overall package: clean components, few third parties, a good image pipeline, a smart caching strategy.

If you’re currently planning a relaunch, a baseline analysis is worthwhile before you commit. Often, the audit alone will show you whether the problem really is the CMS – or the ten scripts around it.

Clean electricity doesn’t replace a lean website

Green hosting is a good step – but it’s not the whole story.

Yes: If your hosting is powered by renewable energy, emissions per page view decrease noticeably. And it’s often one of the quickest measures, because you don’t have to touch the entire codebase right away.

But: We see that green hosting is sometimes used as “indulgence”. Along the lines of: We host green, so everything is fine. This is exactly where it’s worth applying the principle “avoidance before compensation”.

Because even with green electricity, energy consumption remains energy consumption. And other effects remain: data transmission, end devices, unnecessary computing load. In addition, “green” is not the same everywhere. It makes a difference whether a provider supplies genuine renewable energy, how transparent they are, and how efficiently the infrastructure operates.

The database of the Green Web Foundationis helpful here to check whether a provider is listed as “green”.

Another point is location and delivery: If your users are mainly in Europe, it helps to deliver content from nearby – for example via a CDN. This is not just about performance, it also reduces unnecessary routes through the network.

Our practical recommendation: See hosting as basic hygiene, not as a sustainability strategy. A sustainable website is like a well-insulated house: green electricity is great – but you still don’t want to leave all the windows open.

If you have the choice, combine:

1. Green hosting with verifiable evidence,
2. lean pages (so you have less to “blow through”),
3. a setup that keeps updates and security stable over the long term.

Then a good label becomes a real, measurable improvement.

Accessible pages work longer and for more people

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.

That’s why we don’t see accessibility as a separate topic alongside sustainability, but as part of it. Because a website that is robust and accessible usually has three characteristics that also have an ecological impact: It is clearly structured, it is less overloaded, and it works on more devices.

We experience this very concretely: When content is structured cleanly with headings, lists, semantic HTML, and meaningful focus states, it’s not just screen reader use that gets better. The page is often technically tidier as well. Less chaos in the DOM, fewer “workarounds”, fewer fragile layout tricks.

And there is a social dimension that is rarely spoken about: Heavy websites are not just a performance problem. They are a form of inequality. Someone with an older smartphone or traveling in a region with an unstable connection gets the web in poorer quality – or not at all. That is a real problem of access to information and participation.

The discussion around “Page Weight” and the growing divide on the web is also visible in technical analyses. HTTP Archive Web Almanac (2024)↗

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 as a side benefit: Accessibility reduces legal risks and improves SEO comprehension because content is structured cleanly. This is one of those rare areas where doing things “right” pays off in several directions.

Less ballast also saves ongoing costs

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

The business case does not arise from a moral bonus, but from effects that you feel anyway.

First: Performance reduces abandonment. If users leave when load times exceed three seconds, you lose impact – whether it’s about leads, donations, or sales. ScientiaMobile↗

Second: Leaner design reduces ongoing costs. Less data means less traffic, often less hosting pressure, fewer “firefighting” efforts in operations. On large sites, this is directly noticeable in euros. On smaller sites, you feel it as peace of mind in everyday work: fewer bugs, less update panic.

Third: Longevity reduces relaunch cycles. This is the part that rarely appears in blog posts, but is huge in budgets. If you build a website so that it can be expanded modularly, further development becomes more predictable. And predictability is a form of sustainability – financially as well.

Fourth: Credibility. For purpose-driven brands, a quiet contradiction arises when their own website is unnecessarily heavy, loud, and inaccessible. A sustainable website is then not a marketing claim, but consistency.

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

When a landing page gets faster, the bounce rate decreases. When users understand things faster, inquiries increase. When less tracking is loaded, trust often increases. And when the system is stable, more budget remains for content instead of repairs.

Sustainability is not the cherry on top here. It is often the way a website gets back to doing what it is supposed to do: reach people – without unnecessary baggage.

A few tools are enough to create a solid starting point

If you want to get started internally, a few tools can help you quickly get your bearings – without immediately having to undertake a complete replatforming.

We use different tools depending on the phase. Here is a small toolbox that has proven itself in practice:

1) For CO₂ estimation and comparison: Website Carbon and EcoIndex.

2) For performance and Core Web Vitals: PageSpeed Insights (with Lighthouse details).

3) For image optimization: Squoosh or an image pipeline via CDN services such as Cloudinary (if you have a lot of assets).

4) For data-sparing analytics: Plausible (lightweight) or Matomo (more control).

A tip from our day-to-day work: Set up a small “before-and-after” routine. A screenshot of the most important metrics per quarter is often enough to make progress visible – and to defuse discussions within the team.

And if you notice that the figures fluctuate significantly, that is not a failure. It is a signal. Sometimes it shows that new content was created without budget rules. Sometimes that a new tool has been added “quietly”.

Sustainability on the web feels best in the long term when it becomes part of the system: a few checks in the process, clear standards, and the freedom to remain creative anyway.

If you would like support with this, that is exactly the kind of project we at Pola are happy to support: bringing design and technology together so that impact does not come at the expense of resources.

The extra becomes a new quality standard

We believe that sustainable websites will become “normal” rather than an “extra” in the coming years. Not because everyone suddenly becomes idealistic, but because it is converging from several directions.

At the system level, data volumes continue to rise. And the energy demand of data centers remains a relevant issue; estimates put data centers at around 1.5–2 percent of global electricity consumption. CO2free Energy↗

On the user side, expectations are becoming stricter: speed is taken for granted, accessibility is becoming more visible, and people are more sensitive to “loud” digital experiences that they cannot control.

And on the organizational side, reporting is becoming more structured. Large companies already have to collect more sustainability data as part of new reporting requirements. Even if websites are (not yet) explicitly regulated everywhere, the pressure is growing to at least understand and contextualize digital emissions.

We find technical developments that directly support sustainability particularly exciting: less JavaScript approaches, better protocols, and early signals toward “Data Saver” standards, where websites adapt to weak connections or limited data budgets.

If we were to derive one calm recommendation from this, it would be this: Build today so that you don’t have to make frantic improvements tomorrow.

A sustainable website is a promise of presence. It says: We are reachable. For as many people as possible. With as little waste as possible.

And if you reach a point where you no longer want to just optimize, but really want to reorganize, then that is the right moment for a clear plan – not for activism.