-
Notifications
You must be signed in to change notification settings - Fork 715
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update carbon control to latest version of Sustainable Web Design Model #3104
Comments
thanks @fershad we will take care of this in upcoming releases |
@fershad quick question on that: we took a look at this and for example ndtv.com moved from 4.8g per visit to 1.55g per visit. Seems reasonable to you? |
Hi @claud-io, sorry for the delay in getting back to you on this. We do expect to see a reduction in the total emissions returned using the newer version of Sustainable Web Design (version 4). I can't talk about the case of specific websites, but we've talked about that change in this blog post: https://www.thegreenwebfoundation.org/news/understanding-the-latest-sustainable-web-design-model-update/ . Regarding the 100 site's median grams per visit, I'm not sure what this is referencing. |
Hey @fershad, sorry typo on my end, i was referring of the median CO2 footprint of the top 1000 websites, which was 0.6g per visit |
Thanks @claud-io, but I'm still not really sure what number you're referring to here - it's not something that we (Green Web Foundation) track, so I'm not able to help much without a source. |
Hey @fershad, fyi i was talking about the average carbon per visit (which was 0.6 based on web almanac of 2022) now seems that with swd v4 this value is lower like 0.3. |
Feature Request Summary
The Carbon Control feature currently implements the default carbon estimation model from CO2.js. At the time of writing, this is Sustainable Web Design Model version 3. However, this is an older version of the Sustainable Web Design Model and an updated version (Sustainable Web Design Model version 4 - SWDMv4) has now been released (see docs). This version is also available in CO2.js v0.16 - see release notes.
What's the motivation or use case for the change/feature?
Use a more recent model for carbon estimation.
The text was updated successfully, but these errors were encountered: