Sustainability 2022 #2910
Comments
rviscomi
added
help wanted
|
@cqueern @gerrymcgovernireland you've expressed an interest in a sustainability chapter before. This chapter could use coauthors, reviewers, and analysts if you still have the interest and time! @ldevernay has stepped up to author the chapter 🎉 |
|
@tunetheweb @rviscomi I'd love to put my hand up as an analyst, though will need guidance when it comes to querying the dataset. @mrchrisadams would you also be interested in contributing? |
|
Yes, definitely interested if there’s any way I can help
From: Rick Viscomi ***@***.***>
Sent: Thursday 14 April 2022 04:41
To: HTTPArchive/almanac.httparchive.org ***@***.***>
Cc: gerrymcgovernireland ***@***.***>; Mention ***@***.***>
Subject: Re: [HTTPArchive/almanac.httparchive.org] Sustainability 2022 (Issue #2910)
@cqueern <https://github.com/cqueern> @gerrymcgovernireland <https://github.com/gerrymcgovernireland> you've expressed an interest in a sustainability chapter before. This chapter could use coauthors, reviewers, and analysts if you still have the interest and time!
@ldevernay <https://github.com/ldevernay> has stepped up to author the chapter 🎉
—
Reply to this email directly, view it on GitHub <#2910 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQGRE3ZFULNGNUUXK3M5LE3VE6HVJANCNFSM5TMP2RQA> .
You are receiving this because you were mentioned. <https://github.com/notifications/beacon/AQGRE37NPZDAONV53A2JD5TVE6HVJA5CNFSM5TMP2RQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOIF6IASY.gif> Message ID: ***@***.*** ***@***.***> >
|
|
This enthusiasm is awesome! I'm really eager to work with you all! |
|
Hi folks. I'd be happy to contribute as a reviewer at least, given those timelines. I'll ask internally to see if there's anyone who might be able to contribute in other roles. |
I'd love to support as a Reviewer. Thanks. Looking forward to working with everyone. |
|
I'm curious what this will cover? |
|
In my opinion, the point would be to start with insights on the environmental footprint of digital then focus on sustainability applied to websites. Which tools to use to monitor/measure, where to find best practices (and how to prioritize them). The idea would also be to highlight the links to other topics (Performance, Accessibility, Privacy, etc) and briefly explain how to go further (design reviews, measuring other metrics, setting an environmental budget, etc). Also : state of the art regarding repositories of best practices and tools to calculate the environmental impact (and where to go from here). |
|
These are all great points to cover. Some possible added suggestions:
1. If there was some way we could identify page ‘waste’ that could be useful. This might include unused CSS, JS, poor coding that is slowing things down and thus wasting energy, poorly optimized images, etc. We could give good tips on reducing such waste.
2. In the analysis I’ve been doing, over 90% of the energy impacts are either in the creation of the page or during its use. In popular sites, the vast majority of energy occurs during the page use.
3. There have been interesting studies on the energy impact of various computer languages, with JavaScript being found to be 4.5 times more energy intense than C, for example. I wonder might there be a way to create and energy hierarchy for JavaScript, CSS, HTML, etc. In this way we could guide designers and developers to use the least energy intense option if given a choice. I wonder are there ways to identify design elements that are typically done in JS, for example, that could be done in, say, CSS
4. This is probably out of scope, but typically 80% of CO2 and other negative impacts are caused during the manufacture of the digital devices and network architecture. I think if we wanted to deliver a true and total figure of the environmental impact of the Web, we should consider some accounting for the devices.
Tim Frick of Mightybytes and Tom Greenwood of Wholegrain Digital are two people who huge pioneering work in this space. Perhaps it would be worth reaching out to them.
From: LaurentDev ***@***.***>
Sent: Thursday 14 April 2022 15:27
To: HTTPArchive/almanac.httparchive.org ***@***.***>
Cc: gerrymcgovernireland ***@***.***>; Mention ***@***.***>
Subject: Re: [HTTPArchive/almanac.httparchive.org] Sustainability 2022 (Issue #2910)
In my opinion, the point would be to start with insights on the environmental footprint of digital then focus on sustainability applied to websites. Which tools to use to monitor/measure, where to find best practices (and how to prioritize them).
Based on this, analysis of the main proxy metrics for environmental impacts : page weight and number of request (most often use to calculate environmental indicators through various models), explore how to use proxy metrics (such as Core Web Vitals) and finally which other metrics could used to check on sustainability best practices (image format, inclusion of third-party, minification, compression, cache, lazy-loading, etc).
The idea would also be to highlight the links to other topics (Performance, Accessibility, Privacy, etc) and briefly explain how to go further (design reviews, measuring other metrics, setting an environmental budget, etc).
Also : state of the art regarding repositories of best practices and tools to calculate the environmental impact (and where to go from here).
—
Reply to this email directly, view it on GitHub <#2910 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQGRE3Y652DV7FUFNV4Q2CTVFATKHANCNFSM5TMP2RQA> .
You are receiving this because you were mentioned. <https://github.com/notifications/beacon/AQGRE36HBI5F7TM65UN3LJ3VFATKHA5CNFSM5TMP2RQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOIGCR5FQ.gif> Message ID: ***@***.*** ***@***.***> >
|
|
Great points @gerrymcgovernireland ! Introduction Most of the impact comes from user devices, mostly because their fabrication is very impactful. What we can do about that is to reduce the impact of digital services (and change the way we think about digital as being immaterial and environmentally friendly by default). Evaluating the environmental impact of websites Reducing the impact Analysis by Metrics Checking for the usage of sustainability best practices on the web This covers most of your points, I think. On best practices, we should add "limit/avoid animations" with a focus on avoiding JS in favor of CSS for "essential" animations. |
|
I sent a message to Tom yesterday and another to Tim this morning, hope they will have some time for this! On the impact being mostly on devices, I totally agree and that's what the studies mentioned on my previous comments illustrate. |
|
Hi All, Just getting caught up here. Look forward to collaborating with you all. Per some of the points brought up earlier in this thread: For the Sustainable Web Design model, we based our consumer device use numbers mostly on the Andrae study, which estimates that at 52% of the system with repeat visitors using 25% and loading 2% of data: https://sustainablewebdesign.org/calculating-digital-emissions/ I believe this is reflected in the Green Web Foundation's CO2.js as well, correct @mrchrisadams? Per @gerrymcgovernireland's suggestion to tag waste, we're doing this in the new version of Ecograder by identifying how much of a page's emissions impact is due to uncompressed images, unused code, animations, etc. Happy to discuss details if anyone's interested. Our goal is to launch that a week from today, though work on this will be ongoing. |
|
@timfrick : great to have you onboard! This new feature from Ecograder sounds awesome! I would love to have more info on this. I somehow missed the article on calculating digital emissions, I will read this. |
|
Dear contributors, here is the document containing the outline (WIP) : https://docs.google.com/document/d/1g1ACWRTAzTlcaKKODNASLkXe4zquF-XR5oHh0GfayP8/edit#heading=h.orr5h1m9v3cm |
|
Hello All.
Are we suggesting an analysis and discussion of the sustainability or environmental impacts of hardware used to browse the web? I don't believe that would be in scope as the Archive focuses on how websites are built. We don't collect and have data about the fabrication of user devices (or even user agent data) for us to comment on. But perhaps I misunderstand your suggestion. |
|
This should not be the aim of the analysis (other studies do that pretty well) but we should keep this fact in mind because it is a huge part of the reason why digital services should be as sustainable as possible. The reasoning here is :
This makes Web Almanac the best place to study if websites today are sustainable and show how to reduce their environmental impact with sobriety and efficiency considerations. |
|
That’s great to hear about the messages to Tom and Tim
Sounds fascinating that you’re gathering this data on the devices. I read the article from your link. It’s very impressive. I know Caleb has pointed out correctly that the device is out of scope for this project, but I would love to chat with you more about it as a side conversation, if you had time.
From: LaurentDev ***@***.***>
Sent: Friday 15 April 2022 08:30
To: HTTPArchive/almanac.httparchive.org ***@***.***>
Cc: gerrymcgovernireland ***@***.***>; Mention ***@***.***>
Subject: Re: [HTTPArchive/almanac.httparchive.org] Sustainability 2022 (Issue #2910)
I sent a message to Tom yesterday and another to Tim this morning, hope they will have some time for this!
On the impact being mostly on devices, I totally agree and that's what the studies mentioned on my previous comments illustrate.
This is why, in the company where I currently work, we also gather metrics on real devices. On smartphones, this is a good way to measure the depletion of the battery, which allows us, through an environmental model, to evaluate the global environmental impact of a digital service and the share that is due to device manufacturing.
As of today, this is still (unfortunately) a proprietary methodology and model. More details here : https://greenspector.com/en/environmental-footprint-methodology/
—
Reply to this email directly, <#2910 (comment)> view it on GitHub, or <https://github.com/notifications/unsubscribe-auth/AQGRE36R7X7GXA2JECDEEL3VFELI3ANCNFSM5TMP2RQA> unsubscribe.
You are receiving this because you were mentioned. <https://github.com/notifications/beacon/AQGRE36AIBGY3JI35EQ4ADLVFELI3A5CNFSM5TMP2RQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOIGHZFGQ.gif> Message ID: < ***@***.***> ***@***.***>
|
|
These are good contextual points. I think we can note that heavier and more processing intense pages often contribute to forcing people to upgrade their devices sooner than they would if the pages were lighter and less processing intense. I think this would be good context, without having to go into any research or analysis of specific device impacts.
From: LaurentDev ***@***.***>
Sent: Friday 15 April 2022 14:50
To: HTTPArchive/almanac.httparchive.org ***@***.***>
Cc: gerrymcgovernireland ***@***.***>; Mention ***@***.***>
Subject: Re: [HTTPArchive/almanac.httparchive.org] Sustainability 2022 (Issue #2910)
This should not be the aim of the analysis (other studies do that pretty well) but we should keep this fact in mind because it is a huge part of the reason why digital services should be as sustainable as possible.
The reasoning here is :
* Most of the environmental impact of digital comes from manufacturing our devices
* This gets worse because people around the world own lots of devices and change them too often
* Why do we change our devices? Most of the time, because they lag
* How do we prevent that? By making digital service more sober and efficient => sustainability
This makes Web Almanac the best place to study if websites today are sustainable and show how to reduce their environmental impact with sobriety and efficiency considerations.
—
Reply to this email directly, view it on GitHub <#2910 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQGRE32FW5GVRGSTDNUCOOTVFFXYFANCNFSM5TMP2RQA> .
You are receiving this because you were mentioned. <https://github.com/notifications/beacon/AQGRE32NV5K4W63H36AR6I3VFFXYFA5CNFSM5TMP2RQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOIGJILCY.gif> Message ID: ***@***.*** ***@***.***> >
|
|
Great to see you involved, Tim!
And it would be great to hear more about how you’re identify page waste
From: LaurentDev ***@***.***>
Sent: Friday 15 April 2022 13:24
To: HTTPArchive/almanac.httparchive.org ***@***.***>
Cc: gerrymcgovernireland ***@***.***>; Mention ***@***.***>
Subject: Re: [HTTPArchive/almanac.httparchive.org] Sustainability 2022 (Issue #2910)
@timfrick <https://github.com/timfrick> : great to have you onboard!
This new feature from Ecograder sounds awesome! I would love to have more info on this.
I somehow missed the article on calculating digital emissions, I will read this.
—
Reply to this email directly, view it on GitHub <#2910 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQGRE37CWTKWZ5BPB3YMRHDVFFNUHANCNFSM5TMP2RQA> .
You are receiving this because you were mentioned. <https://github.com/notifications/beacon/AQGRE3354FTK2DWANURAFMDVFFNUHA5CNFSM5TMP2RQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOIGI42FI.gif> Message ID: ***@***.*** ***@***.***> >
|
|
Happy to chat about that at any time, @gerrymcgovernireland |
|
For the Analysis by Metrics section of this chapter, I feel we could also look at aligning with the CMS, eCommerce, and Jamstack chapters to examine how the different (top??) platforms in those categories perform in terms of sustainability. Could look at median size of pages, and also hosting options (can self-host? does managed hosting use known green web hosts?). |
|
FYI we've created a I'd also encourage everyone to request edit access to the planning doc and iterate on the chapter outline there. |
|
@hanopcan : this would be great! |
|
Hi, we're having a kickoff meeting next week to get to know each other and work on the outline. |
|
If possible, @4upz and I would like to volunteer as Analysts. |
|
Excellent. Invited you to the project there. |
|
@ldevernay I think we're good to tick off Milestone 1 in the initial comment? We've a good solid outline there, and although it may change still I think we've enough to say we've reached the milestone. |
|
That's true, thanks @tunetheweb ! |
|
Hey all, apologies I've been a bit quiet lately, but been travelling and not had too much Almanac time lately. How are we looking now? Milestone 2's date has passed by quite a bit now, but the crawl is still going on (not sure if you saw Rick's update on Slack in the Web Almanac channel?), so that gives us a bit of time to catch up. We didn't need to add any new Custom Metrics for this chapter, so we just need to open a draft PR with a list of queries to write to complete that Milestone (note you do not need to have the queries written to complete Milestone 2 - just have a list of them). You can see example open PRs for the other chapters already open. It looks like you've a list of them in the Doc, so just need to firm up the exact metric we want for each of them, and then create a draft PR with the checklist. @fershad @camcash17 @4upz as the analysts for this chapter can one of you do this? This will also focus you to question the rest of the chapter team as to exactly what's wanted if a metric is vague, unclear or ambiguous. |
|
Hey @tunetheweb : as soon as this is done, we can settle to see who writes what. Even without the metrics, we should be able to give some flesh to this chapter. |
|
@fershad @camcash17 @4upz any progress on that draft PR? most of the other chapters have theirs up now. |
|
Hi @tunetheweb, sorry we've been away for most of this week. But currently still working on it, and hoping to have a draft done by early next week! |
|
Ok, just to be clear the current Milestone is just to have the list of queries - not the queries written themselves. You’ve a little more time for them. Just want to make sure everyone’s clear on what queries need written. |
|
Hey all, I see #2989 has been raised. Think we're ready to check off milestone 2 @ldevernay ? Also just to make you aware the data is all i there now (apart from parsed_css if looking for CSS data) so you're good to start querying @fershad @camcash17 @4upz ! Do reach out if you need any help with queryies. |
|
@tunetheweb : yes, I think we can check milestone 2. |
|
OK I've completed the review of the request PR, made a few tweaks (took a couple of liberties, but think it's for the better!), ran (or reran where necessary) all the queries, saved the data, created some charts I think presents the data nicely (though let me know if you want other charts). So I think we're all done with the analysis phase. Over to the writers to copy and past in the charts or data they want to use, and finish writing the chapter! |
|
@tunetheweb : this looks awesome! |
|
The chapter has been converted and edited and is available in the below staging links:
Last call for any changes before it's merged! It's looking great so well done all involved. |
|
The chapter looks great. Hats off to all the Authors. I especially like the Actions You Can Take section. A great list for site owners to get started on, added to the backlog, and make the impactful change for a more sustainable web we are hoping for. Great work All. |
Sustainability 2022
If you're interested in contributing to the Sustainability chapter of the 2022 Web Almanac, please reply to this issue and indicate which role or roles best fit your interest and availability: author, reviewer, analyst, and/or editor.
Content team
Expand for more information about each role 👀
Note: The time commitment for each role varies by the chapter's scope and complexity as well as the number of contributors.
For an overview of how the roles work together at each phase of the project, see the Chapter Lifecycle doc.
Milestone checklist
0. Form the content team
1. Plan content
2. Gather data
3. Validate results
4. Draft content
5. Publication
Chapter resources
Refer to these 2022 Sustainability resources throughout the content creation process:
📄 Google Docs for outlining and drafting content
🔍 SQL files for committing the queries used during analysis
📊 Google Sheets for saving the results of queries
📝 Markdown file for publishing content and managing public metadata
💬 #web-almanac-sustainability on Slack for team coordination
The text was updated successfully, but these errors were encountered: