Performance Chat Summary: 17 October 2023

Meeting agenda here and the full chat log is available beginning here on Slack.
Announcements
- Welcome to our new members of #core-performance
- WordPress 6.4 Release Candidate 1 is today
- Dev notes discussion
- @joemcgill We started tracking these in this GH issue: https://github.com/WordPress/performance/issues/840
- @flixos90 updated dev notes ready for review in this Slack thread
- Two other dev notes for the docs team to review please @webcommsat
- Object Caching – requires some changes to be owned by @westonruter
- Template Loading – required some changes to be owned by @westonruter
- @flixos90 to draft the field guide performance section
- Dev notes discussion
- Reminder about the Performance Hallway Hangout this week Thursday, October 19, 2023 at 04:00 PM GMT+1
Priority Projects
Server Response Time
Contributors: @joemcgill @swissspidy @thekt12 @mukesh27
- @joemcgill has been reviewing 6.5 priorities
- @swissspidy opened #59656 to track merging Performant Translations into WP 6.5
- We plan to pick up work on improving Template Loading (see: https://github.com/WordPress/performance/issues/746)
- I’ll be doing another profiling analysis of 6.4 during RC to see what other issues should be prioritized
Database Optimization
Contributors: @mukesh27 @thekt12
- @thekt12 Bug (needs unit tests before going for review #59661
- @thekt12 also completed my analysis
get_posts
#59516 Found that for WP_Queryfields
is the only key that results in modification after cache key generation. I’ll add a writeup shortly - @joemcgill There were several updates made in 6.4 related to autoloaded options, but I know there are a few more things planned. @flixos90 are there updates that need to be made to this tracking issue?
JavaScript & CSS
Contributors: @mukesh27 @10upsimon @westonruter
- @westonruter there were a couple of late changes that were fixed last week
- @mukesh27 We hope to commence the process of removing jQuery usage from the frontend in WordPress default themes for version 6.5 [Link to tickets]
- @pereirinha I’ve been doing research on #59595. I might have a good idea of how to improve it. I hope to have more news later in the week, where I plan to share the findings and potential solutions.
Images
Contributors: @flixos90 @thekt12 @adamsilverstein @joemcgill @pereirinha
- @adamsilverstein I opened a couple of small bugs related to our fetchpriority handling #59641 and #59638
- @adamsilverstein I have one more in the works to cover issues where images are used in layouts that change their size for example in columns
- @joemcgill We discussed background images last week, but I’m unsure if we ever opened a ticket for that which is here https://github.com/WordPress/gutenberg/pull/53934#issuecomment-1756213964
Measurement
Contributors: @adamsilverstein @joemcgill @mukesh27 @swissspidy @flixos90
- @swissspidy WordPress core end-to-end and performance tests now use Playwright — see #59517 for details
Ecosystem Tools
Contributors: @mukesh27 @swissspidy @westonruter
- @mukesh27
- PR Add
Trademarks_Check
285 – Merged - Bump minimum required PHP version to 7.0 and minimum required WP version to 6.3 – Merged
- Working on Refactoring and Code Duplication Reduction for
Plugin_Readme_Check
andTrademarks_Check
- PR Add
Creating Standalone Plugins
Contributors: @flixos90 @mukesh27 @10upsimon
- @10upsimon Priorities for me at the moment:
- Implement migration logic and UI from old PL modules to new standalone plugins in PL settings screen #652
- Final stages of prep for PR
- Have opened a feature branch and 2 PR’s (one with and one without plugin update UI actions)
- Implement migration logic and UI from old PL modules to new standalone plugins in PL settings screen #652
- Following on from the above issue 652
- Exclude
.wordpress-org
directory when deploying standalone plugins #850
- Implement migration logic and UI from old PL modules to new standalone plugins in PL settings screen #652
Open Floor
- n/a
Our next chat will be held on Tuesday, October 24, 2023 at 15:00 UTC in the #core-performance channel in Slack.