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

Announcements

• Welcome to our new members of #core-performance
• RC3 is scheduled for release later today
• Video from the Hallway Hangout that occurred last week is available for those who were not able to attend.
• Please read and leave feedback on this follow-up post by @tellthemachines about how to improve the release workflow between the Gutenberg and Core repos during the release process

class=”wp-block-heading” id=”focus-group-updates”>Priority Projects

Server Response Time

Link to roadmap projects

Contributors: @joemcgill @spacedmonkey @aristath @swissspidy

• @joemcgill and @mukesh27 are working on an exploration of how to improve template loading of classic and block themes. Ideas are welcome.
• @swissspidy is still looking for feedback on this post about i18n performance improvements

Database Optimization

Link to roadmap projects

Contributors: @aristath @spacedmonkey @olliejones

• N/A

JavaScript & CSS

Link to roadmap project

Contributors: @mukesh27 @10upsimon @adamsilverstein @westonruter

• @weston has been working on adding async/defer to more places in core
  • Merged this PR that used defer for all block view scripts
  • Committed the use of async for the comment-reply script in core
  • Proposed adding defer to the wp-embed script, even though his analysis didn’t show much performance benefit.
• @weston reported that now that HTTP Archive has custom metrics for WordPress scripts, he’s been starting to dive into doing queries for how well sites are using the scripts API, including to what degree they’re using $in_footer and how many are currently using async and defer even before our official way of doing so
• He’s also been doing some research into which specific plugins are responsible for those blocking_in_head scripts. So we’ll have some opportunities for ecosystem outreach hopefully soon
• Review/feedback on his HTTP Archive queries would be appreciated
  • Later in the meeting, Weston followed up to share that Felix had identified a flaw in the query he was using go get counts of scripts using async and defer from the HTTP Archive. He plans to revise and share updated results

Images

Link to roadmap projects

Contributors: @flixos90 @thekt12 @adamsilverstein @joemcgill

• @flixos90 opened several smaller follow-up tickets for the lazy-loading and fetchpriority work last week:
  • https://core.trac.wordpress.org/ticket/58891 (PR for review)
  • https://core.trac.wordpress.org/ticket/58892
  • https://core.trac.wordpress.org/ticket/58893
  • https://core.trac.wordpress.org/ticket/58894
  • @joemcgill added one additional: https://core.trac.wordpress.org/ticket/58895
  • Plans to follow up on https://core.trac.wordpress.org/ticket/58853
• @joemcgill opened an issue in the Performance Lab repo for a module proposal to support auto-sizes for lazy-loaded images. Feedback welcome.

Measurement

Link to roadmap projects

Contributors: @adamsilverstein @olliejones @joemcgill @mukesh27 @swissspidy

• @flixos90 plans to do another round of benchmarks for RC3 after the release today

Ecosystem Tools

Link to roadmap projects

Contributors: @mukesh27 @swissspidy @westonruter

• @mukesh27 has been working on some follow-up issues for the Plugin Checker and requested feedback
  • PR #237 – Ignore .git, node_modules, and vendor directories from the checks
  • PR #238 – Fix errors detected by Plugin Checker
  • PR #239 – Incorrect display of readme.txt instead of readme.md in Plugin Readme check

Creating Standalone Plugins

Link to GitHub overview issue

Contributors: @flixos90 @mukesh27 @10upsimon

• N/A

Open Floor

• N/A

Our next chat will be held on Tuesday, August 8, 2023 at 15:00 UTC in the #core-performance channel in Slack.

#core-performance, #performance, #performance-chat, #summary