Performance Chat Summary: 5 December 2023

Performance Chat Summary: 5 December 2023

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

Announcements

Priority Projects

Server Response Time

Link to roadmap projects and link to the GitHub project board

Contributors: @joemcgill @swissspidy

@thekt12 @mukesh27 @pereirinha

  • @joemcgill #58196 has a PR that could use another set of eyes, but can probably be committed. However, turns out this does not solve a big performance issue, but instead the parent function needs to be looked into instead.
  • @swissspidy For i18n performance I am nagging people for code reviews again at the moment. Otherwise there hasn’t really been any progress.
  • @joemcgill I was reviewing #55595 earlier today, and noticed that widget registration itself does not really account for much of a performance cost, but rather rendering widgets that can be costly. I think we can likely close that ticket as `maybelater` but would like a 2nd opinion.
    • Additionally, I noticed that you can already use the `load_default_widgets` filter to keep WP from loading default widgets, but doing so will cause a fatal if you don’t also unhook `wp_widgets_init`, because that function will try to register the default widgets even if they haven’t been loaded. This seems like a bug, although not a critical one.
  • @thekt12 Removing call to build_template_part_block_variations on the fontend showed a decent performance improvement -> https://core.trac.wordpress.org/ticket/59969#comment:8 Additionally we did identify two more palaces where the same improvement could be made. Currently I am addressing PR review comments.

Database Optimization

Link to roadmap projects and link to the GitHub project board

Contributors: @mukesh27 @thekt12

JavaScript & CSS

Link to roadmap project and link to the GitHub project board

Contributors: @mukesh27 @flixos90 @westonruter

Images

Link to roadmap projects and link to the GitHub project board

Contributors: @flixos90 @adamsilverstein @joemcgill @pereirinha @westonruter

  • @westonruter Pull request for applying the image optimizations is in review and nearing merge (to the feature branch)
    • I also have sub-PR opened which makes breadcrumb processing more reliable. (In other words, an XPath for a given image that needs optimization.) Also ready for review.
    • Now that the feature is fully functional I’m going to add test coverage (which I neglected before getting a working prototype in place).
    • I also want to extend the existing logic to also handle CSS background images, whereas currently only img elements are optimized.
    • I’ve also started filing issues under the module’s label for areas where others can contribute.
  • @joemcgill Still working on a proposal for improving the default sizes implementation in WP using available layout data. Also, seeing some progress being made on the browser side implementing the new auto sizes HTML spec, which would be a huge improvement for WP, since we lazy-load many images by default.
  • @swissspidy As for images, I have been looking a bit more into client-side image compression (in Gutenberg) lately to see where this could fit in 2024 plans.

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

Contributors: @mukesh27 @swissspidy

  • @swissspidy No update either from my side, though I just published a small blog post to help spread the word a little bit about Plugin Check

Creating Standalone Plugins

Link to GitHub overview issue

Contributors: @flixos90 @mukesh27

Open Floor

Our next chat will be held on Tuesday, December 12, 2023 at 16:00 UTC in the #core-performance channel in Slack.

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

Leave a Reply

Your email address will not be published. Required fields are marked *