<div style="text-align:center"></div><div>
<p><a href="https://make.wordpress.org/core/2024/03/25/performance-chat-agenda-26-march-2024/">Meeting agenda here</a> and the full chat log is available <a href="https://wordpress.slack.com/archives/C02KGN5K076/p1711468807935069">beginning here on Slack</a>.</p>
<h1 class="wp-block-heading">Announcements</h1>
<ul>
<li>Welcome to our new members of <a href="http://wordpress.slack.com/messages/core-performance/">#core-performance</a></li>
<li>WordPress 6.5 delayed (see <a href="https://make.wordpress.org/core/2024/03/25/wordpress-6-5-release-delayed-1-week/">blog post</a>):
<ul>
<li>RC 4 will be March 28</li>
<li>Release April 2</li>
</ul>
</li>
<li>Performance Team have launched two new plugins
<ul>
<li><a href="https://wordpress.org/plugins/optimization-detective/">Optimization Detective</a> plugin</li>
<li><a href="https://wordpress.org/plugins/embed-optimizer/" target="_blank" rel="noreferrer noopener">Embed Optimizer</a> plugin</li>
</ul>
</li>
<li>Reminder on timezone difference for this week, this chat will remain at 16:00 UTC and then shift to 15:00 UTC from April 2, 2024</li>
</ul>
<h1 class="wp-block-heading" id="focus-group-updates">Priority Items</h1>
<p>Structure:</p>
<ul>
<li>WordPress performance Trac tickets
<ul>
<li>Current release</li>
<li>Future release</li>
</ul>
</li>
<li>Performance Lab plugin (and other performance plugins)</li>
<li>Active priority projects
<ul>
<li>INP research opportunities</li>
<li>Improve template loading</li>
</ul>
</li>
</ul>
<h2 class="wp-block-heading" id="images">WordPress Performance Trac Tickets</h2>
<ul>
<li>For WordPress 6.5:
<ul>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> Nothing concrete, though since part of the reason for the release delay is changes to the Font API, we should probably keep an eye on that it doesn’t regress performance. As far as I understand the scope of the changes, it shouldn’t… but still worth staying on top of</li>
</ul>
</li>
<li>For Future Releases:
<ul>
<li>We already have <a href="https://core.trac.wordpress.org/query?status=accepted&#038;status=assigned&#038;status=closed&#038;status=new&#038;status=reopened&#038;status=reviewing&#038;focuses=~performance&#038;milestone=6.6&#038;groupdesc=1&#038;group=resolution&#038;col=id&#038;col=summary&#038;col=status&#038;col=milestone&#038;col=owner&#038;col=type&#038;col=priority&#038;col=keywords&#038;order=priority" target="_blank" rel="noreferrer noopener">14 open items in the 6.6 milestone</a></li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> update on <a href="https://core.trac.wordpress.org/ticket/42441">#42441</a> (enhancing autoload API and disable autoload for large options) – The <a href="https://github.com/WordPress/wordpress-develop/pull/5671" target="_blank" rel="noreferrer noopener">PR</a> has two approvals and looks excellent to me, so I’ve marked the ticket for commit
<ul>
<li>Going to wait for a few more days to see if any additional feedback comes in, but generally plan to commit this next week so that we can get a lot of testing during the 6.6 release cycle</li>
</ul>
</li>
</ul>
</li>
</ul>
<h2 class="wp-block-heading" id="images">Performance Lab Plugin (and other Performance Plugins)</h2>
<ul>
<li><a href="https://profiles.wordpress.org/mukesh27/" class="mention"><span class="mentions-prefix">@</span>mukesh27</a> for standalone plugins:
<ul>
<li><strong>PRs that have been merged:</strong>
<ul>
<li>PR <a href="https://github.com/WordPress/performance/pull/1048" target="_blank" rel="noreferrer noopener">#1048</a> – Support changing autoload value for largest autoloaded options</li>
<li>PR <a href="https://github.com/WordPress/performance/pull/1060" target="_blank" rel="noreferrer noopener">#1060</a> – Remove modules infrastructure</li>
<li>PR <a href="https://github.com/WordPress/performance/pull/1062" target="_blank" rel="noreferrer noopener">#1062</a> – Bump minimum required WP version to 6.4</li>
</ul>
</li>
<li><strong>PRs that ready for review:</strong>
<ul>
<li>PR <a href="https://github.com/WordPress/performance/pull/1091" target="_blank" rel="noreferrer noopener">#1091</a> – Improve UX/UI of enabling performance features via standalone plugins</li>
</ul>
</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/adamsilverstein/" class="mention"><span class="mentions-prefix">@</span>adamsilverstein</a> The <a href="https://wordpress.org/plugins/embed-optimizer/" target="_blank" rel="noreferrer noopener">Embed Optimizer</a> feature/plugin is also newly available</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> I have been working on two documentation drafts that replace the obsolete module focused documentation articles in the Handbook with their plugin focused equivalents:
<ul>
<li><a href="https://docs.google.com/document/d/1lIR4pvid2fYXI-gF4injOHRN8HKBENBnSxJ5tEYGOMY/edit">This document</a> has the draft to replace <a href="https://make.wordpress.org/performance/handbook/performance-lab/proposing-a-new-module/" target="_blank" rel="noreferrer noopener">https://make.wordpress.org/performance/handbook/performance-lab/proposing-a-new-module/</a></li>
<li><a href="https://docs.google.com/document/d/1QR22o70_CjkYAS_i6ucbZyJ2h8pAEe6mg6pvXZYZUiY/edit">This document</a> has the draft to replace <a href="https://make.wordpress.org/performance/handbook/performance-lab/writing-a-module/" target="_blank" rel="noreferrer noopener">https://make.wordpress.org/performance/handbook/performance-lab/writing-a-module/</a></li>
<li>Most of the content is just the existing content adapted, to get an “MVP” documentation update sooner than later</li>
<li>Review and feedback of those two drafts would be super helpful so that we can update that documentation</li>
<li>I already opened <a href="https://github.com/WordPress/performance/pull/1092" target="_blank" rel="noreferrer noopener">https://github.com/WordPress/performance/pull/1092</a> which replaces the obsolete “module proposal issue template”</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/thelovekesh/" class="mention"><span class="mentions-prefix">@</span>thelovekesh</a> Looking for brainstorming and feedback on:
<ul>
<li><a href="https://github.com/WordPress/performance/issues/1061" target="_blank" rel="noreferrer noopener">https://github.com/WordPress/performance/issues/1061</a></li>
<li><a href="https://github.com/WordPress/performance/issues/1085" target="_blank" rel="noreferrer noopener">https://github.com/WordPress/performance/issues/1085</a></li>
<li>And CodeQL PR needs one more approval. If someone can please take a look – <a href="https://github.com/WordPress/performance/pull/981" target="_blank" rel="noreferrer noopener">https://github.com/WordPress/performance/pull/981</a></li>
</ul>
</li>
</ul>
<h2 class="wp-block-heading" id="object-caching">Active Priority Projects</h2>
<ul></ul>
<h3 class="wp-block-heading" id="measurement">Improve template loading</h3>
<ul>
<li><a href="https://profiles.wordpress.org/thekt12/" class="mention"><span class="mentions-prefix">@</span>thekt12</a> working on PR split here – <a href="https://github.com/WordPress/wordpress-develop/pull/6137" target="_blank" rel="noreferrer noopener">https://github.com/WordPress/wordpress-develop/pull/6137</a>, should add the new PR today for block_template_file and template_part, and keep pattern work in original PR</li>
</ul>
<h3 class="wp-block-heading" id="javascript">INP research opportunities</h3>
<ul>
<li><a href="https://profiles.wordpress.org/adamsilverstein/" class="mention"><span class="mentions-prefix">@</span>adamsilverstein</a> As promised, I have collected the results of my INP research and am sharing now in this <a href="https://docs.google.com/document/d/1R8lPWuW4Qr3oI2qpeACSNGKGyggQyY7AF-Y5KNcAgN4/edit?usp=sharing" target="_blank" rel="noreferrer noopener">summary doc</a> (along with a linked spreadsheet with all the data). If you want access to the colab and queries, please request it directly in the colab.
<ul>
<li>The summary doc Analysis section highlights some notable data for both core and plugins/themes (with action items) that will be worth investigating further. Since there is a ton to absorb there, I think its best to leave comments/questions on the doc itself so we can discuss async, and maybe we can discuss further at a subsequent meeting.</li>
</ul>
</li>
</ul>
<h1 class="wp-block-heading">Open Floor</h1>
<ul>
<li><a href="https://profiles.wordpress.org/pbearne/" class="mention"><span class="mentions-prefix">@</span>pbearne</a> one ticket from the old tickets <a href="https://core.trac.wordpress.org/ticket/29717" target="_blank" rel="noreferrer noopener">https://core.trac.wordpress.org/ticket/29717</a> might worth looking at</li>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> We’ve traditionally done a post following a major release which gives an overview of the performance characteristics of that release. I was planning to draft one for 6.5 once we can take a final set of benchmarks, but I’m assuming that we’re going to end with similar metrics to what we’ve been seeing in the last several RCs, since we’ve not had any new improvements or regressions. I’ll also include details about the editor improvements, but that doesn’t effect any of the CWV metrics we’ve been focusing on. I’d appreciate any thoughts folks have about how to communicate the performance of 6.5 clearly, while accurately reflecting that our benchmarks do NOT show an improvement over the previous release.</li>
<li><strong>REMINDER: </strong>This meeting will switch to 15:00 UTC from April 2 (next week) onwards</li>
</ul>
<p><strong>Our next chat will be held on <a href="https://www.timeanddate.com/worldclock/fixedtime.html?iso=20240402T1500"><abbr class="date" title="2024-04-02T15:00:00+00:00">Tuesday, April 2, 2024 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>

A new ecommerce contender has entered the WordPress space. This week, WPManageNinja officially launched FluentCart,…
The WP Minute is stepping into education. The publication best known for its interviews, podcasts,…
AI-powered site builders are having a moment in WordPress, and 10Web is the latest company…
For as long as Aaron Edwards and Joshua Dailey have known each other, they’ve been…
A U.S. magistrate judge has moved to rein in the escalating discovery battle between WP…
Ollie’s “game-changing” Menu Designer plugin is moving toward inclusion in WordPress core. Anne McCarthy says…