Performance team meeting summary 21 June 2022

Meeting agenda here and the full chat log is available beginning here on Slack.

Table of Contents

Toggle

Announcements

@shetheliving: 1.2.0 release today!
- If you can, join us for the release party on June 21, 2022 at 1pm EDT in the #performance Slack channel

Focus group updates

Images

@adamsilverstein @mikeschroder

GitHub project

@adamsilverstein: Reviewing the hosting survey results and WebP-related research and drafting a follow-up post about next steps on WebP to be shared soon. Also following up with the WebP team to better understand the quality data that we are seeing in our research in Optimize compression levels for WebP, test file sizes vs. JPEGs #7.
@eugenemanuilov: Addressed code review feedback for the fallback images POC; if anyone can test on their end using old browsers that don’t support WebP, that would be much appreciated
@mukesh27: Awaiting feedback from @flixos90 on Discard WebP image if it is larger than corresponding JPEG image #372
@joegrainger: Been working on some documents that are nearing completion for modifying WordPress core image functions to support multiple mime types and introducing bulk regenerate image sizes functionality into WordPress core
@mehulkaklotar: Working on a proposal for API to facilitate more accurate “sizes” attribute #140
@spacedmonkey: Dominant color functionality will go out in 1.2.0 today. XWP team is already thinking about making a core patch and improving the functionality. Some improvements are in this PR.
- @flixos90: Would be great to start with a feature proposal on Make to get additional feedback ASAP from a wider audience. Now is a great time as people will be able to test with the plugin.

Feedback requested

Needs Discussion (10 issues)
Needs Dev (5 issues)
Needs Review (none)

Object Cache

@tillkruess @spacedmonkey

GitHub project

@spacedmonkey: Committed:
@spacedmonkey: Needs review:
@spacedmonkey: Also been looking into REST API performance, including https://core.trac.wordpress.org/ticket/52992 and wondering if anyone wants to work on https://core.trac.wordpress.org/ticket/48654

Feedback requested

See list above
Needs Discussion (3 issues)
Needs Review (3 issues)

Site Health

N/A

GitHub project

We’re seeking 1-2 POCs for this group; if you’re interested, please comment here or ping in Slack
@shetheliving: Added new autoloaded options section to the Optimization doc and will create a PR to link to it in the autoloaded options Site Health report when ready. Also attended documentation trainings last week and now have edit access for docs, so feel free to loop me in if you need help there.
@mukesh27: PR #380 is ready to merge; @spacedmonkey merged

Feedback requested

Needs Discussion (5 issues)

Measurement

N/A

GitHub project

We’re seeking 1-2 POCs for this group; if you’re interested, please comment here or ping in Slack
@flixos90: Working on a blog post for Make about the plugin checker proposal; should be ready to post early next week

Feedback requested

Proposal for plugin checker
Measurement overview doc
Capturing front-end performance metrics in WordPress doc (for #s 63/64)
Needs Discussion (5 issues)
Needs Review (1 issue)

JavaScript

@aristath @sergiomdgomes

GitHub project

No updates

Feedback requested

Tree-shaking block styles on the frontend #41020
Needs Discussion (2 issues)
Needs Review (3 issues)

Infrastructure

@flixos90

GitHub project

@shetheliving: New module proposal issue template is ready. This is based on the Proposing a new module documentation that we added a few weeks back. If you have a module proposal open right now, you don’t have to update to use this template, but please make sure it includes all of the info that is requested in the template.
@mukesh27: Almost done with Implement mechanism to not load module if core version is available #293 and also working on fixes for Remove plugin option for Multisite #382 and Introduce plugin config for not removing DB setting option when uninstall #383
@flixos90: Use `wp_filesize` instead of filesize if available #344 has been merged and will be included in 1.2.0 and we also previously merged Remove: use of perflab_aea_get_resource_file_size() #380, so we’re now consistently using the new wp_filesize() function

Feedback requested

Needs Discussion (3 issues)
Needs Dev (2 issues)

6.1 release plans

@furi3r: Are we thinking of porting some of the modules to core for 6.1, specifically Site Health?
- @furi3r: Full page cache is not experimental, but fairly new. Autoloaded Options could be a good candidate if we can get the documentation updated.
- @spacedmonkey: Would love to see Autoloaded Options in 6.1
- @flixos90: We can get Object Cache and Full Page Cache in 6.1 if we move them forward, but the other two are more of a stretch. Reminder to review the lifecycle of a performance module doc if you haven’t already.
- @spacedmonkey: Should we create Trac tickets for each of the Site Health modules?
  - @flixos90: That would be good, but main thing is feature proposals
  - @spacedmonkey: Do these even need feature proposals, as additions to an existing feature?
  - @flixos90: Depends on how you frame it. I think they’re large enough to justify feature proposals. Mostly critical to get more feedback around the heuristics being used to determine if a check is “passed” or not.
  - @spacedmonkey: Since they’re small, maybe multiple in one post?
  - @flixos90: For related ones, maybe. Some are larger, e.g. Object Cache and Full Page Cache, and should be their own posts.
  - @spacedmonkey: What about the WebP check? Is that part of the WebP core merge?
  - @flixos90: It’s a bit decoupled, but should go in with the WebP feature if not sooner.
- @flixos90: Who here can work on getting some of the other Site Health modules and/or dominant color merged into core?
  - @spacedmonkey will work on dominant color
  - @furi3r will work on a Make post about the Object Cache and Full Page Cache Site Health checks and @shetheliving will help
- @shetheliving: Tentatively aim to include Autoloaded Options check in 6.2 pending docs