3.19 Use the most efficient solution for your service
Identify the project requirements, use the most efficient approach, aim for static over dynamic where possible, and consider the impact of extensions and components.
Criteria
- Identify requirements: Machine-testable
Identify the requirements and use this as a basis to help you select the most appropriate implementation for your project. A simpler technological implementation may use more human resources but could have a smaller footprint. A prebuilt solution may use more system resources and have a bigger emissions impact on render, but it could have a faster build time – meaning less carbon is emitted in development. - Optimized methodology: Human-testable
Use the most effective approach for your use case. Most of the time, coding from scratch will often provide the most performant results. Where an existing solution is present and is being actively maintained, this may be better optimized than what you can reasonably produce yourself. Favor native components and file systems over WYSIWYG editors – including visual page builders – or other heavy frameworks. Be mindful of the impact of third-party solutions.- AFNOR Spec 5.3.3 & 5.2.2 (French)
- CMS, No Code or without CMS, which solution to choose for a sober website?
- Creating a Low Carbon Umbraco Website
- GPF – General Policy Framework (PDF) – 3.1 – Architecture (Impact Reduction)
- GR491 – 3-5021 – Functionality VS Native
- GR491 – 6-3041 – Sustainable IT Impact
- GR491 – 8-3059 – Native System Features
- How heavy are no-code websites?
- Solid Protocol
- Web Almanac: Sustainability
- Static over dynamic: Human-testable
Deliver static in place of dynamic content wherever possible. If you choose to use a code generation tool, then favor the most efficient tool available, such as Static Site Generators (SSGs). Content delivered by a dynamic CMS will involve much more server-side processing and uses bulkier libraries.- 7 Reasons to Use a Static Site Generator
- AFNOR Spec 5.3.3 & 5.2.2 (French)
- Are Content Management Systems Sustainable?
- Building for sustainability with WordPress
- CMS Comparison
- CMS, No Code or without CMS, which solution to choose for a sober website?
- Getting Started with Sustainability
- GPF – General Policy Framework (PDF) – 3.1 – Architecture (Impact Reduction)
- GR491 – 3-5021 – Functionality VS Native
- GR491 – 6-3041 – Sustainable IT Impact
- GR491 – 8-3059 – Native System Features
- GreenIT – 011 – Prefer custom solutions to CMS
- Headless CMS vs. static site generator
- How Many WordPress Plugins Are Too Many?
- Quels sont les avantages des sites statiques? (French)
- Web Almanac: Sustainability
- What Affects CMS Performance?
- What is a static site generator?
- Extensions and plugins: Machine-testable
Carefully select and review plugins, extensions, and themes to maximize interoperability, accessibility, and performance. Audit these regularly over time to ensure continued compatibility.- AFNOR Spec 5.3.3 & 5.2.2 (French)
- Auditing and Using WordPress Plugins to Improve Your Website
- GPF – General Policy Framework (PDF) – 3.1 – Architecture (Impact Reduction)
- GR491 – 6-3041 – Sustainable IT Impact
- GR491 – 8-3059 – Native System Features
- GreenIT – 4037 – Choose the right theme and limit CMS extensions
- How to audit your CMS for unused features that slow down performance
- Outdated CMS Plugins
- Interface components: Human-testable
Pay particular attention to user interface components with respect to their sustainability impact.- AFNOR Spec 5.3.3 & 5.2.2 (French)
- GPF – General Policy Framework (PDF) – 3.1 – Architecture (Impact Reduction)
- GR491 – 6-3041 – Sustainable IT Impact
- How to design a sustainable website?
- Striking a Balance Between Native and Custom Select Elements
- Sustainability Kit for digital designers
- UI Tools
- Web Almanac: Sustainability
Benefits
- Accessibility
Making assistive technologies a core part of project specifications from the very start and throughout a product or service”s lifecycle improves access for people with disabilities. - Economic
Avoiding tooling at risk of overburdening user experience may result in financial savings, especially if tooling has associated maintenance expenses, licensing fees, or subscription costs. - Environment
Evaluating long-term technology implications and taking the time to ensure they are optimized and efficiently utilized helps a team measurably reduce the environmental impact of a product or service. - Performance
Reducing complexity in your infrastructure will increase developer productivity, while also reducing overhead. This further reduces emissions. - Privacy
Prioritizing security and user privacy helps an organization better comply with current and emerging legislation. - Security
Maintaining a software product and restricting your use of third-party solutions to the essential will improve overall security.
GRI
- Materials: Medium
- Energy: Medium
- Water: Medium
- Emissions: Medium