<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/2022/09/performance-team-meeting-summary-6-september-2022.png?ssl=1&w=75&resize=75&ssl=1 75w, https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/09/performance-team-meeting-summary-6-september-2022.png?ssl=1&w=100&resize=100&ssl=1 100w, https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/09/performance-team-meeting-summary-6-september-2022.png?ssl=1&w=150&resize=150&ssl=1 150w, https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/09/performance-team-meeting-summary-6-september-2022.png?ssl=1&w=240&resize=240&ssl=1 240w, https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/09/performance-team-meeting-summary-6-september-2022.png?ssl=1&w=320&resize=320&ssl=1 320w, https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/09/performance-team-meeting-summary-6-september-2022.png?ssl=1&w=500&resize=500&ssl=1 500w, https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/09/performance-team-meeting-summary-6-september-2022.png?ssl=1&w=640&resize=640&ssl=1 640w, https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/09/performance-team-meeting-summary-6-september-2022.png?ssl=1&w=800&resize=800&ssl=1 800w, https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/09/performance-team-meeting-summary-6-september-2022.png?ssl=1&w=1024&resize=1024&ssl=1 1024w, https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/09/performance-team-meeting-summary-6-september-2022.png?ssl=1&w=1280&resize=1280&ssl=1 1280w, https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/09/performance-team-meeting-summary-6-september-2022.png?ssl=1&w=1600&resize=1600&ssl=1 1600w" width="2000" height="2000" fifu-data-src="https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/09/performance-team-meeting-summary-6-september-2022.png?ssl=1" class="attachment-post-thumbnail size-post-thumbnail wp-post-image" alt="Performance team meeting summary 6 September 2022" title="Performance team meeting summary 6 September 2022" srcset="https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/09/performance-team-meeting-summary-6-september-2022.png?ssl=1 2000w, https://www.awordpresscommenter.com/wp-content/uploads/2022/09/performance-team-meeting-summary-6-september-2022-300x300.png 300w, https://www.awordpresscommenter.com/wp-content/uploads/2022/09/performance-team-meeting-summary-6-september-2022-1024x1024.png 1024w, https://www.awordpresscommenter.com/wp-content/uploads/2022/09/performance-team-meeting-summary-6-september-2022-150x150.png 150w, https://www.awordpresscommenter.com/wp-content/uploads/2022/09/performance-team-meeting-summary-6-september-2022-768x768.png 768w, https://www.awordpresscommenter.com/wp-content/uploads/2022/09/performance-team-meeting-summary-6-september-2022-1536x1536.png 1536w" sizes="(max-width: 2000px) 100vw, 2000px" /></div><div>
<p><a href="https://make.wordpress.org/core/2022/09/02/performance-chat-agenda-6-september-2022/">Meeting agenda here</a> and the full chat log is available <a href="https://wordpress.slack.com/archives/C02KGN5K076/p1662476477535219">beginning here on Slack</a>.</p>
<h2>Announcements</h2>
<ul>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: <a href="https://make.wordpress.org/performance/2022/08/09/core-performance-team-rep-nominations/">Team Rep nominations reminder</a></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>: The image team has been focused on addressing feedback on the WebP work and have prepped two follow up commits that address these concerns.
<ul>
<li><a rel="noreferrer noopener" href="https://github.com/WordPress/wordpress-develop/pull/3161" target="_blank">https://github.com/WordPress/wordpress-develop/pull/3161</a> reverts all of the multi-mime changes. Note for contributors to this work who might be disappointed to see it reverted: multi-mime work may return in a future release once we can land async media generation. Even though we aren’t gonna use the approach now, exploring it was important to arriving at the current approach with confidence.
<ul>
<li>This has since been committed in <a href="https://core.trac.wordpress.org/changeset/54085">[54085]</a>.</li>
</ul>
</li>
<li><a rel="noreferrer noopener" href="https://github.com/adamsilverstein/wordpress-develop-fork/pull/35/" target="_blank">https://github.com/adamsilverstein/wordpress-develop-fork/pull/35/</a> introduces the WebP output mapping. It includes some new tests as well as fixing an existing bug and addressing possible generated file naming conflicts.
<ul>
<li>This has since been committed in <a href="https://core.trac.wordpress.org/changeset/54086">[54086]</a>.</li>
</ul>
</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/joegrainger/" class="mention"><span class="mentions-prefix">@</span>joegrainger</a>: Working on <a rel="noreferrer noopener" href="https://github.com/wordpress/performance/issues/24" target="_blank">Regenerate existing images</a> GitHub issues <a href="https://github.com/WordPress/performance/issues/479">#479</a> and <a href="https://github.com/WordPress/performance/issues/480">#480</a></li>
<li><a href="https://profiles.wordpress.org/mukesh27/" class="mention"><span class="mentions-prefix">@</span>mukesh27</a>: Working on Core Trac tickets <a href="https://core.trac.wordpress.org/ticket/16502">#16502</a>, <a href="https://core.trac.wordpress.org/ticket/55227">#55227</a>, <a href="https://core.trac.wordpress.org/ticket/37114">#37114</a></li>
<li><a href="https://profiles.wordpress.org/wpgurudev/" class="mention"><span class="mentions-prefix">@</span>wpgurudev</a>: <a href="https://github.com/WordPress/performance/pull/497">Background job taxonomy PR</a> has been merged; follow up PRs <a href="https://github.com/WordPress/performance/pull/507">#507</a> and <a href="https://github.com/WordPress/performance/pull/512">#512</a> are ready for review</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: Reminder about the <a rel="noreferrer noopener" href="https://github.com/WordPress/performance/issues/477" target="_blank">fetchpriority module</a> which is still looking for an owner. This module was already approved for inclusion in the Performance Lab plugin, and it’s a great opportunity to get started with owning a module – a “good first module” so to speak.</li>
</ul>
<h4 id="feedback-requested">Feedback requested</h4>
<ul>
<li>See above</li>
<li><a style=", sans-serif" href="https://github.com/WordPress/performance/issues?q=is%3Aopen+project%3AWordPress%2Fperformance%2F1+label%3A%22Needs+Discussion%22">Needs Discussion</a><span style="color: initial;, sans-serif"> (9 issues)</span></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 <a href="https://core.trac.wordpress.org/changeset/54080">[54080]</a>
<ul>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: would be curious whether this network options API change has actual performance benefits. It’s certainly great from an API perspective to have that better aligned, but since we’re speaking about performance here, I don’t think we really know how that is going to be impacted</li>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a>: It reduces the number of queries a lot; it also means if a network option does not exist in the database, it does result in another query (with Jetpack installed, 3 less queries per page just from missed network options); To be sure, performance is not the only reason do this. It removed a lot of code and add benefits, like register_meta, default values, new filters etc.</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: Totally makes sense. If you could support that with some benchmarks for the dev note that would be great and also justify it more from a performance perspective</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a>: Core PRs <a href="https://github.com/WordPress/wordpress-develop/pull/3178">#3178</a> and <a href="https://github.com/WordPress/wordpress-develop/pull/2995">#2995</a> are ready for review
<ul>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: Will review <a href="https://github.com/WordPress/wordpress-develop/pull/2995">#2995</a> this week</li>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a>: <a href="https://core.trac.wordpress.org/changeset/54080">[54080]</a> and <a href="https://github.com/WordPress/wordpress-develop/pull/2995">#2995</a> should eventually be covered in one dev note post</li>
</ul>
</li>
</ul>
<h4 id="feedback-requested-2">Feedback requested</h4>
<ul>
<li><a style=", sans-serif" href="https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F6+">Needs Discussion</a><span style="color: initial;, sans-serif"> (3 issues)</span></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/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: Site Health check for full page cache was merged last week in <a href="https://core.trac.wordpress.org/changeset/54043">[54043]</a>
<ul>
<li>There were some follow up quirks to address with some test issues related to some environment edge cases, but those have all been addressed shortly after (see <a href="https://core.trac.wordpress.org/ticket/56041">#56041</a> for more details)</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> (9 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>: working on proposal for Plugin Check plugin, getting ready for reviews from the team</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><a href="https://profiles.wordpress.org/pushpakpop/" class="mention"><span class="mentions-prefix">@</span>pushpakpop</a>: working on research and exploration related to <a href="https://github.com/WordPress/performance/issues/168">JavaScript orchestration</a></li>
</ul>
<h4 id="feedback-requested-3">Feedback requested</h4>
<ul>
<li><a style=", sans-serif" href="https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F3+">Needs Discussion</a><span style="color: initial;, sans-serif"> (2 issues)</span></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>: Performance Lab plugin PR <a href="https://github.com/WordPress/performance/pull/468">#468</a> needs reviews from people experienced with JavaScript tooling, WebPack etc.</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: Plugin PRs <a href="https://github.com/WordPress/performance/issues/388">#388</a> and <a href="https://github.com/WordPress/performance/issues/510">#510</a> were completed last week, which are some great little fixes</li>
</ul>
<h4 id="feedback-requested-1">Feedback requested</h4>
<ul>
<li><a style=", sans-serif" href="https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F2+">Needs Discussion</a><span style="color: initial;, sans-serif"> (5 issues)</span></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>Open Floor</h2>
<ul>
<li><a href="https://profiles.wordpress.org/pbearne/" class="mention"><span class="mentions-prefix">@</span>pbearne</a>: <a href="https://make.wordpress.org/core/2022/07/21/proposal-add-a-dominant-color-background-to-images/">Dominant Color proposal</a> feedback discussion and next steps
<ul>
<li><a href="https://profiles.wordpress.org/pbearne/" class="mention"><span class="mentions-prefix">@</span>pbearne</a>: The feeling is that this is good idea and we would want it, but the theme should control turning it on; the code to store the dominant color values on image upload into the image meta should run regardless (e.g. that data could also be used in the media library in core)
<ul>
<li>We would hide the dominant color for the front-end behind a theme support flag like <code>add_theme_support( 'dominant-color' );</code></li>
<li>This approach can be seen in core PR <a href="https://github.com/WordPress/wordpress-develop/pull/3164">#3164</a></li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: I think it makes sense to have the CSS aspect of it controlled by themes. However there is considerable other feedback on the post which focuses on the performance aspect of this feature</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: IMO we should center the conversation around that first, as there was some concern on the post what the real performance impact is (whether it’s perceived or “actual” performance); FWIW I don’t think the single lab test that was conducted and posted on the GitHub issue serves as a meaningful indicator for performance. PageSpeed Insights lab test results vary greatly, even between runs of the same page, so the fact that it was slightly better in one run doesn’t mean anything – which is a shame really, but that’s the case
<ul>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a>: I am not sure I agree with your judgement on this one</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: We would need to do much larger scale tests across a variety of sites to assess a performance impact. Metrics like bytes throughput, database queries etc. are stable, but for things like CWV they vary greatly between each run; If you run let’s say 10 tests, each time before, the other time after, and it’s consistently better with the feature, then there may be something to it. But a single PSI test doesn’t mean anything in terms of CWV and dynamic metrics like FCP, TTFB etc., that’s unfortunately the truth</li>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a>: But this change has never been about actual performance improvements, perceived performance was always the goal. Could you spend sometime profiling performance further for us and see what results you get?
<ul>
<li>A <a href="https://docs.google.com/document/d/1zuiDUiJFqIBAepSx9VHXUJ4-lk4_wiQNcLD9ItvIiag/edit">follow up analysis</a> with more sample data sets has since been conducted, indicating there is no clear performance impact from the feature, so we probably need to focus on perceived performance indeed</li>
</ul>
</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/adamsilverstein/" class="mention"><span class="mentions-prefix">@</span>adamsilverstein</a>: the discussion on the ticket centers around perceived performance: based on the approach, I doubt there is much actual performance benefit as measured in the lab. Maybe one thing that is missing from the proposal or the comment thread replies is research/data around the benefits background color provides for perceived load time. Part of the issue may be a lack of prior research?
<ul>
<li><a href="https://profiles.wordpress.org/adamsilverstein/" class="mention"><span class="mentions-prefix">@</span>adamsilverstein</a>: the original idea was a bit different (low quality image placeholders, not dominant color) and had even more tradeoffs/cost to use. the commonality is they help users have a sense of what is going to fill an image space before the image loads</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: I think that’s what is a potential problem here: Most articles that we’ve dug up so far focus on perceived performance of regular images with LQIP. But what we’re doing now is “less” than LQIP, so it’s further away from looking like the final image. I know there were technical complexities that make us chose that path, but I think we need to consider that</li>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a>: Dominate color has other benefits and can also be used in styling, contrasting overlays / text for example</li>
<li><a href="https://profiles.wordpress.org/adamsilverstein/" class="mention"><span class="mentions-prefix">@</span>adamsilverstein</a>: lack of existing research may be because dominant color is relatively unique/new approach? were there existing examples of it we looked at? maybe we need to conduct some research?
<ul>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a>: Unsplash uses blurhash and fallback to dominant color, Google Images also uses dominant color</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/masteradhoc/" class="mention"><span class="mentions-prefix">@</span>masteradhoc</a>: I feel like the way that Google uses it for images is really a good way and can improve the visible speed for the user. I would support to have this into core. Frontend is controlled by themes and wp-admin by default looks quite a good way for me</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/pbearne/" class="mention"><span class="mentions-prefix">@</span>pbearne</a>: Do we feel that adding dominant color to the media library what a good improvement in itself (e.g. as an improvement to wp-admin)?
<ul>
<li><a href="https://profiles.wordpress.org/adamsilverstein/" class="mention"><span class="mentions-prefix">@</span>adamsilverstein</a>: might be worth bringing up at a media meeting, I like the idea but have some concerns: how would library look with only some images having dominant color generated? is it worth the effort of generating the color on upload only for the media library?</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: a potential concern is that this runs additional processing on image upload. I don’t know how much it impacts upload, and whether it does increase the chance to time out or run into memory limit, but that is quite sensitive. Especially at this point as we are just going to revert the multi MIME image generation for exactly that reason; I think starting with the media library may be a good approach if this additional processing is not a concern</li>
<li><a href="https://profiles.wordpress.org/pbearne/" class="mention"><span class="mentions-prefix">@</span>pbearne</a>: it’s actually quite lite on upload compared to the rest of processing</li>
</ul>
</li>
</ul>
</li>
</ul>
<p><strong>Our next chat will be held on <a href="https://www.timeanddate.com/worldclock/fixedtime.html?iso=20220913T1500"><abbr class="date" title="2022-09-13T15:00:00+00:00">Tuesday, September 13, 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…