Set goals based on potential impact considerations
Performance is a key part of the sustainability mindset as reductions in loading times can have a considerable impact on energy loads within CPU, GPU, RAM, and hard drive caching (among other variables), as such ensuring a performant product is essential.
Criteria: Performance goals
Explicit goals that impact the environment and performance of the service, for example, HTTP requests, or the amount of DOM elements that need to be rendered are both set and met.
Resources
- 15 page speed optimizations that sites ignore (at their own risk)
- CPU Throttling In Chrome DevTools and Lighthouse
- Does Making Fewer HTTP Requests Improve Page Speed?
- Does not compute: Avoiding pitfalls assessing the Internet's energy and carbon impacts
- Electronics Goes Green (PDF)
- Equations relating total annual energy consumption and chips energy efficiency
- Fast load times
- GPF - General Policy Framework (PDF) - 1.1 - Strategy (Assessment & Impact)
- GPF - General Policy Framework (PDF) - 1.5 - Strategy (Impact Goals)
- GPF - General Policy Framework (PDF) - 4.9 - UX and UI (Server Requests)
- GR491 - 3-7043 - Client / Server Requests
- How Improving Website Performance Can Help Save The Planet
- Investigating the website sustainability of Finnish listed companies (PDF)
- Latency numbers every frontend developer should know
- Platform Strategy and Its Discontents
- Precisely specify the need
- Rethinking Allocation in High-Baseload Systems (PDF)
- Systems thinking and efficiency under emissions constraints
- UI Tools
- United Nations SDGS - Goal 1 - Poverty
- United Nations SDGS - Goal 7 - Sustainable Energy
- United Nations SDGS - Goal 13 - Climate Change
- Web Almanac: Sustainability
- Why do reflows negatively affect performance?
Criteria: Accountancy types
Because the payload being delivered may not always be equal in terms of energy intensity, operators of websites and applications must ensure that consideration is given for the energy intensity (or unit being evaluated) of each component. For example, non-rendering text is less computational than CSS, which in turn is less process-heavy than JavaScript, which is less resource-heavy than WebGL.
Resources
- Analysis of overconsumptions on a light website
- Avoid An Excessive DOM Size For Better Web Performance
- Boring Web Development
- Graphics Card Power Consumption and Efficiency Tested
- How Deep is Your DOM?
- How Much Power Does Memory Use?
- Latency numbers every frontend developer should know
- Mac Pro power consumption and thermal output (BTU/h) information
- Power Consumption of PC Components in Watts
- The Carbon Impact of Web Standards (PDF)
- United Nations SDGS - Goal 1 - Poverty
- United Nations SDGS - Goal 7 - Sustainable Energy
- United Nations SDGS - Goal 13 - Climate Change
- Web Almanac: Sustainability
Impact: Medium, Effort: Medium
| GRI | Impact |
|---|---|
| materials | Medium |
| energy | Medium |
| water | Medium |
| emissions | Medium |
Benefits of this guideline
- Environment: Limiting the number of server requests and the size of the DOM decreases a product or service's environmental impact by reducing CPU and GPU cycles, and RAM usage which benefits energy consumption, reducing the need to recharge devices as frequently.
- Performance: Reducing the hardware utilization as denoted above will also improve performance metrics, as a device will suffer less consumption and thrashing of limited resources.
- Conversion: Search engines consider web performance in their ranking data, as such a faster website may lead to a higher rank and potentially better conversion rates.
Example
-
contentA large list of ways to speed up your website within the front-end performance checklist.
Tags:
- KPIs
- Networking
- Performance
- Research
- Social Equity
- Strategy