<div style="text-align:center"><img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///ywAAAAAAQABAAACAUwAOw==" fifu-lazy="1" fifu-data-sizes="auto" fifu-data-srcset="https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-23-april-2024.png?ssl=1&w=75&resize=75&ssl=1 75w, https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-23-april-2024.png?ssl=1&w=100&resize=100&ssl=1 100w, https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-23-april-2024.png?ssl=1&w=150&resize=150&ssl=1 150w, https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-23-april-2024.png?ssl=1&w=240&resize=240&ssl=1 240w, https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-23-april-2024.png?ssl=1&w=320&resize=320&ssl=1 320w, https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-23-april-2024.png?ssl=1&w=500&resize=500&ssl=1 500w, https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-23-april-2024.png?ssl=1&w=640&resize=640&ssl=1 640w, https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-23-april-2024.png?ssl=1&w=800&resize=800&ssl=1 800w, https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-23-april-2024.png?ssl=1&w=1024&resize=1024&ssl=1 1024w, https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-23-april-2024.png?ssl=1&w=1280&resize=1280&ssl=1 1280w, https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-23-april-2024.png?ssl=1&w=1600&resize=1600&ssl=1 1600w" width="1280" height="720" fifu-data-src="https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-23-april-2024.png?ssl=1" class="attachment-post-thumbnail size-post-thumbnail wp-post-image" alt="Performance Chat Summary: 23 April 2024" title="Performance Chat Summary: 23 April 2024" srcset="https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-23-april-2024.png?ssl=1 1280w, https://www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-23-april-2024-300x169.png 300w, https://www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-23-april-2024-1024x576.png 1024w, https://www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-23-april-2024-768x432.png 768w" sizes="(max-width: 1280px) 100vw, 1280px" /></div><div>
<p><a href="https://make.wordpress.org/core/2024/04/22/performance-chat-agenda-23-april-2024/">Meeting agenda here</a> and the full chat log is available <a href="https://wordpress.slack.com/archives/C02KGN5K076/p1713884403319709">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>
</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/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a> <a href="https://core.trac.wordpress.org/ticket/59442">#59442</a> is nearly ready to commit</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> the <a href="https://wordpress.org/plugins/speculation-rules/" data-type="link" data-id="https://wordpress.org/plugins/speculation-rules/">Speculative Loading plugin</a> is already at 9000+ active installs! I expect it to tip into the 10k+ range today as the counts have been increasing about 1k per day
<ul>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> One of the important things for us to understand with Speculative Loading is what the impacts are on the sites that are using it, that includes performance impact, obviously, but also how it effects things like server resource usage, integration with analytics or other things that may not expect some requests to come from non-users.</li>
<li><a href="https://profiles.wordpress.org/westonruter/" class="mention"><span class="mentions-prefix">@</span>westonruter</a> Yes, the readme has been updated to note that. However, people don’t always read the readmes</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/westonruter/" class="mention"><span class="mentions-prefix">@</span>westonruter</a> planning to kick off the Image Prioritizer plugin this week which will split out the image-specific logic from Optimization Detective, leaving that plugin as an API dependency. We can then feature Image Prioritizer in the PL plugin to promote to users.</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> For the ongoing template loading epic we’ve been working on (<a href="https://github.com/WordPress/performance/issues/746" target="_blank" rel="noreferrer noopener">https://github.com/WordPress/performance/issues/746</a>) there are 3 main tickets we’re tracking for 6.6:
<ul>
<li><a href="https://core.trac.wordpress.org/ticket/59600" target="_blank" rel="noreferrer noopener">https://core.trac.wordpress.org/ticket/59600</a></li>
<li><a href="https://core.trac.wordpress.org/ticket/57789" target="_blank" rel="noreferrer noopener">https://core.trac.wordpress.org/ticket/57789</a></li>
<li><a href="https://core.trac.wordpress.org/ticket/59595" target="_blank" rel="noreferrer noopener">https://core.trac.wordpress.org/ticket/59595</a></li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> On <a href="https://core.trac.wordpress.org/ticket/59600">#59600</a>, I just committed <a href="https://core.trac.wordpress.org/changeset/58025">r58025</a>, which covers block theme patterns on Friday. As <a href="https://profiles.wordpress.org/thekt12/" class="mention"><span class="mentions-prefix">@</span>thekt12</a> has looked into improvements for block templates and template parts, it seems that most of the cost is related to the underlying Theme JSON processing, which is covered by <a href="https://core.trac.wordpress.org/ticket/57789">#57789</a>
<ul>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> did some cleanup, and added some updates to <a href="https://core.trac.wordpress.org/ticket/57789">#57789</a> on that ticket yesterday</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a> Is anyone looking into <a href="https://core.trac.wordpress.org/ticket/59596">#59596</a>
<ul>
<li>Call file size on every css file results in multiple file operations. Might be a good one to pickup, there is already a PR, should be simple to get across the line.</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/thekt12/" class="mention"><span class="mentions-prefix">@</span>thekt12</a> most of this is repeat to what <a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> said above-
<ul>
<li><a href="https://core.trac.wordpress.org/ticket/59600">#59600</a> Performance regression in block tempalte part was related to get_theme_data ( this will be handled in <a href="https://core.trac.wordpress.org/ticket/57789">#57789</a> )</li>
<li><a href="https://core.trac.wordpress.org/ticket/59595">#59595</a> Current implementation (<a href="https://github.com/WordPress/wordpress-develop/pull/6392" target="_blank" rel="noreferrer noopener">PR#6392</a>) was found to have benefit but need to resolve circular dependency – a bit complex scenerio (<a href="https://github.com/WordPress/wordpress-develop/pull/6392#discussion_r1572619712" target="_blank" rel="noreferrer noopener">this</a>)</li>
<li><a href="https://core.trac.wordpress.org/ticket/57789">#57789</a> So far we have observed benefits of caching <code>WP_Theme_JSON_Resolver::get_theme_data</code> – I am checking any side effects if we do so.</li>
<li>We will be caching <code>WP_Theme_JSON_Resolver::get_core_data</code> data inside <code>WP_Theme_JSON_Resolver::get_merged_data</code> , we believe it will result in 3-4% improvement alone and is not subjected to much change.</li>
</ul>
</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> noted that he worked with <a href="https://profiles.wordpress.org/adamsilverstein/" class="mention"><span class="mentions-prefix">@</span>adamsilverstein</a> and started looking into creating a Colab to capture and compare metrics for this, which is what I’m planning to focus on this week</li>
</ul>
<h3 class="wp-block-heading">Optimized autoloaded options</h3>
<ul>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> I created a follow-up ticket last week to update the default auto load option values that get set by core to use the new schema we introduced in <strong><a href="https://core.trac.wordpress.org/ticket/42441" target="_blank" rel="noreferrer noopener">#42441</a></strong>. <a href="https://profiles.wordpress.org/pbearne/" class="mention"><span class="mentions-prefix">@</span>pbearne</a> also started a draft of the dev-note for that change, which I owe a review on.
<ul>
<li><a href="https://core.trac.wordpress.org/ticket/61045">#61045</a> is the new ticket</li>
<li><a href="https://profiles.wordpress.org/pbearne/" class="mention"><span class="mentions-prefix">@</span>pbearne</a> do we need to look at default themes?</li>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> I think that’s probably a good idea. Interestingly, it looks like the commit for <a href="https://core.trac.wordpress.org/ticket/42441">#42441</a> may already have a positive performance impact in our performance tests, which is a bit unexpected given that we shouldn’t have changed the autoload behavior for any core options, so it’s something I want to review deeper.</li>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> You can see it in <a href="https://www.codevitals.run/project/wordpress" target="_blank" rel="noreferrer noopener">https://www.codevitals.run/project/wordpress</a> and also in <a href="https://github.com/WordPress/wordpress-develop/actions/runs/8545770926" target="_blank" rel="noreferrer noopener">the Performance Test GH Summary for that commit</a></li>
</ul>
</li>
</ul>
<h1 class="wp-block-heading">Open Floor</h1>
<ul>
<li><a href="https://profiles.wordpress.org/clarkeemily/" class="mention"><span class="mentions-prefix">@</span>clarkeemily</a> An announcement here that we have <strong>WordCamp Europe</strong> coming up June 13-15 in Turin, Italy 
<ul>
<li>There will be a Performance Table on Contributor Day (Thu Jun 13) lead by <a href="https://profiles.wordpress.org/adamsilverstein/" class="mention"><span class="mentions-prefix">@</span>adamsilverstein</a> – we would love to see as many people there as possible!</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/thelovekesh/" class="mention"><span class="mentions-prefix">@</span>thelovekesh</a> We have an issue open for feedback on moving PL plugin in plugins directory – <a href="https://github.com/WordPress/performance/issues/1165" target="_blank" rel="noreferrer noopener">https://github.com/WordPress/performance/issues/1165</a>
<ul>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> I’d love to see additional feedback from all of our frequent contributors to this proposal</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> We also have an open issue going about the need to update some of our plugin assets after some recent name changes: <a href="https://github.com/WordPress/performance/issues/1136" target="_blank" rel="noreferrer noopener">https://github.com/WordPress/performance/issues/1136</a>
<ul>
<li><a href="https://profiles.wordpress.org/clarkeemily/" class="mention"><span class="mentions-prefix">@</span>clarkeemily</a> to reach out to Sigal who helped with the existing assets, to provide some mock ups</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> is planning to post a 6.5 wrap up post about our performance efforts this week, just waiting on some final review feedback to come in.</li>
</ul>
<p><strong>Our next chat will be held on <a href="https://www.timeanddate.com/worldclock/fixedtime.html?iso=20240430T1500"><abbr class="date" title="2024-04-30T15:00:00+00:00">Tuesday, April 30, 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…