Performance team meeting summary 7 June2022

Table of Contents

Announcements

Huge thank you to everyone who participated in any way in our work at WCEU! Feedback was extremely positive and we have lots of new people who are interested in contributing
Our weekly chat is held in the #performance channel on Tuesdays at 15:00 UTC and our GitHub repo is here; feel free to take a look at open issues and add new issues
You can watch @flixos90‘s talk from WCEU here

@shetheliving: Focused on continuing to move Create WebP images on upload #22 forward in prep for posting a follow-up post to Make in the next few weeks. We’ll review all of the research in Research: Impact of additional WebP images on upload #289 and Research: WebP compatibility #290 as well as the results of the hosting provider survey to determine and outline next steps. Also moving forward on exploration and definition for Regenerate existing images #24.
@spacedmonkey: @flixos90 and @pbearne worked a lot on Add low quality image placeholders using background color #19 at WCEU and it’s getting close, looks like it could be ready for 1.2.0. Flagging Add async decoding attribute as default to the HTML image tags generated by WordPress #86 as very close; the core ticket really helps with time to first paint, so it would be great to get this done. Also want to flag Allow SVG upload (if SVG contains no scripting) #357 for future discussion.
- @codekraft: Have discussed this in #core-media previously and it did not move forward
@mitogh: Back up edited full image sources when restoring the original image #314 is ready for another review and have been working on tests around WP image resizing can result in a larger file size than the original. #264 to see if I can find a workaround

N/A

We’re seeking 1-2 POCs for this group; if you’re interested, please comment here or ping in Slack
@shetheliving: Add Site Health test for full page caching (advanced cache) #220 is ready for 1.2.0 and @flixos90 and I are working on moving Create Autoloaded Options Core Documentation #234 forward with the Documentation team in Add new Autoloaded options section to Optimization article #358

N/A

We’re seeking 1-2 POCs for this group; if you’re interested, please comment here or ping in Slack
No updates

@aristath (async): Working on ways to apply some tree-shaking to block styles. Created a proof of concept in Tree-shaking block styles on the frontend #41020 and would appreciate feedback. Also working on an alternative method which would not require API changes to block.json, but worried about server-side performance. Current implementation in the POC is far from perfect but enough to be a good conversation starter to move this forward.
- @mitogh: Will take a look at this

@flixos90 offline
@shetheliving: Reminder that next release will be 1.2.0 on Monday, June 20, so we should target merge for anything for that release by about June 15.
@shetheliving: If you haven’t already, please review and leave feedback on @flixos90‘s proposal for a WordPress plugin checker
- @jeffpaul: Seems like something that could get added into that existing checks that #tide runs, or maybe that was purposely left out?
- @clarkeemily: Might be good to add as a comment to ask Felix
- @jeffpaul: Cannot leave comments on this doc
- @shetheliving: I’ll check permissions post-meeting