<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/2022/09/performance-team-meeting-summary-13-september-2022.png?ssl=1&w=75&resize=75&ssl=1 75w, https://i0.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/09/performance-team-meeting-summary-13-september-2022.png?ssl=1&w=100&resize=100&ssl=1 100w, https://i0.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/09/performance-team-meeting-summary-13-september-2022.png?ssl=1&w=150&resize=150&ssl=1 150w, https://i0.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/09/performance-team-meeting-summary-13-september-2022.png?ssl=1&w=240&resize=240&ssl=1 240w, https://i0.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/09/performance-team-meeting-summary-13-september-2022.png?ssl=1&w=320&resize=320&ssl=1 320w, https://i0.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/09/performance-team-meeting-summary-13-september-2022.png?ssl=1&w=500&resize=500&ssl=1 500w, https://i0.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/09/performance-team-meeting-summary-13-september-2022.png?ssl=1&w=640&resize=640&ssl=1 640w, https://i0.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/09/performance-team-meeting-summary-13-september-2022.png?ssl=1&w=800&resize=800&ssl=1 800w, https://i0.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/09/performance-team-meeting-summary-13-september-2022.png?ssl=1&w=1024&resize=1024&ssl=1 1024w, https://i0.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/09/performance-team-meeting-summary-13-september-2022.png?ssl=1&w=1280&resize=1280&ssl=1 1280w, https://i0.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/09/performance-team-meeting-summary-13-september-2022.png?ssl=1&w=1600&resize=1600&ssl=1 1600w" width="2000" height="2000" fifu-data-src="https://i0.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/09/performance-team-meeting-summary-13-september-2022.png?ssl=1" class="attachment-post-thumbnail size-post-thumbnail wp-post-image" alt="Performance team meeting summary 13 September 2022" title="Performance team meeting summary 13 September 2022" srcset="https://i0.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/09/performance-team-meeting-summary-13-september-2022.png?ssl=1 2000w, https://www.awordpresscommenter.com/wp-content/uploads/2022/09/performance-team-meeting-summary-13-september-2022-300x300.png 300w, https://www.awordpresscommenter.com/wp-content/uploads/2022/09/performance-team-meeting-summary-13-september-2022-1024x1024.png 1024w, https://www.awordpresscommenter.com/wp-content/uploads/2022/09/performance-team-meeting-summary-13-september-2022-150x150.png 150w, https://www.awordpresscommenter.com/wp-content/uploads/2022/09/performance-team-meeting-summary-13-september-2022-768x768.png 768w, https://www.awordpresscommenter.com/wp-content/uploads/2022/09/performance-team-meeting-summary-13-september-2022-1536x1536.png 1536w" sizes="(max-width: 2000px) 100vw, 2000px" /></div><div>
<p><a href="https://make.wordpress.org/core/2022/09/08/performance-chat-agenda-13-september-2022/">Meeting agenda here</a> and the full chat log is available <a href="https://wordpress.slack.com/archives/C02KGN5K076/p1663081287900709">beginning here on Slack</a>.</p>
<h2>Announcements</h2>
<ul>
<li><a href="https://profiles.wordpress.org/clarkeemily/" class="mention"><span class="mentions-prefix">@</span>clarkeemily</a>: <a href="https://make.wordpress.org/performance/2022/08/09/core-performance-team-rep-nominations/">Team Rep nominations reminder</a>
<ul>
<li>Announced <a href="https://profiles.wordpress.org/shetheliving/" class="mention"><span class="mentions-prefix">@</span>shetheliving</a> and <a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> as Team Reps as they were the only two nominations and two reps are needed</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>: In the last week the image team finished addressing the WebP feedback and switching back to the original single mime output approach. We also started work on controlling output per size and adding support to <code>add_image_size</code>.</li>
<li><a href="https://profiles.wordpress.org/adamsilverstein/" class="mention"><span class="mentions-prefix">@</span>adamsilverstein</a>: Yesterday during contributor day at WCUS, Matt posted on (not shipping) WebP in 6.1 which was a surprise to the team. We are currently working with the release leads to better understand his concerns and develop a path forward. I want to acknowledge this is a blow for everyone who worked on the feature (myself included) and at the same time I’d like to encourage us to focus on how we can move forward given the current position. Are there concerns we can address? Does a canonical plugin make sense?
<ul>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a>: I think it makes sense to move the webp functionality found in the performance plugin to it’s own plugin. That way it will be easier to get users to test it and get feedback on just this functionality.</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: I think if it remains a “feature project”, it makes sense to remain in the Performance Lab plugin – we don’t know if moving it out of it would get us more testers (especially since the Performance Lab plugin has 10k+ installs which is a lot for a feature plugin). If the path of a “canonical plugin” should be pursued, then of course we would need to take it out, but then the nature of the project would also change.</li>
<li><a href="https://profiles.wordpress.org/kadamwhite/" class="mention"><span class="mentions-prefix">@</span>kadamwhite</a>: Speaking from REST experience, the times we flirted with making add-on plugins to test specific routes, they never got the traction the main plugin did.</li>
<li><a href="https://profiles.wordpress.org/adamsilverstein/" class="mention"><span class="mentions-prefix">@</span>adamsilverstein</a>: My main concern about a feature like WebP being in a canonical plugin is how users would know they should enable it.
<ul>
<li><a href="https://profiles.wordpress.org/eatingrules/" class="mention"><span class="mentions-prefix">@</span>eatingrules</a>: FWIW, millions of users are finding and installing image optimization plugins in the repo. Smush has over 1 million installs. EWWW Image Optimizer has 1+ million. Imagify has 600k. Shortpixel, 300k. WebP Express, 200k. Robin image optimizer, 100k.</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/kadamwhite/" class="mention"><span class="mentions-prefix">@</span>kadamwhite</a>: Something I remember coming up when we initially introduced responsive images was server / cdn costs, because certain configuration could cause higher-res versions to be downloaded. Does WebP’s size benefit translate to any hosting benefit?, in terms of money?
<ul>
<li><a href="https://profiles.wordpress.org/adamsilverstein/" class="mention"><span class="mentions-prefix">@</span>adamsilverstein</a>: with the current implementation yes! lower storage requirements since WebPs are smaller, and lower bandwidth requirements as well, though slightly more processor effort to generate</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: I think this discussion is very valuable, however we won’t be able to make any decision here today since we’re still waiting for more information. Hopefully we’ll know more by next week. We definitely need to continue this discussion once we do.</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/pbearne/" class="mention"><span class="mentions-prefix">@</span>pbearne</a> worked on <a href="https://github.com/WordPress/performance/pull/528">https://github.com/WordPress/performance/pull/528</a> to add a <code>fetchpriority</code> module to the Performance Lab plugin; will be a co-owner of the module</li>
<li><a href="https://profiles.wordpress.org/wpgurudev/" class="mention"><span class="mentions-prefix">@</span>wpgurudev</a> has been working through the feedback and comments on background job class for image regeneration: <a href="https://github.com/WordPress/performance/pull/507">https://github.com/WordPress/performance/pull/507</a>, this is again up for review; next PR for review will be background process runner <a href="https://github.com/WordPress/performance/pull/512">https://github.com/WordPress/performance/pull/512</a>, this makes use of job instance, so will be reviewed and merged post the above PR merge</li>
</ul>
<h4 id="feedback-requested">Feedback requested</h4>
<ul>
<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+Dev%22">Needs Dev</a> (1 issue)</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> (1 issue)</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> got 3 commits into core (<a href="https://core.trac.wordpress.org/changeset/54080">[54080]</a>, <a href="https://core.trac.wordpress.org/changeset/54098">[54098]</a>, <a href="https://core.trac.wordpress.org/changeset/54099">[54099]</a>) and worked on PR <a href="https://github.com/WordPress/wordpress-develop/pull/3178">#3178</a></li>
<li><a href="https://profiles.wordpress.org/kadamwhite/" class="mention"><span class="mentions-prefix">@</span>kadamwhite</a>: We’ve been doing some work on sites with very high comment volume around understanding the comment caching in core, because we began to actually see bottlenecks in cache performance with churn from comment cache eviction. Is anybody in this group specifically knowledgable about how WP handles comment caching?
<ul>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a> worked on this in the past</li>
</ul>
</li>
</ul>
<h4 id="feedback-requested-2">Feedback requested</h4>
<ul>
<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><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a>: <a href="https://profiles.wordpress.org/furi3r/" class="mention"><span class="mentions-prefix">@</span>furi3r</a> has updated <a href="https://docs.google.com/document/d/11ekflhRTZjxwuXBBDBcvvrRNDL0Gy2NobsuKrHSXdb8/edit#">draft</a> for new cache Site Health checks dev note, ready for another review
<ul>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> will have another look</li>
</ul>
</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/mehulkaklotar/" class="mention"><span class="mentions-prefix">@</span>mehulkaklotar</a> is working on proposal for Plugin Check plugin. Right now, we would include minimal checks in the plugin that is included in the <a href="https://github.com/WordPress/wporg-code-analysis/tree/trunk/MinimalPluginStandard">wporg-code-analysis</a> and check the error log for any warnings, notices when plugin activated. I would love to hear suggestions about Github action that we will provide as an action that developers can use into their plugin repo.</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%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><a href="https://profiles.wordpress.org/mukesh27/" class="mention"><span class="mentions-prefix">@</span>mukesh27</a> worked on JavaScript coding standard workflow <a href="https://github.com/WordPress/performance/pull/515">#515</a>. Please review and share feedback.</li>
</ul>
<h4 id="feedback-requested-3">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%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>N/A</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%2F2">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%2F2">Needs Review</a> (3 issues)</li>
</ul>
<h2>Open Floor</h2>
<ul>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a>: Next steps for <a href="https://make.wordpress.org/core/2022/07/21/proposal-add-a-dominant-color-background-to-images/">Dominant color feature</a> (continued from last week)
<ul>
<li><a href="https://profiles.wordpress.org/pbearne/" class="mention"><span class="mentions-prefix">@</span>pbearne</a>: Are we all happy to merge the theme flag version?</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: I think there were still some open questions and research to do on the perceived performance improvement</li>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a>: What are those questions? It comes down to the fact, we can’t move the performance benefit when it comes to metrics. But the benefit is more about what the users sees. That benefit is not an easy one to prove with numbers. It is more like a feeling of speed.</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: Agreed, it’s certainly more challenging to prove anything regarding perceived performance. I don’t know but there is research on how “good” the LQIP perceived performance benefit is – so at least in theory there is something to unpack there for the dominant color perceived performance benefit as well. Maybe it’s a bit of a stretch to have us to UX research around that, which may be the only thing we could do in terms of research. At this point, I’m not opposed to it landing in core, but I’m also not sold on it.</li>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a>: I consider dominant color like other meta data we generate, so why not this? It could be helpful for theme developers.</li>
</ul>
</li>
</ul>
<p><strong>Our next chat will be held on <a href="https://www.timeanddate.com/worldclock/fixedtime.html?iso=20220920T1500"><abbr class="date" title="2022-09-20T15:00:00+00:00">Tuesday, September 20, 2022 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/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>

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…
The full chat log is available beginning here on Slack. WordPress Performance Trac tickets @westonruter…