Performance Chat Summary: 27 June 2023

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

Table of Contents

Toggle

Announcements

Welcome to our new members of #core-performance
Beta 1 for the 6.3 release is today!

Priority Projects

@joemcgill I’m happy to be able to report that I committed the PR for https://core.trac.wordpress.org/ticket/12009 yesterday, closing a 13 year old ticket. This is a big milestone for the team, thank you to everyone who contributed to get this across the line. I know that there is still a desire to extend support to inline scripts, so I’ve opened a new ticket (https://core.trac.wordpress.org/ticket/58632) for that discussion.
@10upsimon is drafting a dev-note for this change, which we can hopefully post in the next few weeks.
@spacedmonkey I had people asking me questions about module support. – https://core.trac.wordpress.org/ticket/56313 I wonder if this should be something we look into for WP 6.4
- @joemcgill Seems like the logical next step. Would be nice to do in coordination with packages from Gutenberg that want to make use of it.
- @flixos90 Yeah I know the folks working on the new interactivity API were quite interested in this one
- @clarkeemily let’s look at adding this to our roadmap in a future chat
- @spacedmonkey The important thing about this functionality is the developer communication. We need a great dev note, with easy to understand and copy and paste implementations. We will also have to show developers how we can make the change and be backwards compatible.

Images

Link to roadmap projects

Contributors: @flixos90 @thekt12 @adamsilverstein @joemcgill

@flixos90 Excited to share that yesterday we landed fetchpriority="high" support: https://core.trac.wordpress.org/changeset/56037
- That commit includes notable refactoring to make the logic that was previously scoped to only lazy-loading more broadly available, as it is also required for fetchpriority
- So with that refactoring it also unblocks a fix to another issue that still needs to be addressed with lazy-loading: https://core.trac.wordpress.org/ticket/58635
- I’m planning to work on dev notes for these changes. Still thinking through whether it should be two individual dev notes or a single one. While they are separate topics, they are deeply intertwined, and especially with the refactoring it may be a lot of repetition to have two separate posts
  - @joemcgill I think a single dev note would be good
  - @spacedmonkey One dev note for image related changes.

Measurement

Link to roadmap projects

Contributors: @adamsilverstein @olliejones @joemcgill @mukesh27

@joemcgill Nothing here either. Though, once the dust settles on beta release day, I’d like to revisit improvements we can make to the automated testing tools during this release cycle, to better support the RC cycle.

Ecosystem Tools

Link to roadmap projects

Contributors: @joegrainger @mukesh27

@mukesh27 and @joegrainger are currently prioritizing tasks for Milestone 2 of the Plugin Checker. Progress can be seen on the GitHub repo here. Feel free to take a look and leave any thoughts/ideas you may have in the repo. Thanks!

Creating Standalone Plugins

Link to GitHub overview issue

Contributors: @flixos90 @mukesh27 @10upsimon

@flixos90 Still awaiting approval of the Dominant Color Images plugin in the plugin repo

Open Floor

@clarkeemily our next chat is on July 4 Independence Day in the US, so I suspect a large portion of folks will be out. I still plan to run the chat, but a heads up that it will likely be much shorter as many folks will be out
@mukesh27 highlighted the message from @johnbillion
- #21938 has been re-opened with the performance focus added, the e2e tests are indicating a potential performance regression that needs testing in different browsers and configurations
- @johnbillion Ah yes ^ . Some of you might have seen the core and Gutenberg e2e tests are flakier than usual at the moment and it may be due to the no-store cache header directive that was added last week. I’ve reopened the ticket and added the performance focus, if anyone has time to do some testing that would be greatly appreciated.
- @joemcgill I remember looking at this last week when I opened the bug ticket about the E2E tests, and I was not convinced that the failures were related to that change, so this might be a red herring. I recall seeing several instances of network timeouts showing up prior to that change.
- @johnbillion I agree it could be a red herring, but git bisect does point to that commit, so I’m honestly not sure. Although the core e2e tests did start failing before that commit, so..
- @joemcgill I think we can certainly try revering that change to see if the tests stop failing. Are there other steps to take to try and debug this issue?
- @johnbillion I added some testing steps in a comment on the ticket, I don’t have much else at the moment
@westonruter On another front, I believe I’ve addressed the last code review for optimizing the emoji loader. Final reviews/testing appreciated so I can commit in the next hour: https://github.com/WordPress/wordpress-develop/pull/4562