<div style="text-align:center"></div><div>
<p><a href="https://make.wordpress.org/core/2023/08/07/performance-chat-agenda-8-august-2023/">Meeting agenda here</a> and the full chat log is available <a href="https://wordpress.slack.com/archives/C02KGN5K076/p1691506849019219">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.3 stable release is today</li>
<li>WordPress 6.3 performance highlights post from yesterday: <a rel="noreferrer noopener" href="https://make.wordpress.org/core/2023/08/07/wordpress-6-3-performance-improvements/" target="_blank">https://make.wordpress.org/core/2023/08/07/wordpress-6-3-performance-improvements/</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/aristath/" class="mention"><span class="mentions-prefix">@</span>aristath</a> <a href="https://profiles.wordpress.org/swissspidy/" class="mention"><span class="mentions-prefix">@</span>swissspidy</a></p>
<ul>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> is working with <a href="https://profiles.wordpress.org/mukesh27/" class="mention"><span class="mentions-prefix">@</span>mukesh27</a> on an exploration of ways we can improve performance of the template loading process, which we’ve seen be responsible for a large portion of the overall server response time. Hoping to have something to share later this week. He also plans to do another (smaller) profiling analysis of WP 6.3 after the release today to see if we can identify any optimizations that we can put in place during this release cycle</li>
<li><a href="https://profiles.wordpress.org/swissspidy/" class="mention"><span class="mentions-prefix">@</span>swissspidy</a> is summarizing the responses to the<a rel="noreferrer noopener" href="https://make.wordpress.org/core/2023/07/24/i18n-performance-analysis/" target="_blank"> i18n peformance analysis</a> this week together with some suggested next steps (which is probably going to involve a feature plugin / PL module).</li>
<li>Not directly part of the template loading work, but closely related, <a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> shared <a href="https://profiles.wordpress.org/oandregal/" class="mention"><span class="mentions-prefix">@</span>oandregal</a>‘s PR to cache block theme template part data from <code>theme.json</code>: <a rel="noreferrer noopener" href="https://github.com/WordPress/wordpress-develop/pull/4971" target="_blank">https://github.com/WordPress/wordpress-develop/pull/4971</a>
<ul>
<li><a href="https://profiles.wordpress.org/swissspidy/" class="mention"><span class="mentions-prefix">@</span>swissspidy</a>: Maybe at some point we can just build some caching into <code>WP_Theme_JSON_Resolver</code> ? Just so we don’t end up with X similar public functions that are just cached wrappers around it</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a>: I’m curious if we have thought of ways of evaluating the impact of WP 6.3 using HTTPArchive data, or similar so we can compare real world impact to the benchmarks we’ve been doing?
<ul>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: I’m definitely planning to take a closer look once CrUX performance data is available, i.e. starting in September. Separately, we can also measure our success with some more specific not directly performance-related analyses, e.g. check what % of LCP images is lazy-loaded (bad!) or what % of LCP images receives <code>fetchpriority="high"</code> (good!).</li>
<li><a href="https://profiles.wordpress.org/westonruter/" class="mention"><span class="mentions-prefix">@</span>westonruter</a> is looking into measuring script loading strategy adoption. The upcoming Gutenberg release will have <code>defer</code> scripts so hopefully we’ll get some data soon</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/thekt12/" class="mention"><span class="mentions-prefix">@</span>thekt12</a> is working on changes related to <a rel="noreferrer noopener" href="https://core.trac.wordpress.org/ticket/58532" target="_blank">https://core.trac.wordpress.org/ticket/58532</a> (block_has_support performance enhancement).</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/aristath/" class="mention"><span class="mentions-prefix">@</span>aristath</a> <a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a> <a href="https://profiles.wordpress.org/olliejones/" class="mention"><span class="mentions-prefix">@</span>olliejones</a> </p>
<ul>
<li><a href="https://profiles.wordpress.org/mukesh27/" class="mention"><span class="mentions-prefix">@</span>mukesh27</a> raised <a rel="noreferrer noopener" href="https://github.com/WordPress/wordpress-develop/pull/4970" target="_blank">PR Provide a way to load multiple specific options with a single database request #4970</a> for ticket <a rel="noreferrer noopener" href="https://core.trac.wordpress.org/ticket/58962" target="_blank">https://core.trac.wordpress.org/ticket/58962</a>, If anyone has spare time, please take a look.</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/adamsilverstein/" class="mention"><span class="mentions-prefix">@</span>adamsilverstein</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/10upsimon/" class="mention"><span class="mentions-prefix">@</span>10upsimon</a>: New script loading strategy API will of course be released today with 6.3! The docs team has taken ownership of the documentation document that we drafted (with the intent to update all the necessary areas)</li>
<li><a href="https://profiles.wordpress.org/westonruter/" class="mention"><span class="mentions-prefix">@</span>westonruter</a> <a rel="noreferrer noopener" href="https://core.trac.wordpress.org/changeset/56355" target="_blank">committed</a> use of <code>defer</code> for the <code>wp-embed</code> script.</li>
<li><a href="https://profiles.wordpress.org/westonruter/" class="mention"><span class="mentions-prefix">@</span>westonruter</a> worked queries to determine <a rel="noreferrer noopener" href="https://github.com/GoogleChromeLabs/wpp-research/pull/63" target="_blank">frequency of themes/plugins adding blocking/async/defer scripts in head/footer</a>. Good news that most sites have embraced <code>$in_footer</code>: around 80% of blocking scripts are in the footer instead of the head. Nevertheless, there are opportunities to engage with the 20% to consider moving blocking head scripts to the footer, <em>or rather add </em><code><em>defer</em></code><em> and leave in the </em><code><em>head</em></code>. He also queried for the specific themes and plugins that seem to be adding those blocking head scripts, so we can engage with the plugin authors for possible adoption. (The list is in that same PR.)</li>
<li>On the emoji loader front, which accounts for a large improvement to LCP-TTFB in 6.3, <a href="https://profiles.wordpress.org/westonruter/" class="mention"><span class="mentions-prefix">@</span>westonruter</a> tried querying for HTTP Archive for how often sites have the emoji loader enabled. Found that 61.8% indexed sites have it enabled, with the sites not indexed (the long tail) surely having it more commonly enabled (since it is enabled by default). But we should be seeing the large client-side LCP improvement in about two-thirds of sites in HTTP Archive at least.</li>
<li>Also, in relation to inline before/after scripts, <a href="https://profiles.wordpress.org/westonruter/" class="mention"><span class="mentions-prefix">@</span>westonruter</a> created query to determine <a rel="noreferrer noopener" href="https://github.com/GoogleChromeLabs/wpp-research/pull/64" target="_blank">counts for inline script types</a>. The vast majority (~90%) are <em>not</em> <code>after</code> inline scripts. So the fact that we didn’t include support for them in 6.3 probably won’t be hurting us. (In that we shouldn’t commonly be seeing fallbacks to to blocking.)</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></p>
<ul>
<li><a href="https://profiles.wordpress.org/pereirinha/" class="mention"><span class="mentions-prefix">@</span>pereirinha</a> is making good progress on <a rel="noreferrer noopener" href="https://core.trac.wordpress.org/ticket/58892" target="_blank">#58892</a>. Currently going through all the needed updates on testing — removing the deprecated tests and adding updated ones; should have a PR ready toward the EOW.</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> opened <a rel="noreferrer noopener" href="https://github.com/WordPress/wordpress-develop/pull/4973" target="_blank">https://github.com/WordPress/wordpress-develop/pull/4973</a> yesterday which is a PR to fix images within shortcodes to be handled properly with the other content that it is part of (see <a rel="noreferrer noopener" href="https://core.trac.wordpress.org/ticket/58853" target="_blank">https://core.trac.wordpress.org/ticket/58853</a>). This morning there are still test failures, so he’ll take another look shortly, but other than that it’s ready for review.
<ul>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a>: I planned to write a test to demonstrate the use case I mentioned in that ticket about <code>do_shortcode()</code> when used directly to generate markup that then gets processed again on <code>the_content</code> filter.</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: I added a test on the PR covering what <em>I think</em> you meant, but that may not be what you meant, so it would be great if you could take a look.</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a>: Still watching browser implementation of auto-sizes for lazy-loaded images, but no updates over the past few weeks.</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/olliejones/" class="mention"><span class="mentions-prefix">@</span>olliejones</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></p>
<ul>
<li><a href="https://profiles.wordpress.org/westonruter/" class="mention"><span class="mentions-prefix">@</span>westonruter</a> added <a rel="noreferrer noopener" href="https://github.com/GoogleChromeLabs/wpp-research/pull/62" target="_blank">added network condition emulation</a> to the benchmark-web-vitals command. This will allow us to simulate Slow 3G and Fast 3G when benchmarking.</li>
<li><a href="https://profiles.wordpress.org/swissspidy/" class="mention"><span class="mentions-prefix">@</span>swissspidy</a> recently built <a rel="noreferrer noopener" href="https://github.com/swissspidy/compare-wp-performance" target="_blank">https://github.com/swissspidy/compare-wp-performance</a>, as shared in the performance analysis post; also working on some other stuff for improving the performance testing environment, hope to have something shareable this week.</li>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> ran into an issue yesterday with the way we’re loading the web-vitals library in the CLI script that causes it to get blocked by some sites with restrictive content security policies (CSP). <a rel="noreferrer noopener" href="https://github.com/GoogleChromeLabs/wpp-research/issues/65" target="_blank">Reported here</a>. Spent some time trying some workarounds yesterday without success. Will pick this back up, but if anyone has ideas, feel free to jump in.</li>
<li><a href="https://profiles.wordpress.org/swissspidy/" class="mention"><span class="mentions-prefix">@</span>swissspidy</a>: As a sneak peek for the curious, here’s another GitHub action I just started building, also building on top of the wpp-research CLI utils: <a rel="noreferrer noopener" href="https://github.com/swissspidy/wp-performance-action" target="_blank">https://github.com/swissspidy/wp-performance-action</a></li>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a>: There are a number of improvements for the core performance workflow that we’ve identified, but not yet picked up work on, like <a rel="noreferrer noopener" href="https://core.trac.wordpress.org/ticket/58358" target="_blank">https://core.trac.wordpress.org/ticket/58358</a>, which <a href="https://profiles.wordpress.org/oandregal/" class="mention"><span class="mentions-prefix">@</span>oandregal</a> recently asked about prioritizing. I’m unsure if/how that relates to the work <a href="https://profiles.wordpress.org/swissspidy/" class="mention"><span class="mentions-prefix">@</span>swissspidy</a> is doing and if we want to wait until that effort is done before addressing some of these things, or if we want to move forward on these in the mean time?
<ul>
<li><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;component=Build%2FTest+Tools&#038;col=id&#038;col=summary&#038;col=status&#038;col=owner&#038;col=type&#038;col=priority&#038;col=milestone&#038;order=priority">Overview covering those tickets</a></li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: I think we need to review those and discuss what to prioritize. While partially a reusable performance testing workflow may address them in a more efficient way, we also have to consider the trade-off between the “perfect” solution and getting to a working solution <em>for core</em> faster</li>
<li><a href="https://profiles.wordpress.org/swissspidy/" class="mention"><span class="mentions-prefix">@</span>swissspidy</a>: Yeah so among other things I’m basically looking into tickets like that and for example <a href="https://core.trac.wordpress.org/ticket/58359">#58359</a> to see how best to address them.</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>: We just fixed and merged all the Plugin Checker follow-up issues that we found. To stay up-to-date with our progress, follow us on GitHub: <a rel="noreferrer noopener" href="https://github.com/10up/plugin-check/" target="_blank">https://github.com/10up/plugin-check/</a> We highly value your input! If you have any thoughts, ideas, or feedback, please don’t hesitate to share them on the repository.</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> has been working on a POC, have the UI working with the current WPP standalone plugins being rendered with various states. He is currently working on A/B testing two approaches and hopes to have some direction by tomorrow:
<ul>
<li>Retrofitting core’s <code>updates.js</code> to work in the UI</li>
<li>Custom REST controllers with wpp plugin authored JS to handle the installlation, activation, deactivation etc.</li>
</ul>
</li>
</ul>
<h1 class="wp-block-heading">Open Floor</h1>
<ul>
<li>N/A</li>
</ul>
<p><strong>Our next chat will be held on <a href="https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230815T1500"><abbr class="date" title="2023-08-15T15:00:00+00:00">Tuesday, August 15, 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>

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…
Canada’s largest gathering of WordPress enthusiasts drew a strong turnout at Carleton University last weekend,…