<div style="text-align:center"><img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///ywAAAAAAQABAAACAUwAOw==" fifu-lazy="1" fifu-data-sizes="auto" fifu-data-srcset="https://i0.wp.com/www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-30-april-2024.png?ssl=1&w=75&resize=75&ssl=1 75w, https://i0.wp.com/www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-30-april-2024.png?ssl=1&w=100&resize=100&ssl=1 100w, https://i0.wp.com/www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-30-april-2024.png?ssl=1&w=150&resize=150&ssl=1 150w, https://i0.wp.com/www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-30-april-2024.png?ssl=1&w=240&resize=240&ssl=1 240w, https://i0.wp.com/www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-30-april-2024.png?ssl=1&w=320&resize=320&ssl=1 320w, https://i0.wp.com/www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-30-april-2024.png?ssl=1&w=500&resize=500&ssl=1 500w, https://i0.wp.com/www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-30-april-2024.png?ssl=1&w=640&resize=640&ssl=1 640w, https://i0.wp.com/www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-30-april-2024.png?ssl=1&w=800&resize=800&ssl=1 800w, https://i0.wp.com/www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-30-april-2024.png?ssl=1&w=1024&resize=1024&ssl=1 1024w, https://i0.wp.com/www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-30-april-2024.png?ssl=1&w=1280&resize=1280&ssl=1 1280w, https://i0.wp.com/www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-30-april-2024.png?ssl=1&w=1600&resize=1600&ssl=1 1600w" width="1560" height="880" fifu-data-src="https://i0.wp.com/www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-30-april-2024.png?ssl=1" class="attachment-post-thumbnail size-post-thumbnail wp-post-image" alt="Performance Chat Summary: 30 April 2024" title="Performance Chat Summary: 30 April 2024" srcset="https://i0.wp.com/www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-30-april-2024.png?ssl=1 1560w, https://www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-30-april-2024-300x169.png 300w, https://www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-30-april-2024-1024x578.png 1024w, https://www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-30-april-2024-768x433.png 768w, https://www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-30-april-2024-1536x866.png 1536w" sizes="(max-width: 1560px) 100vw, 1560px" /></div><div>
<p><a href="https://make.wordpress.org/core/2024/04/29/performance-chat-agenda-30-april-2024/">Meeting agenda here</a> and the full chat log is available <a href="https://wordpress.slack.com/archives/C02KGN5K076/p1714489172263079">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>New post published summarising the <a href="https://make.wordpress.org/core/2024/04/23/wordpress-6-5-performance-improvements/">WordPress 6.5 performance improvements</a></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 (WP 6.6)</li>
</ul>
</li>
<li>Performance Lab plugin (and other performance plugins)</li>
<li>Active priority projects
<ul>
<li>Improve template loading</li>
<li>INP research opportunities</li>
<li>Improving the calculation of image size attributes</li>
<li>Optimized autoloaded options</li>
</ul>
</li>
</ul>
<h2 class="wp-block-heading" id="images">WordPress Performance Trac Tickets</h2>
<ul>
<li>For WordPress 6.6:
<ul>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> For our auto-loading improvents, <a href="https://core.trac.wordpress.org/ticket/42441">#42441</a>, I owe <a href="https://profiles.wordpress.org/pbearne/" class="mention"><span class="mentions-prefix">@</span>pbearne</a> feedback on a draft of the dev-note (planning to do so this week). I also left some feedback on the follow-up issue (<a href="https://core.trac.wordpress.org/ticket/61045">#61045</a>) that needs to be addressed, and then I think that is ready for commit.
<ul>
<li><a href="https://profiles.wordpress.org/pbearne/" class="mention"><span class="mentions-prefix">@</span>pbearne</a> I need feedback on this as I went through core and set the autoload for all update_options. If i felt they were admin only options i set them to off</li>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> I think that’s a useful idea, but we should probably handle that in a separate issue/PR</li>
<li><a href="https://profiles.wordpress.org/pbearne/" class="mention"><span class="mentions-prefix">@</span>pbearne</a> in an attempt to reduce options load on the front-end</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a> I want to try and get <a href="https://github.com/WordPress/wordpress-develop/pull/6393" target="_blank" rel="noreferrer noopener">https://github.com/WordPress/wordpress-develop/pull/6393</a> committed in the next couple of days. Just waiting on final feedback from <a href="https://profiles.wordpress.org/peterwilsoncc/" class="mention"><span class="mentions-prefix">@</span>peterwilsoncc</a></li>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a> also working on <a href="https://github.com/WordPress/wordpress-develop/pull/6311" target="_blank" rel="noreferrer noopener">https://github.com/WordPress/wordpress-develop/pull/6311</a>. It needs tests.
<ul>
<li>The <code>wp_prime_network_options</code> function is an example of where it might not have a direct benefit out of the box. It is a developer api and would enable plugins to “do the right thing” I prime multiple network options caches at once.</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/thekt12/" class="mention"><span class="mentions-prefix">@</span>thekt12</a> I have started a new <a href="https://github.com/WordPress/wordpress-develop/pull/6463" target="_blank" rel="noreferrer noopener">PR 6463</a> for caching #57789 (not ready for review). I was trying to see if we could cache before filter to avoid unit test failures but seems that doing so only give 0.01% improvement.
<ul>
<li>At the moment I am trying to cache inside <code>WP_Theme_JSON_Data::__construct</code> and <code>WP_Theme_JSON::__construct</code> as they are the one with major regression</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/westonruter/" class="mention"><span class="mentions-prefix">@</span>westonruter</a> A <a href="https://github.com/WordPress/performance/pull/1184" target="_blank" rel="noreferrer noopener">PR</a> is ready for review which allows performance features to have plugin dependencies. This is needed for <a href="https://github.com/WordPress/performance/issues/1088" target="_blank" rel="noreferrer noopener">Image Prioritizer</a> which depends on Optimization Detective. With this PR merged, the work on Image Prioritizer can press forward full steam.</li>
<li><a href="https://profiles.wordpress.org/mukesh27/" class="mention"><span class="mentions-prefix">@</span>mukesh27</a> I worked on <a href="https://github.com/WordPress/performance/issues/1139" target="_blank" rel="noreferrer noopener">Progress indicator is missing when activating a feature</a> and it has been merged! Requires a follow up though from this <a href="https://github.com/WordPress/performance/pull/1190#discussion_r1585022305">comment</a></li>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> For the <a href="https://github.com/WordPress/performance/milestone/37" target="_blank" rel="noreferrer noopener">3.1.0 milestone</a>, we have one issue that needs an owner to move forward: <a href="https://github.com/WordPress/performance/issues/1032" target="_blank" rel="noreferrer noopener">https://github.com/WordPress/performance/issues/1032</a>. <a href="https://profiles.wordpress.org/westonruter/" class="mention"><span class="mentions-prefix">@</span>westonruter</a> were you planning to pick that up from Felix, or do we need someone else to help move this forward?
<ul>
<li><a href="https://profiles.wordpress.org/westonruter/" class="mention"><span class="mentions-prefix">@</span>westonruter</a> had not planned it but <a href="https://profiles.wordpress.org/thelovekesh/" class="mention"><span class="mentions-prefix">@</span>thelovekesh</a> offered to pick up</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/westonruter/" class="mention"><span class="mentions-prefix">@</span>westonruter</a> Both Speculative Loading (<a href="https://github.com/WordPress/performance/pull/1159" target="_blank" rel="noreferrer noopener">PR</a> merged) and Optimization Detective (<a href="https://github.com/WordPress/performance/pull/1185" target="_blank" rel="noreferrer noopener">PR</a> pending merge, review please) will be able to be embedded in other plugins or themes to increase adoption. This is more relevant to Optimization Detective since it is lower-level plumbing which optimization plugins can leverage, and Speculative Loading is getting popular.
<ul>
<li>Also for Speculative Loading, there’s a <a href="https://github.com/WordPress/performance/pull/1178" target="_blank" rel="noreferrer noopener">PR</a> open to add a filter for whether speculation rules are printed and default to not printing when the user is logged-in non-admin or PHP session is active. Could use additional eyes to confirm the approach. Should there be a checkbox for whether to enable for logged-in users? Also, perhaps Speculative Loading should add a Site Health check for when PHP sessions are being used on the frontend so a user can be aware why it doesn’t seem to be doing anything?</li>
</ul>
</li>
</ul>
<h2 class="wp-block-heading" id="object-caching">Active Priority Projects</h2>
<h3 class="wp-block-heading" id="measurement">Improve template loading</h3>
<ul>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> There are really only three issues remaining in this project, <a href="https://core.trac.wordpress.org/ticket/59595">#59595</a>, <a href="https://core.trac.wordpress.org/ticket/59600">#59600</a>, and <a href="https://core.trac.wordpress.org/ticket/57789">#57789</a> (which we already discussed and is probably the most important next step).</li>
</ul>
<h3 class="wp-block-heading" id="javascript">INP research opportunities</h3>
<ul>
<li>No updates this week</li>
<li><a href="https://github.com/WordPress/performance/issues/1120">GitHub tracking issue</a></li>
</ul>
<h3 class="wp-block-heading">Improving the calculation of image size attributes</h3>
<ul>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> I spent some time updating <a href="https://github.com/WordPress/performance/issues/760" target="_blank" rel="noreferrer noopener">the overview issue for Improving Images </a><code>sizes</code>, and began filling in some details. This project covers two main efforts to improve the way WP calculates <code>sizes</code>:
<ul>
<li>Improving the default <code>sizes</code> algorithm (accounting for layout)</li>
<li>Implement the auto-sizes HTML spec (already handed by the auto-sizes plugin)</li>
</ul>
</li>
<li>Rather than creating a whole separate performance feature plugin for developing the improvements to the default <code>sizes</code> algorithm, I think it makes sense to combine all of this into the original auto-sizes plugin.</li>
<li>In addition, I created <a href="https://github.com/WordPress/performance/issues/1186" target="_blank" rel="noreferrer noopener">an issue</a> to track the work needed to measure and track the impact of these changes, in which I link to the latest data we were able to query from HTTPArchive as a baseline.</li>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> has assigned one issue to <a href="https://profiles.wordpress.org/mukesh27/" class="mention"><span class="mentions-prefix">@</span>mukesh27</a> </li>
</ul>
<h3 class="wp-block-heading">Optimized autoloaded options</h3>
<ul>
<li>Updates covered in WordPress 6.6 item above</li>
</ul>
<h1 class="wp-block-heading">Open Floor</h1>
<ul>
<li><a href="https://profiles.wordpress.org/mukesh27/" class="mention"><span class="mentions-prefix">@</span>mukesh27</a> Is there any plan to merge <a href="https://github.com/WordPress/performance/tree/trunk/includes/site-health/audit-autoloaded-options" target="_blank" rel="noreferrer noopener">https://github.com/WordPress/performance/tree/trunk/includes/site-health/audit-autoloaded-options</a> in core?
<ul>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a> The blocker for the above was at the lack of action to. </li>
<li>it is all well and good highlighting that there are 20 options that are very large, but with no way to fix it, a user it out of luck. I had planned to have a way of changing options to be from being autoloaded or not. Think checkbox and rest api to update the row in the database. I haven’t had anytime to look at now I am not sponsored.</li>
</ul>
</li>
</ul>
<p><strong>Our next chat will be held on <a href="https://www.timeanddate.com/worldclock/fixedtime.html?iso=20240507T1500"><abbr class="date" title="2024-05-07T15:00:00+00:00">Tuesday, May 7, 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>

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…