<div style="text-align:center"></div><div>
<p><a href="https://make.wordpress.org/core/2023/06/20/performance-chat-agenda-20-june-2023/">Meeting agenda here</a> and the full chat log is available <a href="https://wordpress.slack.com/archives/C02KGN5K076/p1687273193141669">beginning here on Slack</a>.</p>
<h2 class="wp-block-heading">Announcements</h2>
<ul>
<li>Welcome to our <strong>new members</strong> of <a href="http://wordpress.slack.com/messages/core-performance/">#core-performance</a> [<a href="https://wordpress.slack.com/archives/C02KGN5K076/p1687273321335899">Slack thread</a>]</li>
<li>Release 2.4.0 scheduled for later today
<ul>
<li>Agreed to <strong>postpone this to Tuesday June 20 </strong>to support several team members being out for the US holiday</li>
</ul>
</li>
<li>Upcoming <strong>Beta 1 for the 6.3 release on Tuesday June 27, 2023</strong></li>
<li>Updates to our Core Performance Handbook with the introduction of the <a href="https://make.wordpress.org/performance/handbook/measuring-performance/profiling-php-performance-with-xhprof/">Profiling PHP performance with XHProf</a> article</li>
</ul>
<h2 class="wp-block-heading" id="focus-group-updates">Priority Projects</h2>
<h3 class="wp-block-heading" id="images">Server Response Time</h3>
<p><a href="https://make.wordpress.org/performance/roadmap-2023/#category-server-response-time">Link to roadmap projects</a></p>
<p>Contributors: <a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> <a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a> <a href="https://profiles.wordpress.org/aristath/" class="mention"><span class="mentions-prefix">@</span>aristath</a></p>
<ul>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a>:
<ul>
<li>Committed
<ul>
<li><a rel="noreferrer noopener" href="https://github.com/WordPress/wordpress-develop/commit/3e2121c83de37335bcda944a09c2d1a8f11dab7b" target="_blank">https://github.com/WordPress/wordpress-develop/commit/3e2121c83de37335bcda944a09c2d1a8f11dab7b</a></li>
<li><a rel="noreferrer noopener" aria-describedby="qtip-75" href="https://github.com/WordPress/wordpress-develop/commit/ea0a4881aeaa97c09bdab0ba7d3895dc29ea6247" target="_blank">https://github.com/WordPress/wordpress-develop/commit/ea0a4881aeaa97c09bdab0ba7d3895dc29ea6247</a></li>
<li><a rel="noreferrer noopener" href="https://github.com/WordPress/wordpress-develop/commit/a14bc9b298b59c9d05f36038358e0a1ea5087c32" target="_blank">https://github.com/WordPress/wordpress-develop/commit/a14bc9b298b59c9d05f36038358e0a1ea5087c32</a></li>
<li><a rel="noreferrer noopener" data-hasqtip="79" aria-describedby="qtip-84" href="https://github.com/WordPress/gutenberg/pull/50636" target="_blank">https://github.com/WordPress/gutenberg/pull/50636</a></li>
</ul>
</li>
<li>Near commit
<ul>
<li><a rel="noreferrer noopener" href="https://core.trac.wordpress.org/ticket/57832" target="_blank">https://core.trac.wordpress.org/ticket/57832</a></li>
</ul>
</li>
<li>In need of code review
<ul>
<li><a rel="noreferrer noopener" href="https://github.com/WordPress/wordpress-develop/pull/4641" target="_blank">https://github.com/WordPress/wordpress-develop/pull/4641</a><br /><a rel="noreferrer noopener" href="https://github.com/WordPress/wordpress-develop/pull/4621" target="_blank">https://github.com/WordPress/wordpress-develop/pull/4621</a><br /><a rel="noreferrer noopener" href="https://github.com/WordPress/wordpress-develop/pull/3528" target="_blank">https://github.com/WordPress/wordpress-develop/pull/3528</a></li>
</ul>
</li>
<li>New tickets created
<ul>
<li><a rel="noreferrer noopener" href="https://core.trac.wordpress.org/ticket/58576" target="_blank">https://core.trac.wordpress.org/ticket/58576</a></li>
<li><a rel="noreferrer noopener" aria-describedby="qtip-142" href="https://core.trac.wordpress.org/ticket/58560" target="_blank">https://core.trac.wordpress.org/ticket/58560</a></li>
<li><a rel="noreferrer noopener" data-hasqtip="139" href="https://core.trac.wordpress.org/ticket/58525" target="_blank">https://core.trac.wordpress.org/ticket/58525</a></li>
<li><a rel="noreferrer noopener" href="https://core.trac.wordpress.org/ticket/58528" target="_blank">https://core.trac.wordpress.org/ticket/58528</a></li>
</ul>
</li>
</ul>
</li>
</ul>
<h3 class="wp-block-heading" id="images">Database Optimization</h3>
<p><a href="https://make.wordpress.org/performance/roadmap-2023/#category-database-optimization">Link to roadmap projects</a></p>
<p>Contributors: <a href="https://profiles.wordpress.org/aristath/" class="mention"><span class="mentions-prefix">@</span>aristath</a> <a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a> <a href="https://profiles.wordpress.org/olliejones/" class="mention"><span class="mentions-prefix">@</span>olliejones</a> </p>
<ul>
<li>No updates this week</li>
</ul>
<h3 class="wp-block-heading" id="object-caching">JavaScript &#038; CSS</h3>
<p><a href="https://make.wordpress.org/performance/roadmap-2023/#category-javascript-css">Link to roadmap project</a></p>
<p>Contributors: <a href="https://profiles.wordpress.org/mukesh27/" class="mention"><span class="mentions-prefix">@</span>mukesh27</a> <a href="https://profiles.wordpress.org/10upsimon/" class="mention"><span class="mentions-prefix">@</span>10upsimon</a> <a href="https://profiles.wordpress.org/adamsilverstein/" class="mention"><span class="mentions-prefix">@</span>adamsilverstein</a> <a href="https://profiles.wordpress.org/westonruter/" class="mention"><span class="mentions-prefix">@</span>westonruter</a></p>
<ul>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> For Script Loading Strategy: <a rel="noreferrer noopener" href="https://core.trac.wordpress.org/ticket/12009" target="_blank">https://core.trac.wordpress.org/ticket/12009</a>
<ul>
<li>Most of the PR for adding support for `async` and `defer` has been approved for commit. Unfortunately, keeping in support for inline scripts is blocking the current PR, so we’re going to remove that part of the implementation this week and commit the rest. This just means that if anyone tries to add an `async` or `defer` strategy to a handle that has an inline script attached in an `after` position, the original script will be loaded with a blocking strategy instead.</li>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a> I code reviewed the above and approved it for commit</li>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> we will likely ask for another review once we’ve implemented the changes</li>
<li><a href="https://profiles.wordpress.org/10upsimon/" class="mention"><span class="mentions-prefix">@</span>10upsimon</a> Nothing more from my side, I’ll be working with <a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> on the reversal of delayed after inline scripts, and further testing</li>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a> Should we talk about the comment – <a rel="noreferrer noopener" href="https://github.com/WordPress/wordpress-develop/pull/4391#issuecomment-1598421109" target="_blank">https://github.com/WordPress/wordpress-develop/pull/4391#issuecomment-1598421109</a> . Or leave it open floor. I think this should be in core and I want to work out a path to unblock it</li>
<li><a href="https://profiles.wordpress.org/10upsimon/" class="mention"><span class="mentions-prefix">@</span>10upsimon</a> this is the same level of push back we’re receiving on the <a rel="noreferrer noopener" href="https://core.trac.wordpress.org/ticket/12009" target="_blank">Trac ticket itself</a>. It’s a long standing aversion to support delayed inline scripts. I’d like to see it in core as well, if possible.</li>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> I think we’ve exhausted this conversation for now. The focus this week should be to get the majority of this feature committed and we can advocate for extending support for inline scripts during the beta period.</li>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a> Could it be commit before the beta and then if we can resolve the inline style stuff, then we can do a part revert?</li>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> Andrew has indicated in the PR thread that we could continue that conversation during the beta period, yes</li>
</ul>
</li>
</ul>
<h3 class="wp-block-heading" id="measurement">Images</h3>
<p><a href="https://make.wordpress.org/performance/roadmap-2023/#category-images">Link to roadmap projects</a></p>
<p>Contributors: <a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> <a href="https://profiles.wordpress.org/thekt12/" class="mention"><span class="mentions-prefix">@</span>thekt12</a> <a href="https://profiles.wordpress.org/adamsilverstein/" class="mention"><span class="mentions-prefix">@</span>adamsilverstein</a> <a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a></p>
<ul>
<li><a href="https://profiles.wordpress.org/adamsilverstein/" class="mention"><span class="mentions-prefix">@</span>adamsilverstein</a> Some recent developments on the modern image front: the new version of Safari includes JpegXL support which was a bit of a surprise and somewhat exciting. If other browsers follow suit, maybe the format will become useful for the web and WordPress?! In addition, Edge canary has apparently added AVIF support, so we will hopefully see all major browsers supporting AVIF soon. I created a patch to add AVIF support to core on the existing ticket that is ready for testing – <a rel="noreferrer noopener" href="https://core.trac.wordpress.org/ticket/51228" target="_blank">https://core.trac.wordpress.org/ticket/51228</a></li>
<li><a href="https://profiles.wordpress.org/thekt12/" class="mention"><span class="mentions-prefix">@</span>thekt12</a> and <a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> are also working on finalising <a rel="noreferrer noopener" href="https://github.com/WordPress/wordpress-develop/pull/4495" target="_blank">https://github.com/WordPress/wordpress-develop/pull/4495</a> this week
<ul>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a> I have been code review and profiling this. We are awaiting a new version that improves PHP performance.</li>
</ul>
</li>
</ul>
<h3 class="wp-block-heading" id="javascript">Measurement</h3>
<p><a href="https://make.wordpress.org/performance/roadmap-2023/#category-measurement">Link to roadmap projects</a></p>
<p>Contributors: <a href="https://profiles.wordpress.org/adamsilverstein/" class="mention"><span class="mentions-prefix">@</span>adamsilverstein</a> <a href="https://profiles.wordpress.org/olliejones/" class="mention"><span class="mentions-prefix">@</span>olliejones</a> <a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> <a href="https://profiles.wordpress.org/mukesh27/" class="mention"><span class="mentions-prefix">@</span>mukesh27</a></p>
<ul>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> Over the weekend, the Theme Unit Test data that we rely on briefly went offline and broke the automated performance tests in Core. There is an open ticket about bringing that code directly into our repo, rather than relying on the Theme Unit Test data, but there is also conversation happening about moving all of that code into the WP organization. Original thread: <a rel="noreferrer noopener" href="https://wordpress.slack.com/archives/C02RQBWTW/p1687140431658569" target="_blank">https://wordpress.slack.com/archives/C02RQBWTW/p1687140431658569</a> For now, I don’t think we need to take immediate action, but is something to consider over the coming weeks.</li>
</ul>
<h3 class="wp-block-heading">Ecosystem Tools</h3>
<p><a href="https://make.wordpress.org/performance/roadmap-2023/#category-ecosystem-tools">Link to roadmap projects</a></p>
<p>Contributors: <a href="https://profiles.wordpress.org/joegrainger/" class="mention"><span class="mentions-prefix">@</span>joegrainger</a> <a href="https://profiles.wordpress.org/mukesh27/" class="mention"><span class="mentions-prefix">@</span>mukesh27</a></p>
<ul>
<li><a href="https://profiles.wordpress.org/joegrainger/" class="mention"><span class="mentions-prefix">@</span>joegrainger</a> We are working on the last check for Milestone 2 for the <a rel="noreferrer noopener" href="https://github.com/10up/plugin-check/" target="_blank">Plugin Checker</a>. Once complete we’ll be moving onto further QA/Testing and remediating over this week and next. Progress can be seen on the <a rel="noreferrer noopener" href="https://github.com/10up/plugin-check/" target="_blank">GitHub repo</a> here. Feel free to take a look and leave any thoughts/ideas you may have in the repo. Thanks!</li>
</ul>
<h3 class="wp-block-heading" id="infrastructure">Creating Standalone Plugins</h3>
<p><a href="https://github.com/WordPress/performance/issues/656">Link to GitHub overview issue</a></p>
<p>Contributors: <a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> <a href="https://profiles.wordpress.org/mukesh27/" class="mention"><span class="mentions-prefix">@</span>mukesh27</a> <a href="https://profiles.wordpress.org/10upsimon/" class="mention"><span class="mentions-prefix">@</span>10upsimon</a></p>
<ul>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> Still awaiting approval of the Dominant Color Images plugin in the plugin repo</li>
</ul>
<h1 class="wp-block-heading">Open Floor</h1>
<ul>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a> This ticket has been very active – <a rel="noreferrer noopener" href="https://core.trac.wordpress.org/ticket/58368" target="_blank">https://core.trac.wordpress.org/ticket/58368</a>
<ul>
<li>TLDR, WP_Commey_Query does count queries using order by, resulting in bad performance. Comment type is not a database index.</li>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> That ticket needs an owner and and agreed upon patch in the next week. Seems like a stretch at the moment.</li>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a> I am not sure we can add indexes easily to a table like comments. The person on the ticket has 5 million comments in this database. Adding an index normally locks a table on a high traffic like that, it could be a problem. I think we will have to punt to 6.4. I will update the ticket.
<ul>
<li><a href="https://profiles.wordpress.org/rmccue/" class="mention"><span class="mentions-prefix">@</span>rmccue</a> I think we’ve added indexes on large tables before, seem to recall .com needing to orchestrate a slow rollout of them</li>
</ul>
</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> Do we know who is ensuring the fix for <a rel="noreferrer noopener" href="https://core.trac.wordpress.org/ticket/58457" target="_blank">https://core.trac.wordpress.org/ticket/58457</a> is getting synced from the Gutenberg repo? This process still seems very manual and error prone to me.
<ul>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a> Do you mean – <a rel="noreferrer noopener" href="https://github.com/WordPress/gutenberg/pull/50266" target="_blank">https://github.com/WordPress/gutenberg/pull/50266</a>?</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> </li>
<li>There’s a PR already, give me a sec. Needs review: <a rel="noreferrer noopener" href="https://github.com/WordPress/wordpress-develop/pull/4380" target="_blank">https://github.com/WordPress/wordpress-develop/pull/4380</a></li>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> That ticket seems to include references to two Gutenberg PRs, and a newly updated patch on that ticket. It would be good to have someone making sure that all of this gets resolved correctly.</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> I hadn’t seen that ticket. Seems like the reporter found the same issue but fixed it in a different way. The patches on that ticket are effectively obsolete if my above PR is committed. I’ll leave a comment</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a> Would useful to get eyes on – <a rel="noreferrer noopener" href="https://github.com/WordPress/gutenberg/pull/51116" target="_blank">https://github.com/WordPress/gutenberg/pull/51116</a></li>
</ul>
<p><strong>Our next chat will be held on <a href="https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230627T1500"><abbr class="date" title="2023-06-27T15:00:00+00:00">Tuesday, June 27, 2023 at 15:00 UTC</abbr></a> in the <a href="https://wordpress.slack.com/messages/core-performance/">#core-performance channel</a> in <a href="https://make.wordpress.org/chat/">Slack</a>.</strong></p>
<p class="o2-appended-tags"><a href="https://make.wordpress.org/core/tag/core-performance/" class="tag"><span class="tag-prefix">#</span>core-performance</a>, <a href="https://make.wordpress.org/core/tag/performance/" class="tag"><span class="tag-prefix">#</span>performance</a>, <a href="https://make.wordpress.org/core/tag/performance-chat/" class="tag"><span class="tag-prefix">#</span>performance-chat</a>, <a href="https://make.wordpress.org/core/tag/summary/" class="tag"><span class="tag-prefix">#</span>summary</a></p>
</div>

WordPress 6.9 Beta 2 is now ready for testing! This beta version of the WordPress…
The WordPress Community Team is calling for contributors to help overhaul the tools that power…
As October winds down, so too does Blocktober, Tammie Lister’s month-long challenge to create a…
The WordPress Foundation and WooCommerce have joined Automattic and Matt Mullenweg in countersuing WP Engine,…
The first-ever CloudFest USA Hackathon, taking place November 4 in Miami, will bring together contributors…
Canada’s largest gathering of WordPress enthusiasts drew a strong turnout at Carleton University last weekend,…