<div style="text-align:center"><img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///ywAAAAAAQABAAACAUwAOw==" fifu-lazy="1" fifu-data-sizes="auto" fifu-data-srcset="https://i2.wp.com/www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-23-july-2024.webp?ssl=1&w=75&resize=75&ssl=1 75w, https://i2.wp.com/www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-23-july-2024.webp?ssl=1&w=100&resize=100&ssl=1 100w, https://i2.wp.com/www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-23-july-2024.webp?ssl=1&w=150&resize=150&ssl=1 150w, https://i2.wp.com/www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-23-july-2024.webp?ssl=1&w=240&resize=240&ssl=1 240w, https://i2.wp.com/www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-23-july-2024.webp?ssl=1&w=320&resize=320&ssl=1 320w, https://i2.wp.com/www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-23-july-2024.webp?ssl=1&w=500&resize=500&ssl=1 500w, https://i2.wp.com/www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-23-july-2024.webp?ssl=1&w=640&resize=640&ssl=1 640w, https://i2.wp.com/www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-23-july-2024.webp?ssl=1&w=800&resize=800&ssl=1 800w, https://i2.wp.com/www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-23-july-2024.webp?ssl=1&w=1024&resize=1024&ssl=1 1024w, https://i2.wp.com/www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-23-july-2024.webp?ssl=1&w=1280&resize=1280&ssl=1 1280w, https://i2.wp.com/www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-23-july-2024.webp?ssl=1&w=1600&resize=1600&ssl=1 1600w" width="583" height="2560" fifu-data-src="https://i2.wp.com/www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-23-july-2024.webp?ssl=1" class="attachment-post-thumbnail size-post-thumbnail wp-post-image" alt="Performance Chat Summary: 23 July 2024" title="Performance Chat Summary: 23 July 2024" srcset="https://i2.wp.com/www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-23-july-2024.webp?ssl=1 583w, https://www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-23-july-2024-68x300.webp 68w, https://www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-23-july-2024-233x1024.webp 233w, https://www.awordpresscommenter.com/wp-content/uploads/2024/11/performance-chat-summary-23-july-2024-350x1536.webp 350w" sizes="(max-width: 583px) 100vw, 583px" /></div><div>
<p><a href="https://make.wordpress.org/core/2024/07/23/performance-chat-agenda-23-july-2024/">Meeting agenda here</a> and the full chat log is available <a href="https://wordpress.slack.com/archives/C02KGN5K076/p1721746803571199">beginning here on Slack</a>.</p>
<h1 class="wp-block-heading">Announcements</h1>
<ul class="wp-block-list">
<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>
<ul class="wp-block-list">
<li>WordPress performance Trac tickets
<ul class="wp-block-list">
<li>Current release (6.7)</li>
<li>Future releases</li>
</ul>
</li>
<li>Performance Lab plugin (and other performance plugins)
<ul class="wp-block-list">
<li>Enhanced Responsive Images</li>
<li>Embed Optimizer</li>
<li>Image Prioritizer</li>
<li>Image Placeholders</li>
<li>Modern Image Formats</li>
<li>Optimization Detective</li>
<li>Performant Translations</li>
<li>Speculative Loading</li>
</ul>
</li>
<li>Active priority projects</li>
</ul>
<h2 class="wp-block-heading" id="images">WordPress Performance Trac Tickets</h2>
<ul class="wp-block-list">
<li>There are currently <a href="https://core.trac.wordpress.org/query?status=accepted&#038;status=assigned&#038;status=new&#038;status=reopened&#038;status=reviewing&#038;focuses=~performance&#038;milestone=6.7&#038;order=priority">16 performance issues in 6.7</a> </li>
<li><a href="https://profiles.wordpress.org/pbearne/" class="mention"><span class="mentions-prefix">@</span>pbearne</a> I need input on this ticket as I made opinionated changes as to which option should not be autoloaded <a href="https://core.trac.wordpress.org/ticket/61103">#61103</a>
<ul class="wp-block-list">
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> I plan on digging into that PR to give you feedback, but am going to be out on holiday for a bit. If anyone else has time to look at this in the mean time, please do so.</li>
<li><a href="https://profiles.wordpress.org/mukesh27/" class="mention"><span class="mentions-prefix">@</span>mukesh27</a> I will take a look this week</li>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> One thing that will be good to understand, is that if we aren’t autoloading options that are only needed in the admin, how do we make sure the editor experience isn’t negatively affected. I think you’re already planning on priming all of those options in the admin, but would be good to get some performance measurements of the before/after of both the front end and admin.</li>
<li><a href="https://profiles.wordpress.org/pbearne/" class="mention"><span class="mentions-prefix">@</span>pbearne</a> I have a patch to load the admin options in back on wp_int</li>
</ul>
</li>
</ul>
<h2 class="wp-block-heading" id="images">Performance Lab Plugin (and other Performance Plugins)</h2>
<ul class="wp-block-list">
<li><a href="https://wordpress.org/plugins/performance-lab/">Performance Lab plugin</a> and the following performance plugins:
<ul class="wp-block-list">
<li><a href="https://wordpress.org/plugins/auto-sizes/">Enhanced Responsive Images</a></li>
<li><a href="https://wordpress.org/plugins/embed-optimizer/">Embed Optimizer</a></li>
<li><a href="https://wordpress.org/plugins/image-prioritizer/">Image Prioritizer</a></li>
<li><a href="https://wordpress.org/plugins/dominant-color-images/">Image Placeholders</a></li>
<li><a href="https://wordpress.org/plugins/webp-uploads/">Modern Image Formats</a></li>
<li><a href="https://wordpress.org/plugins/optimization-detective/">Optimization Detective (Developer Preview)</a></li>
<li><a href="https://wordpress.org/plugins/performant-translations/">Performant Translations</a></li>
<li><a href="https://wordpress.org/plugins/speculation-rules/">Speculative Loading</a></li>
</ul>
</li>
</ul>
<ul class="wp-block-list">
<li><a href="https://profiles.wordpress.org/mukesh27/" class="mention"><span class="mentions-prefix">@</span>mukesh27</a> I have been working on PRs that ready for review<strong>:</strong>
<ul class="wp-block-list">
<li><strong>Performance Lab plugin</strong>:
<ul class="wp-block-list">
<li>PR <a href="https://github.com/WordPress/performance/pull/1374" target="_blank" rel="noreferrer noopener">#1374</a> – Autoloaded Options Health Check: Disabled options reappear in Site Health after external update</li>
</ul>
</li>
<li><strong>Modern Image Formats plugin</strong>:
<ul class="wp-block-list">
<li>PR <a href="https://github.com/WordPress/performance/pull/1354" target="_blank" rel="noreferrer noopener">#1354</a> – Picture element: The accurate sizes improvement for images not working</li>
</ul>
</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/westonruter/" class="mention"><span class="mentions-prefix">@</span>westonruter</a> It seems like we’re getting increasing reports of issues with image generation in <strong>Modern Image Formats</strong>
<ul class="wp-block-list">
<li>In <a href="https://github.com/WordPress/performance/issues/1390">GitHub</a> and <a href="https://wordpress.org/support/topic/broken-images-in-blog-post-images-not-replaced-with-avif-are-broken/#post-17900799">support forums</a></li>
<li><a href="https://profiles.wordpress.org/westonruter/" class="mention"><span class="mentions-prefix">@</span>westonruter</a> Might be related to the issue of AVIF generation taking a very long time sometimes?</li>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> Ah, I do remember cases a long time ago where image generation could take longer than the max PHP timeout on some hosts and result in the attachment data being created in the DB while the actual image generation failed. I wonder if something like that is happening?</li>
<li><a href="https://profiles.wordpress.org/westonruter/" class="mention"><span class="mentions-prefix">@</span>westonruter</a> That’s being discussed here: <a href="https://github.com/WordPress/performance/issues/371" target="_blank" rel="noreferrer noopener">https://github.com/WordPress/performance/issues/371</a></li>
<li><a href="https://profiles.wordpress.org/adamsilverstein/" class="mention"><span class="mentions-prefix">@</span>adamsilverstein</a> this could also be a support detection issue, (where format support for AVIF gives a false negative or positive), interesting they say it falls back to WebP</li>
<li><a href="https://profiles.wordpress.org/westonruter/" class="mention"><span class="mentions-prefix">@</span>westonruter</a> I wonder if the AVIF generation should be moved a background process? Use the JPEG immediately upon upload and then use the AVIF once it is available</li>
<li><a href="https://profiles.wordpress.org/adamsilverstein/" class="mention"><span class="mentions-prefix">@</span>adamsilverstein</a> we already have a way of generating images in multiple passes, but it needs to be able to process one image completely before the timeout</li>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> That’s a good idea. There is prior art for generating missing intermediate sizes that could be referenced.</li>
<li><a href="https://profiles.wordpress.org/pbearne/" class="mention"><span class="mentions-prefix">@</span>pbearne</a> Idea: we need a long process control for wp-admin that can be used for any task that takes a long time (images gen, post delete, etc.)</li>
<li><a href="https://profiles.wordpress.org/adamsilverstein/" class="mention"><span class="mentions-prefix">@</span>adamsilverstein</a> <a href="https://github.com/WordPress/performance/issues/490">https://github.com/WordPress/performance/issues/490</a> was part of that previous effort, there is also a trac ticket</li>
<li><a href="https://profiles.wordpress.org/westonruter/" class="mention"><span class="mentions-prefix">@</span>westonruter</a> I thought that was primarily for regenerating the entire media library</li>
<li><a href="https://profiles.wordpress.org/adamsilverstein/" class="mention"><span class="mentions-prefix">@</span>adamsilverstein</a> yes, but part of that was the ability to regenerate images in i the background <a href="https://core.trac.wordpress.org/ticket/6814">#6814</a> 16 year old ticket</li>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> It’s not totally accurate anymore, after <a href="https://core.trac.wordpress.org/ticket/40439">#40439</a></li>
<li><a href="https://profiles.wordpress.org/adamsilverstein/" class="mention"><span class="mentions-prefix">@</span>adamsilverstein</a> true, we partially solved the issue with that, as long as the user agent remains present to trigger the retries</li>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> I’ve played with using WP_Cron for this a looooooong time ago, but that can cause failures to affect end-user front-end requests, which we’d want to avoid</li>
</ul>
</li>
</ul>
<h2 class="wp-block-heading" id="object-caching">Active Priority Projects</h2>
<h3 class="wp-block-heading">Improving the calculation of image size attributes</h3>
<ul class="wp-block-list">
<li><a href="https://profiles.wordpress.org/mukesh27/" class="mention"><span class="mentions-prefix">@</span>mukesh27</a> For Improving the calculation of image size attributes i have been working on:
<ul class="wp-block-list">
<li>PR <a href="https://github.com/WordPress/performance/pull/1382" target="_blank" rel="noreferrer noopener">#1382</a> – Update <code>wp_calculate_image_sizes</code> to Reflect Changes in sizes attribute</li>
<li>Issue <a href="https://github.com/WordPress/performance/issues/1389" target="_blank" rel="noreferrer noopener">#1389</a> – Accurate sizes improvement didn’t account for the disable filter for sizes</li>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> I’m reviewing those this morning</li>
</ul>
</li>
</ul>
<h3 class="wp-block-heading">Plugin Check</h3>
<ul class="wp-block-list">
<li><a href="https://profiles.wordpress.org/swissspidy/" class="mention"><span class="mentions-prefix">@</span>swissspidy</a> there is 1 new performance-related check being worked on that’s ready for code review: <a href="https://github.com/WordPress/plugin-check/pull/519" target="_blank" rel="noreferrer noopener">https://github.com/WordPress/plugin-check/pull/519</a>. There are more PRs some other contributors are working on, but nothing performance-specific.</li>
</ul>
<h1 class="wp-block-heading">Open Floor</h1>
<ul class="wp-block-list">
<li>WordPress 6.6 performance analysis
<ul class="wp-block-list">
<li><a href="https://profiles.wordpress.org/adamsilverstein/" class="mention"><span class="mentions-prefix">@</span>adamsilverstein</a> Yes… I have been working on a post for 6.6 performance changes and will share a draft here for feedback soon!</li>
<li>one challenge has been identifying the source of the slight regressions we see in 6.6 (the numbers haven’t changed much since I shared results here for an RC a few weeks ago)</li>
<li>part of the challenges is tracking changes that originate in the Gutenberg project and are then merged over to core. our automated tests haven’t highlighted issues, nor are the Gutenberg performance tests</li>
<li>some ideas: it might be because the regressions are very small and spread out over a number of commits, or it might be related to the difference in how we are doing automated tests. in case, it points to an area we can improve</li>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> Agreed. There are a number of improvements that we could make to our CI infrastructure in both the GB repo and in Core that would help. We’ve already got <a href="https://github.com/WordPress/performance/issues/1380" target="_blank" rel="noreferrer noopener">https://github.com/WordPress/performance/issues/1380</a> as a place to discuss a set of improvements we want to focus on next. I’d love to see more discussion there so we can define and prioritize some next steps.</li>
<li>One of the questions that I still have is whether the benchmarks that we have been taking at the end of each release are providing us with useful info, or if they are obscuring what is really happening in the field. <a href="https://profiles.wordpress.org/adamsilverstein/" class="mention"><span class="mentions-prefix">@</span>adamsilverstein</a> I’m curious if we could get some HTTPArchive data after 6.6 has been out a while to see if our lab benchmarks relate to real user data or not.</li>
<li><a href="https://profiles.wordpress.org/adamsilverstein/" class="mention"><span class="mentions-prefix">@</span>adamsilverstein</a> that is a good point, I’m happy to work on that. we should have enough data in a few months.</li>
<li>some performance improvements we are adding will really only become apparent in the field data, and our automated testing can’t really measure those</li>
</ul>
</li>
</ul>
<p><strong>Our next chat will be held on <a href="https://www.timeanddate.com/worldclock/fixedtime.html?iso=20240730T1500"><abbr class="date" title="2024-07-30T15:00:00+00:00">Tuesday, July 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>

WordPress co-founder Matt Mullenweg will deliver this year’s State of the Word in San Francisco…
Automattic has teamed up with the Internet Archive to launch a new plugin designed to…
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…