Performance Chat Summary: 19 December 2023


Meeting agenda here and the full chat log is available beginning here on Slack.
Announcements
- Welcome to our new members of #core-performance
- Call for 2024 roadmap priorities https://github.com/WordPress/performance/issues/903
- Highlighting this recent post on WordPress performance impact on Core Web Vitals in 2023
- Reminder there will be no Slack meeting on Tuesday December 26
Priority Projects
Server Response Time
Link to roadmap projects and link to the GitHub project board
Contributors: @joemcgill @swissspidy @thekt12 @mukesh27 @pereirinha
- @thekt12 several updates
- Need someone from GB team to review – #59969
- PR is ready for review – https://github.com/WordPress/wordpress-develop/pull/5281
- Continuing research on – #59719
- Need to review (to start) – https://core.trac.wordpress.org/ticket/60025#comment:6
- @joemcgill On the lazy-loading variations ticket, I did hear from @mamaduka yesterday that he plans on reviewing that ticket soon, as he’s been off for the past few weeks.
- @joemcgill Related to work we did in 6.4, I’ve been tracking some follow-up bugs that were reported due to the deprecation of
STYLESHEETPATH
andTEMPLATEPATH
env vars, and would appreciate a second opinion. See: https://wordpress.slack.com/archives/C02KGN5K076/p1702953637418849- @thekt12 will check this today
Database Optimization
Link to roadmap projects and link to the GitHub project board
Contributors: @mukesh27 @thekt12
- No updates this week
JavaScript & CSS
Link to roadmap project and link to the GitHub project board
Contributors: @mukesh27 @flixos90 @westonruter
- @flixos90 No real update, just that I’m currently experimenting with the Interactivity API, specifically to use it in classic default themes to replace more manual custom JS. Partly to familiarize myself with the API, partly for a first prototype of something we could potentially do in the future. Should have a first draft PR up for later today. Really for reference more than anything
Images
Link to roadmap projects and link to the GitHub project board
Contributors: @flixos90 @adamsilverstein @joemcgill @pereirinha @westonruter
- @joemcgill Last week I put together a small experiment to see how the new auto-sizes for lazy-loaded images feature is working now that it’s being implemented in browsers. Based on that exploration, I put together an initial module implementation that can already be used for testing. I plan to update the PR this week.
- Related – I also opened a new issue to discuss how we want to handle new modules once the unbundling project is complete. Feedback would be appreciated.
Measurement
Link to roadmap projects and link to the GitHub project board
Contributors: @adamsilverstein @joemcgill @mukesh27 @swissspidy @flixos90
- No updates this week
Ecosystem Tools
Link to roadmap projects and link to the GitHub repo for Plugin Checker
Contributors: @mukesh27 @swissspidy
- @mukesh27 For the Plugin Check, I have been addressing issue 342 and have opened PR 347, which is now ready for review and I also supported in code review process. Moreover, there is positive news that some community contributors are actively working on several issues and have raised corresponding PRs for them.
Creating Standalone Plugins
Contributors: @flixos90 @mukesh27
- @mukesh27 We are on the cusp of completing Milestone 2a issues for Creating Standalone Plugins.
- The following PRs have been successfully merged:
- Implemented migration logic and UI from old PL modules to new standalone plugins in the PL settings screen #652 – Merged
- Enhanced the user experience during the installation _and_ activation of standalone plugins #880 – Merged
- Follow-up: Minor changes for creating standalone plugins #912 – Merged
- Implementing an admin pointer to prompt users to activate the new standalone plugins #653 – Merged
- The following PRs have been successfully merged:
Open Floor
- @desrosj I noticed that the performance tests started failing in some older branches while working on some E2E test related changes. Well, it only seems to be happening for the 6.4 branch currently. But I’m wondering if the needed conditions just haven’t been met for the other branches.
- @joemcgill I’m only seeing the latest commit fail according to this list. Am I looking at the wrong thing?
- @desrosj That’s accurate. I was confusing the additional E2E failures with something (potentially) unrelated that I’ve fixed separately. #60095 is what I was working on. The step that is failing seems to be checking 6.1.1 for a baseline if I’m reading it correctly.
- @joemcgill I’m going to try rerunning that one, since the same commit to the 6.3 branch worked fine.
- @desrosj
- FWIW, I committed the fix for 60095 in the 6.1 branch this morning, and this workflow was from yesterday. Maybe the re-run does not include changes for the other branch because they were not there when this change was made? Started a manual run for 6.4 to try and rule that out.
Our next chat will be held on Tuesday, January 2, 2024 at 16:00 UTC in the #core-performance channel in Slack.