Performance Chat Summary: 13 February 2024
Meeting agenda here and the full chat log is available beginning here on Slack.
Announcements
- Welcome to our new members of #core-performance
- Release 2.9.0 of the Performance Lab plugin is scheduled for Monday February 19
- Call for opinions on the naming of the ‘Image Loading Optimizations’ plugin [see here]
Priority Projects
Server Response Time
- Link to the GitHub project board
- Contributors: @joemcgill @swissspidy @thekt12 @mukesh27 @pereirinha
- Projects from the 2024 roadmap:
- Internationalization Performance
- Improve template loading
Notes from today’s meeting:
- @thekt12 This is something I was working on https://github.com/WordPress/wordpress-develop/pull/5941, new changes has caused some test to fail. The issue is with older test cases. I’ll give a final look tomorrow
- @joemcgill I ran some profiling on the improvements we made to block varations (#59969) and am showing that this has made a noticeable reduction to server response times, e.g. ~5-7%
- @joemcgill Yesterday, I also identified an issue with the new Plugin Dependencies feature that was negatively impacting server timing. #60518 is fixed for beta 1 and it looks like we’ve mostly recovered from the regressions that were previously discovered, but we’ll take new benchmarks after Beta 1 is released today
Database Optimization
- Link to the GitHub project board
- Contributors: @mukesh27 @thekt12 @pbearne
- Projects from the 2024 roadmap:
- Optimized autoloaded options
Notes from today’s meeting:
- No updates this week
JavaScript & CSS
- Link to the GitHub project board
- Contributors: @mukesh27 @flixos90 @westonruter @thelovekesh
- Projects from the 2024 roadmap:
- INP opportunities research
- Interactivity API
- Speculative prerendering
- Embed Optimizer
Notes from today’s meeting:
- @thelovekesh No major updates from my side.
As per @westonruter and@swissspidy feedback, we will be changing the Partytown module name to – Web Worker Offloading - @westonruter For Embed Optimizer, the initial PR has been merged into feature branch: https://github.com/WordPress/performance/pull/886
- @adamsilverstein and the follow up adding tests: https://github.com/WordPress/performance/pull/979
- @westonruter Several other pull requests have been merged
- @westonruter There’s also a label now in GitHub
Images
- Link to the GitHub project board
- Contributors: @flixos90 @adamsilverstein @joemcgill @pereirinha @westonruter
- Projects from the 2024 roadmap:
- Image loading optimization
- API to facilitate more accurate “sizes” attribute
- Land AVIF support in core
- Client side image compression
Notes from today’s meeting:
- @adamsilverstein one more image optimization landed for 6.5: support for progressive images – see https://core.trac.wordpress.org/ticket/21668#comment:64. Right now this requires opting in although it was suggested on the ticket that if the upload is progressive, the output should automatically be progressive. Also, we might want to consider a Performance Lab plugin that turns on progressive images by default.
- @adamsilverstein although progressive images tend to be around the same size or only slightly smaller (for JPEGs anyway), the perceived performance gain is huge, and not to be underestimated
- @westonruter For Image Loading Optimization, several improvements and fixes landed over the past week, currently working on using classes for common objects: https://github.com/WordPress/performance/issues/933)
- @westonruter we have 7 responses to the survey for a new name for Image Loading Optimization. Thank you. I welcome more!
Measurement
- Link to the GitHub project board
- Contributors: @adamsilverstein @joemcgill @mukesh27 @swissspidy @flixos90
- Projects from the 2024 roadmap:
- Stabilized automated performance testing metrics
- Improve core automated performance tests
Notes from today’s meeting:
- @joemcgill Nothing specific to report against those milestones. Now that we’re getting into the part of the release cycle where we’ll be doing lots of benchmarks, I suspect we’ll identify some opportunities to streamline things a bit. I also think that @oandregal was working on some improvements to the GB tests that would have caught some regressions that were not caught until after the sync. I’d be curious to know if there are ways we can support that work for the future?
- @joemcgill Some initial performance benchmarks for 6.5-beta1 against 6.4.3, for anyone interested:
Ecosystem Tools
- Link to the GitHub repo for Plugin Checker
- Contributors: @mukesh27 @swissspidy
- Projects from the 2024 roadmap:
- Creating standalone plugins milestone 2
- Plugin checker
- Reusable testing environment
Notes from today’s meeting:
- @mukesh27 for Creating standalone plugins milestone 2b:
- Move
auto-sizesto plugins folder Ready for another round of review - Working on Implement publishing workflow for standalone plugins that aren’t modules
- Move
- @thelovekesh PR for adding CodeQL analysis on JS files – https://github.com/WordPress/performance/pull/981
- @mukesh27 For Plugin Checker, nothing more, just been offering support by conducting code reviews for open PRs
Open Floor
- Suggestion from @joemcgill and @swissspidy to rethink the structure of the chat to align with the Core Dev Chat
- For the past couple of weeks, the Core Dev-chat has attempted to spend more time synchronously discussing a proposal or pending issue, and having most updates linked in the agenda with the expectation that folks are reading the information ahead of the meeting. So far, it’s led to more engaging chats. Perhaps there are ways to do something similar here?
- @clarkeemily is away on holiday next week, so @joemcgill will run the chat
Our next chat will be held on Tuesday, February 20, 2024 at 16:00 UTC in the #core-performance channel in Slack.
