<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/2022/10/performance-team-meeting-summary-4-october-2022.png?ssl=1&w=75&resize=75&ssl=1 75w, https://i2.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/10/performance-team-meeting-summary-4-october-2022.png?ssl=1&w=100&resize=100&ssl=1 100w, https://i2.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/10/performance-team-meeting-summary-4-october-2022.png?ssl=1&w=150&resize=150&ssl=1 150w, https://i2.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/10/performance-team-meeting-summary-4-october-2022.png?ssl=1&w=240&resize=240&ssl=1 240w, https://i2.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/10/performance-team-meeting-summary-4-october-2022.png?ssl=1&w=320&resize=320&ssl=1 320w, https://i2.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/10/performance-team-meeting-summary-4-october-2022.png?ssl=1&w=500&resize=500&ssl=1 500w, https://i2.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/10/performance-team-meeting-summary-4-october-2022.png?ssl=1&w=640&resize=640&ssl=1 640w, https://i2.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/10/performance-team-meeting-summary-4-october-2022.png?ssl=1&w=800&resize=800&ssl=1 800w, https://i2.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/10/performance-team-meeting-summary-4-october-2022.png?ssl=1&w=1024&resize=1024&ssl=1 1024w, https://i2.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/10/performance-team-meeting-summary-4-october-2022.png?ssl=1&w=1280&resize=1280&ssl=1 1280w, https://i2.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/10/performance-team-meeting-summary-4-october-2022.png?ssl=1&w=1600&resize=1600&ssl=1 1600w" width="514" height="1746" fifu-data-src="https://i2.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/10/performance-team-meeting-summary-4-october-2022.png?ssl=1" class="attachment-post-thumbnail size-post-thumbnail wp-post-image" alt="Performance team meeting summary 4 October 2022" title="Performance team meeting summary 4 October 2022" srcset="https://i2.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/10/performance-team-meeting-summary-4-october-2022.png?ssl=1 514w, https://www.awordpresscommenter.com/wp-content/uploads/2022/10/performance-team-meeting-summary-4-october-2022-88x300.png 88w, https://www.awordpresscommenter.com/wp-content/uploads/2022/10/performance-team-meeting-summary-4-october-2022-452x1536.png 452w" sizes="(max-width: 514px) 100vw, 514px" /></div><div>
<p><a href="https://make.wordpress.org/core/2022/10/03/performance-chat-agenda-4-october-2022/">Meeting agenda here</a> and the full chat log is available <a href="https://wordpress.slack.com/archives/C02KGN5K076/p1664895645634169">beginning here on Slack</a>.</p>
<h2>Announcements</h2>
<ul>
<li><a href="https://profiles.wordpress.org/shetheliving/" class="mention"><span class="mentions-prefix">@</span>shetheliving</a>: <a href="https://docs.google.com/document/d/1X04VyZ5j-UaGchXqWnZNER3arGv1XXo3abw4YfSnN3M/edit#">Mission and philosophies</a> review
<ul>
<li>Drafting a Handbook for <a href="https://make.wordpress.org/performance/">our site</a> and would like to include overall mission for the team</li>
<li>Please review and leave comments on the doc with your thoughts</li>
</ul>
</li>
</ul>
<h2 id="focus-group-updates">Focus group updates</h2>
<h3 id="images">Images</h3>
<p><a href="https://profiles.wordpress.org/adamsilverstein/" class="mention"><span class="mentions-prefix">@</span>adamsilverstein</a> <a href="https://profiles.wordpress.org/mikeschroder/" class="mention"><span class="mentions-prefix">@</span>mikeschroder</a></p>
<p><a href="https://github.com/WordPress/performance/projects/1">GitHub project</a></p>
<ul>
<li><a href="https://profiles.wordpress.org/adamsilverstein/" class="mention"><span class="mentions-prefix">@</span>adamsilverstein</a>: Not much to update, worked on a bug fix for <a href="https://core.trac.wordpress.org/ticket/56442">#56442</a></li>
<li><a href="https://profiles.wordpress.org/eugenemanuilov/" class="mention"><span class="mentions-prefix">@</span>eugenemanuilov</a>: <a href="https://github.com/WordPress/performance/issues/524">#524</a> to disable JPEG subsizes generation for WebP images has been updated based on feedback from <a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a></li>
<li><a href="https://profiles.wordpress.org/mukesh27/" class="mention"><span class="mentions-prefix">@</span>mukesh27</a>: Working on <a rel="noreferrer noopener" href="https://github.com/WordPress/performance/issues/525" target="_blank">#525</a> to add a checkbox to the Media screen to enable multi-MIME type output, to match with the core WebP implementation</li>
<li><a href="https://profiles.wordpress.org/ankitgade/" class="mention"><span class="mentions-prefix">@</span>ankitgade</a>: Working on background processing infrastructure related to image regeneration
<ul>
<li>Background job class PR <a rel="noreferrer noopener" href="https://github.com/WordPress/performance/pull/507" target="_blank">#507</a> is merged</li>
<li>Background process runner <a rel="noreferrer noopener" href="https://github.com/WordPress/performance/pull/512" target="_blank">PR</a> is in progress and will be ready to review tonight</li>
<li>Admin queue screen <a rel="noreferrer noopener" href="https://github.com/WordPress/performance/pull/533" target="_blank">PR</a> is work in progress</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/khoipro/" class="mention"><span class="mentions-prefix">@</span>khoipro</a>: Any updates on SVG uploads?
<ul>
<li><a href="https://profiles.wordpress.org/shetheliving/" class="mention"><span class="mentions-prefix">@</span>shetheliving</a>: No one is actively working on this at the moment, so anyone can pick it up if they have time <a href="https://github.com/WordPress/performance/issues/427">https://github.com/WordPress/performance/issues/427</a></li>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a>: Not working on this right now, but may in the future. Biggest blocker is that the library that everyone uses for cleaning SVGs requires PHP 7+, so it would need to be forked/rewritten if we wanted backwards compatibility. If we wanted to make it a PHP 7+-only feature, it would make things a lot easier.</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: WP hasn’t really done that before, but don’t think it’s a no-go as long as it’s a non-critical feature</li>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a>: PHP 5.6 is only 4% of WP installs, per https://wordpress.org/about/stats/</li>
<li><a href="https://profiles.wordpress.org/adamsilverstein/" class="mention"><span class="mentions-prefix">@</span>adamsilverstein</a>: We already do something like this with server support for images where you can’t use a format unless your server supports it</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: As long it gracefully falls back if unsupported and doesn’t break anything on older versions, would be totally onboard</li>
<li><a href="https://profiles.wordpress.org/khoipro/" class="mention"><span class="mentions-prefix">@</span>khoipro</a>: What about sanitize and escape file uploading, and styling SVG in media preview?</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: Matt also mentioned a few years back that he would be open to WP offering certain features only to sites with HTTPS, kind of similar</li>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a>: The creator of the library was open to support, not sure how much work we would need to do to port back to 5.6</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: Unless backporting would be super straightforward, I would say it’s not worth our effort and we make it 7+ only</li>
<li><a href="https://profiles.wordpress.org/ankitgade/" class="mention"><span class="mentions-prefix">@</span>ankitgade</a>: We can analyze what issues we see on 5.6 to evaluate how difficult this would be</li>
</ul>
</li>
</ul>
<h4 id="feedback-requested">Feedback requested</h4>
<ul>
<li>See above</li>
<li><a href="https://github.com/WordPress/performance/issues?q=is%3Aopen+project%3AWordPress%2Fperformance%2F1+label%3A%22Needs+Discussion%22">Needs Discussion</a> (9 issues)</li>
<li><a href="https://github.com/WordPress/performance/issues?q=is%3Aopen+project%3AWordPress%2Fperformance%2F1+label%3A%22Needs+Review%22+">Needs Review</a> (2 issues)</li>
</ul>
<h3 id="object-caching">Object Cache</h3>
<p><a href="https://profiles.wordpress.org/tillkruess/" class="mention"><span class="mentions-prefix">@</span>tillkruess</a> <a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a></p>
<p><a href="https://github.com/WordPress/performance/projects/6">GitHub project</a></p>
<ul>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a>: Committed https://core.trac.wordpress.org/ticket/56721 and need review and commit on https://github.com/WordPress/wordpress-develop/pull/3403</li>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a>: Also been profiling and testing WP 6.1 beta 2 – <a href="https://docs.google.com/spreadsheets/d/1O_76ErpsjUZzEcJLez3GrXhQQyNC-nndTJ61WMYnmj4/edit?usp=sharing">profiling data</a>
<ul>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a>: WP6.1 beta 2 has a slower page generation time than 6.0, in some cases by a lot (0.6325 vs. 0.2929 seconds), even with fewer DB calls in a lot of cases</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: Did you test 1 for each scenario, or multiple and then use average/median results?</li>
</ul>
<ul>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a>: Ran at least three times and did median</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: If we could automate, maybe do something like 5-10 runs to make it more accurate</li>
</ul>
</li>
<li>Also working on dev notes (<a href="https://docs.google.com/document/d/1leEkWUxvcoHd52-lxglz3lX-pS9Fc4nVRGRrH4m9GKk/edit?usp=sharing">1</a>, <a href="https://docs.google.com/document/d/1EFKmDd97jo0St9bIMZ82EDFd2_mDfDEheJ3VuVJUUG0/edit?usp=sharing">2</a>, <a href="https://docs.google.com/document/d/1_D3_J1BwWQ8_zpc7TWWypR-29dHC6l7HZ7eNX0eeMZs/edit?usp=sharing">3</a>) – <a href="https://profiles.wordpress.org/shetheliving/" class="mention"><span class="mentions-prefix">@</span>shetheliving</a> has reviewed and <a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> will take a look today or tomorrow</li>
<li><a href="https://profiles.wordpress.org/khoipro/" class="mention"><span class="mentions-prefix">@</span>khoipro</a>: Will assign someone from their back-end team to take a look at profiling and testing, as well</li>
</ul>
<h4 id="feedback-requested-2">Feedback requested</h4>
<ul>
<li>See above</li>
<li><a href="https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F6+">Needs Discussion</a> (4 issues)</li>
<li><a href="https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Review%22+project%3AWordPress%2Fperformance%2F6+">Needs Review</a> (1 issue)</li>
</ul>
<h3 id="site-health">Site Health</h3>
<p>N/A</p>
<p><a href="https://github.com/WordPress/performance/projects/4">GitHub project</a></p>
<ul>
<li><strong>We’re seeking 1-2 POCs for this group; if you’re interested, please comment here or ping in Slack</strong></li>
<li><a href="https://profiles.wordpress.org/furi3r/" class="mention"><span class="mentions-prefix">@</span>furi3r</a>: Draft Make post is in progress for the new SH checks in 6.1, waiting for a final review before publishing</li>
</ul>
<h4 id="feedback-requested-1">Feedback requested</h4>
<ul>
<li><a href="https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F4+">Needs Discussion</a> (8 issues)</li>
</ul>
<h3 id="measurement">Measurement</h3>
<p>N/A</p>
<p><a href="https://github.com/WordPress/performance/projects/5">GitHub project</a></p>
<ul>
<li><strong>We’re seeking 1-2 POCs for this group; if you’re interested, please comment here or ping in Slack</strong></li>
<li><a href="https://profiles.wordpress.org/shetheliving/" class="mention"><span class="mentions-prefix">@</span>shetheliving</a>: Getting closer to starting engineering on the plugin performance checker thanks to <a href="https://profiles.wordpress.org/mehulkaklotar/" class="mention"><span class="mentions-prefix">@</span>mehulkaklotar</a> and <a href="https://profiles.wordpress.org/jjgrainger/" class="mention"><span class="mentions-prefix">@</span>jjgrainger</a>‘s work on a design doc</li>
</ul>
<h4 id="feedback-requested-1">Feedback requested</h4>
<ul>
<li><a href="https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F5+">Needs Discussion</a> (5 issues)</li>
<li><a href="https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Review%22+project%3AWordPress%2Fperformance%2F5+">Needs Review</a> (1 issue)</li>
</ul>
<h3 id="javascript">JavaScript</h3>
<p><a href="https://profiles.wordpress.org/aristath/" class="mention"><span class="mentions-prefix">@</span>aristath</a> <a href="https://profiles.wordpress.org/sergiomdgomes/" class="mention"><span class="mentions-prefix">@</span>sergiomdgomes</a></p>
<p><a href="https://github.com/WordPress/performance/projects/3">GitHub project</a></p>
<ul>
<li>No updates</li>
</ul>
<h4 id="feedback-requested-3">Feedback requested</h4>
<ul>
<li><a href="https://github.com/WordPress/gutenberg/pull/41020">Tree-shaking block styles on the frontend #41020</a></li>
<li><a href="https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F3+">Needs Discussion</a> (2 issues)</li>
<li><a href="https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Review%22+project%3AWordPress%2Fperformance%2F3+">Needs Review</a> (3 issues)</li>
</ul>
<h2 id="infrastructure">Infrastructure</h2>
<p><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a></p>
<p><a href="https://github.com/WordPress/performance/projects/2">GitHub project</a></p>
<ul>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: Per the <a href="https://github.com/WordPress/performance/issues/531">vote to bump the Performance Lab plugin minimum requirement to WP 6.0</a>, our next release will require 6.0</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: Our next release, 1.6.0, will be Monday, October 17, less than two weeks from now. Any feature or enhancement that you want to include in this release should be completed and merged by next Wednesday, October 12 (see <a href="https://github.com/WordPress/performance/issues/548">#548</a>).</li>
</ul>
<h4 id="feedback-requested-1">Feedback requested</h4>
<ul>
<li>See above</li>
<li><a href="https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F2+">Needs Discussion</a> (6 issues)</li>
<li><a href="https://github.com/WordPress/performance/issues?q=is%3Aopen+project%3AWordPress%2Fperformance%2F2+label%3A%22Needs+Review%22+">Needs Review</a> (3 issues)</li>
</ul>
<h2>Module proposal: <a href="https://github.com/WordPress/performance/issues/551">Server-Timing API</a></h2>
<p><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a></p>
<ul>
<li><a href="https://profiles.wordpress.org/rickjames/" class="mention"><span class="mentions-prefix">@</span>rickjames</a>: For server-side performance measurement, MySQL’s “slowlog” can be useful</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: Not familiar with that tool, but worth exploring another time and feel free to draft a proposal. The current proposal leaves the actual measurement agnostic so it would leave room to introduce a more flexible and opinionated system later.</li>
<li><a href="https://profiles.wordpress.org/adamsilverstein/" class="mention"><span class="mentions-prefix">@</span>adamsilverstein</a>: Overall love the proposal, are you proposing that this would be included in the response by default once this is added?
<ul>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: Yes, envision that it would be added by default</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/johnbillion/" class="mention"><span class="mentions-prefix">@</span>johnbillion</a>: Added a comment on the issue about headers: headers need to be sent before any output, and a lot of processing that happens in WordPress that would ideally be measured occurs after the output begins
<ul>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: Definitely a fair point. Even with that limitation, still a lot of benefit to having the header to measure everything until WP begins to render the output. This will be a known limitation eventually, but also think this will become a smaller issue with FSE sites because they typically generate all content and then it is just “printed” out, so less “work” happening after headers are sent.</li>
<li><a href="https://profiles.wordpress.org/johnbillion/" class="mention"><span class="mentions-prefix">@</span>johnbillion</a>: Maybe, but <code><head></code> still gets filled up by plugins and core doing processing. Would be good to think of what metrics would be useful to see and whether exposing those metrics via this API makes sense.</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: One example would be the autoloaded options query given the recent module proposal to improve that</li>
<li><a href="https://profiles.wordpress.org/johnbillion/" class="mention"><span class="mentions-prefix">@</span>johnbillion</a>: Does FSE actually construct its output before it’s all sent?
<ul>
<li><a href="https://profiles.wordpress.org/aristath/" class="mention"><span class="mentions-prefix">@</span>aristath</a>: Yes, the whole content/template gets rendered internally prior to sending any headers</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/johnbillion/" class="mention"><span class="mentions-prefix">@</span>johnbillion</a>: Like the idea of using the Server-Timing API header, but not sure if it necessarily works for WP</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: Isn’t it worth pursuing to be able to cover anything that happens prior to page output, which is a lot?</li>
<li><a href="https://profiles.wordpress.org/johnbillion/" class="mention"><span class="mentions-prefix">@</span>johnbillion</a>: It could well be, but would be good to see real world examples of what would be good to measure. Output buffering may not be the worst idea if the API is restricted to the plugin; definitely worth investigating.</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> will think about examples</li>
</ul>
</li>
</ul>
<h2>Open floor</h2>
<ul>
<li><a href="https://profiles.wordpress.org/aristath/" class="mention"><span class="mentions-prefix">@</span>aristath</a>: Started porting SQLite as a module: https://github.com/WordPress/performance/pull/547; will discuss further next week</li>
<li><a href="https://profiles.wordpress.org/josklever/" class="mention"><span class="mentions-prefix">@</span>josklever</a>: https://core.trac.wordpress.org/ticket/55344 is related to the performance of the WP dashboard. Resources are loaded for dashboard widgets that are disabled via Screen Options, which can cause unwanted delays or issues for other widgets if there are conflicts. </li>
</ul>
<p><strong>Our next chat will be held on <a href="https://www.timeanddate.com/worldclock/fixedtime.html?iso=20221011T1500"><abbr class="date" title="2022-10-11T15:00:00+00:00">Tuesday, October 11, 2022 at 11am EDT</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><a href="https://make.wordpress.org/core/tag/core-js/" class="tag"><span class="tag-prefix">#</span>core-js</a>, <a href="https://make.wordpress.org/core/tag/core-media/" class="tag"><span class="tag-prefix">#</span>core-media</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>, <a href="https://make.wordpress.org/core/tag/hosting-community/" class="tag"><span class="tag-prefix">#</span>hosting-community</a></p>
<p class="o2-appended-tags"><a href="https://make.wordpress.org/core/tag/meta/" class="tag"><span class="tag-prefix">#</span>meta</a></p>
</div>

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…
WordPress.com has rolled out support for the Model Context Protocol (MCP), allowing AI assistants to…
Ten hosting providers have been certified under the Secure Hosting Alliance’s new Trust Seal program,…
When WP Accessibility Day kicks off next week, someone, somewhere will always be awake. As…