Can you mitigate the carbon footprint of websites?
summary
Claims that frontend code changes cut per-view CO2 from 4.6 g to ~0.2 g and annual emissions by -96% using a linter-style tool called ec0lint. Demonstrates concrete fixes: replace PNG with webp/webm/SVG, swap TTF for woff2, remove unused libraries and API calls, prefer system fonts, enable dark mode, and pick low-PUE green hosts. Shows how ec0lint flags and auto-suggests changes, gives installation steps (npm + config) and estimates an 88% reduction across tested sites.
AI-written summary · about
chapters (11)
- 0:00Digital ecology basics
- 1:56What is digital ecology
- 3:46Daily habits to reduce footprint
- 6:15Website carbon footprint
- 9:08Sustainable programming choices
- 10:33Optimizing media for sustainability
- 12:19Eco-friendly hosting
- 13:46Benefits of reducing footprint
- 14:26Introducing eco-link
- 16:38Getting started with eco-link
- 17:00Conclusion
related talks
20mThe Role of Frontend Code in Reducing Carbon Emissions
22mDigital Ecology: Can you Mitigate The Carbon Footprint of Websites
45mYour frontend is ☠️ ⚠️ Let's measure its impact with CO2 js
30mReducing the Carbon Footprint of your Website
10mSustainable means performant
38mSustainable Web Design: Principles and Best Practices
33mUX and sustainable Web
31mYour frontend is ☠️ ⚠️ Let's measure its impact with CO2.js