Contact

From the blog

Sustainability on the web

Sustainability on the web does not start with hosting, but with the question of what actually needs to be on a page. And that is exactly where it meets accessibility.

Reading time: about 8 minutes

All articles

Machine translation. This article was translated automatically from German into English and has not been reviewed. Read the German original.

When people talk about sustainability on the web, many think of green hosting first. That is an important part, but only a part. For me, sustainability starts much earlier: with the question of what really needs to be on a page, how much data is transferred, which technology is necessary and whether people can use content quickly, easily and without hurdles.

That is exactly why, for me, accessibility naturally belongs to a more sustainable web. An accessible website reduces detours, misunderstandings and unnecessary interactions. People find what they need faster. Pages often load leaner, clearer and more robustly. And that saves not only nerves, but often data, energy and technical complexity as well.

Who is this article for?

For people who plan, design or develop websites and want to understand better why sustainability on the web is not only about hosting, but also about content, technology, accessibility and deliberate decisions.

Infographic on sustainable web design The graphic shows four building blocks of a more sustainable web: small amounts of data, accessibility, reduced media and responsible hosting. A more sustainable web is made of several building blocks Less data small pages fewer requests clear budgets Accessibility fewer detours clear structure easier use Mindful media compressed images SVG where it fits no decorative clutter Responsibility green hosting fewer third parties clean technology
Sustainability on the web is not a single switch, but the interplay of content, technology, accessibility and infrastructure.

Web sustainability extends beyond environmental issues, because principles such as accessibility, internationalization, privacy, and security can impact the sustainability of a project.

Web Sustainability Guidelines (WSG) (External link, opens in a new window), W3C

What do the Web Sustainability Guidelines say?

The Web Sustainability Guidelines (External link, opens in a new window) of the W3C Sustainable Web Interest Group describe sustainability not only as an environmental question, but as the interplay of planet, people and prosperity. So it is not only about lowering emissions, but also about designing digital products to be fair, accessible, understandable and meaningful in the long run.

What I find particularly relevant: the WSG connect topics that are often looked at separately in practice. Performance, accessibility, maintainability, hosting, media, navigation, forms and technical decisions are all linked. A website is more sustainable when it works well for people and creates as little unnecessary load as possible.

Why is accessibility part of a more sustainable web?

Accessibility is sometimes seen only as a social or legal requirement. That falls short. An accessible website is often more sustainable as well, because it is simpler, clearer and more efficient.

  • Clear navigation reduces searching and frustration.
  • A clean HTML structure improves robustness and maintainability.
  • Text alternatives help when images do not load or are deliberately left out.
  • Fewer visual gimmicks often mean less data, less JavaScript and less processing.
  • Plain language reduces follow-up questions and mistakes.

In other words: when people reach their goal faster, that is almost always better for usability, accessibility and sustainability at the same time.

How big is a website, actually?

Many websites today are surprisingly heavy. According to the HTTP Archive (External link, opens in a new window), the median weight of web pages is currently around 2.6 MB on mobile and just under 3.0 MB on desktop. A large part of that is images, scripts and fonts.

For me, that is a good reality check. Anyone who wants to build a small, fast website should not ask “How much more can I add?”, but rather “What can go without the website losing value?”

On my own website, I deliberately take this route. I largely do without images and prefer to keep the site small, clear and text-based. Not because images are bad in principle, but because I only want to use them when they really explain something or add value to the content. It matters more to me that content is there quickly, stays understandable and does not drag unnecessary data along with it.

Why images are so often the biggest problem

On many websites, images are the largest block of data. That automatically makes them one of the most important levers for a more sustainable web. The WSG say very clearly in several places that media should only be used when they are really needed – and then suitably optimised.

When images do make sense, these basic rules help:

  • Only use images that really carry content.
  • Export them at the size actually needed, not larger.
  • Consider modern formats such as WebP or AVIF.
  • Use SVG for simple graphics and illustrations.
  • Compress before uploading.
  • Add alt text when the image is relevant to the content.

How can you compress images?

In practice, a few good tools are often enough. What matters is not forcing maximum compression blindly, but finding the right balance between file size, legibility and benefit.

On content websites in particular, it is worth checking before the upload: does this image really need to be 1,600 pixels wide if it will only ever be displayed at 640 pixels? Very often the honest answer is no.

Useful links for a more sustainable web

Checklist for web developers

  • Before every new feature, ask: do we really need it?
  • Define a page weight budget, for the home page and subpages, for example.
  • Only use images when they contribute something to the content.
  • Compress images before uploading and crop them to size.
  • Use SVG instead of heavy graphics where it suits the content.
  • Use an accessible HTML structure with headings, lists and landmarks.
  • Keep forms short and label them clearly.
  • Scrutinise third-party scripts and reduce them to the essentials.
  • Keep fonts, JavaScript and CSS as small as possible.
  • Prefer static delivery when no dynamic logic is needed.
  • Check hosting for sustainability, energy mix and transparency.
  • Measure regularly: size, requests, loading time and unnecessary dependencies.

Conclusion

A more sustainable web is not created by a single green label. It is created by many deliberate decisions: fewer unnecessary media, less dead weight, clearer content, better accessibility, more efficient technology and hosting that takes responsibility.

For me, all of this belongs together. When I do without unnecessary images and want to keep my website small, that is not a purely aesthetic decision. It is also a decision for accessibility, maintainability and a web that is a little more careful with resources.