A sustainable website has a clear purpose. It avoids unnecessary content and functionality. It works for more people, loads efficiently, respects privacy, uses dependable technology and can be maintained without being replaced every time the industry changes its favourite tool.
Purpose is the first performance budget.
Start with the job the website has to do
The purpose of a website should be understood before its effects are judged. Sustainable design begins by understanding the service. Who needs it? What are they trying to do? What information allows them to decide? What does the organisation need to achieve in return?
Content has a physical consequence
Digital content can feel weightless because we cannot see the infrastructure behind it. But every image, font, script, document and video has to be stored, transmitted and processed on somebody’s device. The question is whether the content earns the resources it uses.
Accessibility is part of sustainability
A website cannot be called responsible if people are prevented from using it. Accessible design includes semantic structure, keyboard access, readable contrast, useful alternatives and reduced-motion support.
Performance is experienced, not merely scored
Web performance is about how quickly a site feels, responds and remains visually stable. Lab scores are useful evidence, but they need context and should be paired with real-user measures where possible.
Evidence note. Use field data where traffic allows. Record test conditions for laboratory results. Treat every score as evidence, not a verdict.
The technology should fit the requirement
Every dependency carries a cost: more files, more updates, more security review and more failure points. Technology should earn its place through usefulness, maintainability and resilience.
Hosting matters, but it is not absolution
The energy used by data centres is part of a website’s impact. Hosting claims should be current, specific and careful about their boundary. Efficient hosting does not excuse wasteful design.
Website carbon figures are estimates
Most carbon tools estimate impact from data transfer, hosting energy and assumptions about user devices and networks. The model, version, date and limitations should be stated close to the figure.
A practical checklist
- Every page has a defined purpose.
- Images are responsive and appropriately compressed.
- Keyboard access, contrast and labels are checked.
- JavaScript, fonts and third-party requests are limited.
- Performance budgets are agreed before build.
- Carbon estimates name the model and assumptions.
- The site has an owner and a maintenance plan.
Sources and further reading
- W3C Web Content Accessibility Guidelines 2.2
- Sustainable Web Design Model and CO2.js documentation
- Web Almanac, Page Weight and Performance chapters
- Green Web Foundation, hosting and energy guidance