<div style="text-align:center"><img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///ywAAAAAAQABAAACAUwAOw==" fifu-lazy="1" fifu-data-sizes="auto" fifu-data-srcset="https://i3.wp.com/www.awordpresscommenter.com/wp-content/uploads/2023/10/performance-chat-summary-10-october-2023.png?ssl=1&w=75&resize=75&ssl=1 75w, https://i3.wp.com/www.awordpresscommenter.com/wp-content/uploads/2023/10/performance-chat-summary-10-october-2023.png?ssl=1&w=100&resize=100&ssl=1 100w, https://i3.wp.com/www.awordpresscommenter.com/wp-content/uploads/2023/10/performance-chat-summary-10-october-2023.png?ssl=1&w=150&resize=150&ssl=1 150w, https://i3.wp.com/www.awordpresscommenter.com/wp-content/uploads/2023/10/performance-chat-summary-10-october-2023.png?ssl=1&w=240&resize=240&ssl=1 240w, https://i3.wp.com/www.awordpresscommenter.com/wp-content/uploads/2023/10/performance-chat-summary-10-october-2023.png?ssl=1&w=320&resize=320&ssl=1 320w, https://i3.wp.com/www.awordpresscommenter.com/wp-content/uploads/2023/10/performance-chat-summary-10-october-2023.png?ssl=1&w=500&resize=500&ssl=1 500w, https://i3.wp.com/www.awordpresscommenter.com/wp-content/uploads/2023/10/performance-chat-summary-10-october-2023.png?ssl=1&w=640&resize=640&ssl=1 640w, https://i3.wp.com/www.awordpresscommenter.com/wp-content/uploads/2023/10/performance-chat-summary-10-october-2023.png?ssl=1&w=800&resize=800&ssl=1 800w, https://i3.wp.com/www.awordpresscommenter.com/wp-content/uploads/2023/10/performance-chat-summary-10-october-2023.png?ssl=1&w=1024&resize=1024&ssl=1 1024w, https://i3.wp.com/www.awordpresscommenter.com/wp-content/uploads/2023/10/performance-chat-summary-10-october-2023.png?ssl=1&w=1280&resize=1280&ssl=1 1280w, https://i3.wp.com/www.awordpresscommenter.com/wp-content/uploads/2023/10/performance-chat-summary-10-october-2023.png?ssl=1&w=1600&resize=1600&ssl=1 1600w" width="3230" height="1219" fifu-data-src="https://i3.wp.com/www.awordpresscommenter.com/wp-content/uploads/2023/10/performance-chat-summary-10-october-2023.png?ssl=1" class="attachment-post-thumbnail size-post-thumbnail wp-post-image" alt="Performance Chat Summary: 10 October 2023" title="Performance Chat Summary: 10 October 2023" srcset="https://i3.wp.com/www.awordpresscommenter.com/wp-content/uploads/2023/10/performance-chat-summary-10-october-2023.png?ssl=1 3230w, https://www.awordpresscommenter.com/wp-content/uploads/2023/10/performance-chat-summary-10-october-2023-300x113.png 300w, https://www.awordpresscommenter.com/wp-content/uploads/2023/10/performance-chat-summary-10-october-2023-1024x386.png 1024w, https://www.awordpresscommenter.com/wp-content/uploads/2023/10/performance-chat-summary-10-october-2023-768x290.png 768w, https://www.awordpresscommenter.com/wp-content/uploads/2023/10/performance-chat-summary-10-october-2023-1536x580.png 1536w, https://www.awordpresscommenter.com/wp-content/uploads/2023/10/performance-chat-summary-10-october-2023-2048x773.png 2048w" sizes="(max-width: 3230px) 100vw, 3230px" /></div><div>
<p><a href="https://make.wordpress.org/core/2023/10/10/performance-chat-agenda-10-october-2023/">Meeting agenda here</a> and the full chat log is available <a href="https://wordpress.slack.com/archives/C02KGN5K076/p1696950002920219">beginning here on Slack</a>.</p>
<h2 class="wp-block-heading">Announcements</h2>
<ul>
<li>Welcome to our new members of <a href="http://wordpress.slack.com/messages/core-performance/">#core-performance</a></li>
<li>WordPress 6.4 beta 3 is <strong>today</strong></li>
<li>Reminder about the <a href="https://make.wordpress.org/core/2023/09/18/hallway-hangout-performance-improvements-for-wordpress-6-4/">Performance Hallway Hangout</a> next week <a href="https://www.timeanddate.com/worldclock/fixedtime.html?iso=20231019T1500"><abbr title="2023-10-19T15:00:00+00:00">Thursday, October 19, 2023 at 04:00 PM GMT+1</abbr></a></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/swissspidy/" class="mention"><span class="mentions-prefix">@</span>swissspidy</a> <a href="https://profiles.wordpress.org/thekt12/" class="mention"><span class="mentions-prefix">@</span>thekt12</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> Everything planned for 6.4 has been resolved. I’m keep an eye out for issues that come up during the last week of beta and RC. Otherwise, am beginning to start focusing on opportunities for 6.5, like <a href="https://github.com/WordPress/performance/issues/746" data-type="link" data-id="https://github.com/WordPress/performance/issues/746">Improving Template Loading</a> and Improvements to the way block widgets are registered (ex: <a href="https://core.trac.wordpress.org/ticket/55595">#55595</a>)</li>
<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/3ad20183b0f54b79ae7a2bbf449ea523d50fd687" target="_blank">https://github.com/WordPress/wordpress-develop/commit/3ad20183b0f54b79ae7a2bbf449ea523d50fd687</a></li>
<li><a rel="noreferrer noopener" aria-describedby="qtip-86" href="https://github.com/WordPress/wordpress-develop/commit/d8206d2167f2c082258f31db163289bae3682e06" target="_blank">https://github.com/WordPress/wordpress-develop/commit/d8206d2167f2c082258f31db163289bae3682e06</a></li>
</ul>
</li>
<li>Code reviewed
<ul>
<li><a rel="noreferrer noopener" href="https://github.com/WordPress/wordpress-develop/commit/41cf9f0a38ae2bb2136102f2394ff883bbd4085f" target="_blank">https://github.com/WordPress/wordpress-develop/commit/41cf9f0a38ae2bb2136102f2394ff883bbd4085f</a></li>
<li><a rel="noreferrer noopener" aria-describedby="qtip-97" href="https://github.com/WordPress/wordpress-develop/commit/9d039e6c911d2479453cb26f6895249f0d40fa23" target="_blank">https://github.com/WordPress/wordpress-develop/commit/9d039e6c911d2479453cb26f6895249f0d40fa23</a></li>
</ul>
</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/mukesh27/" class="mention"><span class="mentions-prefix">@</span>mukesh27</a> <a href="https://core.trac.wordpress.org/ticket/59360">#59360</a> to be committed today. It was reopened for some concern that I’m looking into right now</li>
<li><a href="https://profiles.wordpress.org/swissspidy/" class="mention"><span class="mentions-prefix">@</span>swissspidy</a> <a rel="noreferrer noopener" href="https://wordpress.org/plugins/performant-translations/" target="_blank">Performant Translations</a> is doing well. There are already PRs and tickets for all the relevant areas this touches. I’m working on further simplifying the plugin &#038; core patch. Once 6.4 is released we can continue with the next steps for a 6.5 merge.</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> I would like to flag <strong><a href="https://wordpress.slack.com/archives/C02RQBWTW/p1696950609355169?thread_ts=1696880738.627909&#038;cid=C02RQBWTW" data-type="link" data-id="https://wordpress.slack.com/archives/C02RQBWTW/p1696950609355169?thread_ts=1696880738.627909&#038;cid=C02RQBWTW">this Slack thread</a></strong> – just spotted this literally 5 minutes ago, but it looks like the most significant performance fix for TT4 caused a bug, which now with the fix for that bug effectively may have reverted almost all the performance benefit
<ul>
<li>In my benchmark yesterday, TT4 was about ~10% slower than TT3. Now it’s again ~25% slower</li>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a> to re-open <a href="https://core.trac.wordpress.org/ticket/59541">#59541</a> to see if it helps</li>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> to run some profiles, but assuming it’s due to <code>parse_blocks()</code> being called way more often.</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/thekt12/" class="mention"><span class="mentions-prefix">@</span>thekt12</a> I have picked up <a rel="noreferrer noopener" href="https://github.com/WordPress/performance/issues/746" target="_blank">https://github.com/WordPress/performance/issues/746</a> (just a while ago), checking through tickets that are still left</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/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a> <a href="https://profiles.wordpress.org/mukesh27/" class="mention"><span class="mentions-prefix">@</span>mukesh27</a> <a href="https://profiles.wordpress.org/thekt12/" class="mention"><span class="mentions-prefix">@</span>thekt12</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/94d2f4e68be97a24f4b588551e30bcf5339c5b15" target="_blank">https://github.com/WordPress/wordpress-develop/commit/94d2f4e68be97a24f4b588551e30bcf5339c5b15</a></li>
<li><a rel="noreferrer noopener" href="https://github.com/WordPress/wordpress-develop/commit/6ee34689ca8a3336cd7fe4bbde552380564cfee6" target="_blank">https://github.com/WordPress/wordpress-develop/commit/6ee34689ca8a3336cd7fe4bbde552380564cfee6</a></li>
<li><a rel="noreferrer noopener" href="https://github.com/WordPress/wordpress-develop/commit/33b32ebc4ee8cdc577792c40ee47736394442dc4" target="_blank">https://github.com/WordPress/wordpress-develop/commit/33b32ebc4ee8cdc577792c40ee47736394442dc4</a></li>
</ul>
</li>
<li>Still working on <a href="https://core.trac.wordpress.org/ticket/59188">#59188</a>
<ul>
<li>Would love feedback on <a rel="noreferrer noopener" href="https://github.com/WordPress/wordpress-develop/pull/5443" target="_blank">https://github.com/WordPress/wordpress-develop/pull/5443</a></li>
<li>Worth reading this comment – <a rel="noreferrer noopener" href="https://core.trac.wordpress.org/ticket/59188#comment:62" target="_blank">https://core.trac.wordpress.org/ticket/59188#comment:62</a></li>
</ul>
</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> to follow up on both the above items</li>
<li><a href="https://profiles.wordpress.org/pbearne/" class="mention"><span class="mentions-prefix">@</span>pbearne</a> I would like help looking at the all options ideas to see if it worth going forward and how best to approach implementing this here <a rel="noreferrer noopener" href="https://gist.github.com/pbearne/ce21417bf5ecfa10b84afc758092cd9f" target="_blank">https://gist.github.com/pbearne/ce21417bf5ecfa10b84afc758092cd9f</a>
<ul>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a> this ticket could also do with some review <a href="https://core.trac.wordpress.org/ticket/42441">#42441</a></li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> we have a running GH ticket about autoloaded options that would be useful to get your comments on, if there are additional ideas you want to consider: <a rel="noreferrer noopener" href="https://github.com/WordPress/performance/issues/766" target="_blank">https://github.com/WordPress/performance/issues/766</a></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/westonruter/" class="mention"><span class="mentions-prefix">@</span>westonruter</a> <a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a></p>
<ul>
<li><a href="https://profiles.wordpress.org/westonruter/" class="mention"><span class="mentions-prefix">@</span>westonruter</a> Yesterday I <a rel="noreferrer noopener" href="https://core.trac.wordpress.org/changeset/56809" target="_blank">committed</a> the removal of <code>unload</code> event listeners and use of <code>pagehide</code> and <code>pageshow</code> where appropriate for <a href="https://core.trac.wordpress.org/ticket/55491">#55491</a> . In the best case this will improve performance by allowing bfcache to speed up page navigations. But as I mentioned before, bfcache is also disabled when <code>Cache-Control: no-store</code> is present, and this was added to all authenticated page requests in 6.3 with <a href="https://core.trac.wordpress.org/ticket/21938">#21938</a>. Lastly, the heartbeat script is only used on 0.25% of HTTP Archive pages (which would be unauthenticated). So in practice the performance benefits will be marginal. Nevertheless, the <code>unload</code> event is unreliable so the change is an improvement regardless.</li>
<li><a href="https://profiles.wordpress.org/adamsilverstein/" class="mention"><span class="mentions-prefix">@</span>adamsilverstein</a> I have been working on adoption of the script strategy feature with plugins and have been having some success. Its great how easy it is to layer on the new API without breaking old use cases (especially using `wp_script_add_data`). One potential issue I have discovered that could cause regressions has to do with dependencies and the footer attribute.
<ul>
<li>Here is the scenerio:
<ul>
<li>Popular plugin “Plugin A” currently enqueues a script on the front end, using `in_footer` => true, so the script is essentially non blocking</li>
<li>To get a slight performance gain, in WP >= 6.3 the plugin changes `in_footer` to `array( ‘strategy => ‘defer’ )`. Great, now the script is in the header so it can be discovered slightly earlier, and it is marked as `defer` so it is non-blocking.</li>
</ul>
</li>
<li>Now… along comes “Plugin B”, they enqueue a script that depends on the script from “Plugin A”, and they still use `in_footer => true`. Now the script from “Plugin A” can no longer be deferred, so it is not – however it remains in the header. The result: we now have a new blocking script in the header.</li>
<li>I wonder if we had considered this during the design? Maybe in my scenario I should instead use `array( ‘strategy => ‘defer’, ‘in_fooer’ => true )`</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> I think opening a ticket would be good. If a script has <code>defer</code>, it should always be fine to load it in the footer (since with <code>defer</code> it only loads after the DOM anyway). So I think that would be a good fix: If a script is in the head and its <code>defer</code> is forced back to blocking, move it to the footer</li>
<li><a href="https://profiles.wordpress.org/adamsilverstein/" class="mention"><span class="mentions-prefix">@</span>adamsilverstein</a> I was thinking that also, but it might have other implications…Also in my testing I noticed that in_footer already has some dependency behavior built in that can move scripts to the header:<br />Script A is marked for the footer. If script b depends on script a and is marked for the header, script a also gets put in the header</li>
<li><a href="https://profiles.wordpress.org/10upsimon/" class="mention"><span class="mentions-prefix">@</span>10upsimon</a> That makes sense <a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> I think we only never did that because by design you’d only usually have deferred in the header, generally, correct?
<ul>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> Not sure, I don’t remember us ever thinking about the head vs footer implication of a deferred script being forced back to blocking. So we may just have missed that consideration. To me what <a href="https://profiles.wordpress.org/adamsilverstein/" class="mention"><span class="mentions-prefix">@</span>adamsilverstein</a> pointed out above is something we should be able to fix in a rather straightforward way</li>
<li><a href="https://profiles.wordpress.org/adamsilverstein/" class="mention"><span class="mentions-prefix">@</span>adamsilverstein</a> yea, I don’t think we considered that exact scenereo, I came across it trying to implement/use the feature</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> I think the latter has been the case forever, so that wouldn’t be a regression</li>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> We could do some analysis of how many registered deferred scripts end up in the head, since we added some data attributes to track that sort of thing</li>
<li><a href="https://profiles.wordpress.org/westonruter/" class="mention"><span class="mentions-prefix">@</span>westonruter</a> We don’t currently capture whether a script was originally registered with <code>$in_footer</code> in the data attributes like we do with the script strategies though</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> FWIW I cannot see any concerns with moving a <code>head defer</code> script to <code>footer</code> from a functional perspective. In both cases it would be loaded after the DOM. Not sure how important the impact research would be for that bug specifically</li>
<li><strong><a href="https://profiles.wordpress.org/adamsilverstein/" class="mention"><span class="mentions-prefix">@</span>adamsilverstein</a> to open a ticket to discuss further</strong></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> <a href="https://profiles.wordpress.org/pereirinha/" class="mention"><span class="mentions-prefix">@</span>pereirinha</a></p>
<ul>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> I’m planning to follow up on two things we’ve discussed, related to improving how WordPress calculates the <code>sizes</code> attribute.
<ul>
<li>1. Improving how WP calculates its default `sizes` attributes: <a rel="noreferrer noopener" href="https://github.com/WordPress/performance/issues/760" target="_blank">https://github.com/WordPress/performance/issues/760</a></li>
<li>2. Support native lazy sizes once it’s available (currently still in development by browsers) <a rel="noreferrer noopener" href="https://github.com/WordPress/performance/issues/791" target="_blank">https://github.com/WordPress/performance/issues/791</a></li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/adamsilverstein/" class="mention"><span class="mentions-prefix">@</span>adamsilverstein</a> I’ve been testing the fetchpriority attribute and wanted to raise some potential issues. First: I created a simple plugin that adds an advanced image control that lets users set the fetchpriority manually for individual images – <a rel="noreferrer noopener" data-hasqtip="496" aria-describedby="qtip-496" href="https://github.com/adamsilverstein/wp-fetchpriority-control" target="_blank">https://github.com/adamsilverstein/wp-fetchpriority-control</a>
<ul>
<li>Noticed a few edge cases with our approach in testing –
<ul>
<li>putting images in columns in GB resizes them but only with styles (?) so we still apply fetchpriority – <a rel="noreferrer noopener" data-hasqtip="382" href="https://wp-sample-pages.instawp.xyz/another-test/" target="_blank">https://wp-sample-pages.instawp.xyz/another-test/</a> — note that the thumbnail in the first row gets the fetchpriority=high which is probably incorrect</li>
<li>repeating the same image three times means all three will get the fetchpriority attribute – because our processing tries to skip re-processing duplicate images – <a rel="noreferrer noopener" href="https://wp-sample-pages.instawp.xyz/test-post/" target="_blank">https://wp-sample-pages.instawp.xyz/test-post/</a></li>
<li>manually setting the fetchpriority for an image causes core to skip it (not change it), but it then applies the attribute to the next image, In this test, I applied fetchpriority=”low” to the first image, and fetchpriority=”high” to the large image below the thumbnails. Core aded the fetchpriority=”high” to the second thumbnail image – <a rel="noreferrer noopener" href="https://wp-sample-pages.instawp.xyz/with-manually-set-high-and-low/" target="_blank">https://wp-sample-pages.instawp.xyz/with-manually-set-high-and-low/</a>. If core finds existing fetchpriority=high tagging it should probably avoid adding its own.
<ul>
<li><a href="https://profiles.wordpress.org/westonruter/" class="mention"><span class="mentions-prefix">@</span>westonruter</a> found the same issue with columns: <a rel="noreferrer noopener" href="https://gist.github.com/westonruter/fc251e8f0917ae4135b3334273360be8" target="_blank">https://gist.github.com/westonruter/fc251e8f0917ae4135b3334273360be8</a></li>
<li>Also can be an issue with Image &#038; Text block: <a rel="noreferrer noopener" href="https://gist.github.com/westonruter/72d00dfd9d59f2c1870524f8dcd3cb79" target="_blank">https://gist.github.com/westonruter/72d00dfd9d59f2c1870524f8dcd3cb79</a></li>
<li><a href="https://profiles.wordpress.org/adamsilverstein/" class="mention"><span class="mentions-prefix">@</span>adamsilverstein</a> very interesting! I always wondered about these cases (and how we should address them)</li>
<li><a href="https://profiles.wordpress.org/westonruter/" class="mention"><span class="mentions-prefix">@</span>westonruter</a> I don’t really see how such scenarios can be easily fixed with PHP heuristics. But this should be easily accounted for with client-side detection.</li>
</ul>
</li>
</ul>
</li>
<li>I think these are all addressable in some form and the first may already be covered by an existing ticket; I’ll plan to open tickets for further discussion</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> I opened a new ticket yesterday for a recently found limitation of <code>wp_get_loading_optimization_attributes()</code> when it comes to images in block templates <a href="https://core.trac.wordpress.org/ticket/59577">#59577</a> that affects TT4</li>
<li><a href="https://profiles.wordpress.org/pereirinha/" class="mention"><span class="mentions-prefix">@</span>pereirinha</a> I’m looking for good candidates to pick up, but nothing yet. Happy to assist here.</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/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> <a href="https://profiles.wordpress.org/swissspidy/" class="mention"><span class="mentions-prefix">@</span>swissspidy</a> <a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a></p>
<ul>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> Nothing from my end, other than running benchmarks on several tickets this week</li>
<li><a href="https://profiles.wordpress.org/mukesh27/" class="mention"><span class="mentions-prefix">@</span>mukesh27</a> Planning to run benchmarks for beta 3 tomorrow.</li>
<li><a href="https://profiles.wordpress.org/swissspidy/" class="mention"><span class="mentions-prefix">@</span>swissspidy</a> Continuing working on documenting ways for improving the core performance test setup &#038; reducing test variance. Nothing concrete right now</li>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> Another thing we’ve been discussing for the past few weeks is how to improve the confidence we have in our benchmarking setups. Many of us have been using <a rel="noreferrer noopener" href="https://github.com/swissspidy/compare-wp-performance" target="_blank">an automated script</a> that <a href="https://profiles.wordpress.org/swissspidy/" class="mention"><span class="mentions-prefix">@</span>swissspidy</a> put together to run benchmarks for each release, and we’re getting consistent numbers, but those numbers are showing much bigger performance gains than what <a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> has been reporting with his local setup. I’m planning to dig into this a bit more today. <a href="https://profiles.wordpress.org/swissspidy/" class="mention"><span class="mentions-prefix">@</span>swissspidy</a> I saw that you’re making good progress on converting performance tests to Playwrite. Anything we can help with there?
<ul>
<li><a href="https://profiles.wordpress.org/swissspidy/" class="mention"><span class="mentions-prefix">@</span>swissspidy</a> basically complete. Just needs code review under <a href="https://core.trac.wordpress.org/ticket/59517">#59517</a></li>
</ul>
</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/mukesh27/" class="mention"><span class="mentions-prefix">@</span>mukesh27</a> <a href="https://profiles.wordpress.org/swissspidy/" class="mention"><span class="mentions-prefix">@</span>swissspidy</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/mukesh27/" class="mention"><span class="mentions-prefix">@</span>mukesh27</a> For the Plugin Checker: <em>PR <a rel="noreferrer noopener" href="https://github.com/WordPress/plugin-check/pull/285" target="_blank">Add </a></em><code><em>Trademarks_Check</em></code><em><a rel="noreferrer noopener" href="https://github.com/WordPress/plugin-check/pull/285" target="_blank"> 285</a></em> – Ready for review</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/10upsimon/" class="mention"><span class="mentions-prefix">@</span>10upsimon</a> No major updates from me at the moment, I did decide to refactor some code to be more WordPress’y when it comes to the standalone plug-in card rendering within WPP settings screen, so I’ll open said PR for standalone plug-ins UI soon, via a feature branch.</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> I am changing roles ( I am leaving XWP ). I will not have sponsored time to work on this project. So as of the end of this week, I will be stepping down from this project. That means I will not be around to answer questions or code review. If you need anything, please message me before the end of the week.</li>
</ul>
<p><strong>Our next chat will be held on <a href="https://www.timeanddate.com/worldclock/fixedtime.html?iso=20231017T1500"><abbr class="date" title="2023-10-17T15:00:00+00:00">Tuesday, October 17, 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>

The WordPress Plugins Team is now automatically scanning every plugin update on WordPress.org for security,…
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…