Blog/ Sustainable webdevelopment

Why I Started Focusing on Building Sustainable Websites

I did not start building websites to think about sustainability. I started because I liked making things for the web. Here is why sustainable websites became part of my everyday work.

By Danny Moons

I did not start building websites because I wanted to think about sustainability.

I started because I liked making things for the web: a page, a layout, a button, a piece of content, a small interaction. There is something satisfying about turning an idea into something people can actually visit, use, read, and share.

The question that changed

For a long time, my focus was mostly practical:

  • Does the website work?
  • Does it look good?
  • Can people find it?
  • Is it easy to manage?
  • Does it perform well in search?
  • Does it load fast enough?

Those questions still matter. But over time, another question started to sit underneath all of them:

What is the real cost of this website?

Not only the financial cost. Not only the hosting cost. The wider cost.

The extra JavaScript nobody needs. The oversized images. The third-party scripts added without much thought. The pages that keep growing heavier. The tracking tools that collect more than they use. The rebuilds that happen because the previous system became too hard to maintain.

Individually, those things can seem small. But the web is made of small things repeated at enormous scale.

Sustainability is part of quality

A sustainable website is not just a "green" website. It is not a badge, a score, or a nice claim in the footer.

For me, sustainable web design and development is about building digital products with more care.

It means asking better questions earlier:

  • Do we need this feature?
  • Does this script earn its place?
  • Can this page be lighter?
  • Can the content be clearer?
  • Can the system be easier to maintain?
  • Can we make the website faster for users and less wasteful at the same time?

What I like about this way of thinking is that sustainability does not sit apart from quality. It connects directly to the things good websites should already do.

A sustainable website is often:

  • Faster
  • Simpler
  • Easier to maintain
  • More respectful of the user
  • Cheaper to run
  • Better for content, code, infrastructure, and attention

Why this became important to me

I started focusing on sustainable websites because the web has become heavier than it needs to be, and because many of the improvements are within reach.

Not because I think every website can be perfect.

Not because every digital project needs to become a climate manifesto.

Not because carbon measurements are always simple or exact.

But because we can make better choices.

We can:

  • Optimize images
  • Reduce unnecessary scripts
  • Choose better hosting
  • Avoid rebuilding everything from scratch without a reason
  • Make performance part of the project from the beginning
  • Write clearer content
  • Measure page weight
  • Question dependencies
  • Build systems that last longer

None of that is glamorous. But it matters.

Sustainability often sounds like an extra requirement, while in practice it can be a very useful design constraint.

It forces clarity. It makes you choose. It pushes you to remove what does not serve the user.

And that is usually where better websites come from.

More software is not always better software

This topic feels even more important now because AI, automation, and modern web tooling are making it easier than ever to create more software.

  • More pages.
  • More components.
  • More generated content.
  • More scripts.
  • More infrastructure.
  • More everything.
  • But more is not automatically better.

If AI helps us build faster, we also need better judgment about what we are building. If frameworks make complex things easier, we still need to ask whether the complexity is necessary. If websites can become more dynamic, personalized, and automated, we need to think carefully about the cost of that complexity.

For me, sustainable websites are part of a bigger question:

How do we build software with more intelligence and less waste?

That question now influences a lot of my work. It affects how I think about performance, SEO, content, design, hosting, analytics, accessibility, maintainability, and AI-assisted development.

The web I want to help build

I do not want sustainability to be treated as a trend or a marketing layer. I want it to become part of everyday web quality. Something developers, designers, founders, agencies, and product teams can actually use when making decisions.

That starts with small, practical changes:

  • A lighter page
  • A cleaner content model
  • A better performance budget
  • A more honest carbon claim
  • A website that lasts longer before it needs another rebuild

That is the kind of web I want to help build.

Faster, smarter, and more sustainable.