<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-20-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-20-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-20-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-20-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-20-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-20-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-20-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-20-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-20-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-20-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-20-september-2022.png?ssl=1&w=1600&resize=1600&ssl=1 1600w" width="850" height="1314" fifu-data-src="https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/09/performance-team-meeting-summary-20-september-2022.png?ssl=1" class="attachment-post-thumbnail size-post-thumbnail wp-post-image" alt="Performance team meeting summary 20 September 2022" title="Performance team meeting summary 20 September 2022" srcset="https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2022/09/performance-team-meeting-summary-20-september-2022.png?ssl=1 850w, https://www.awordpresscommenter.com/wp-content/uploads/2022/09/performance-team-meeting-summary-20-september-2022-194x300.png 194w, https://www.awordpresscommenter.com/wp-content/uploads/2022/09/performance-team-meeting-summary-20-september-2022-662x1024.png 662w, https://www.awordpresscommenter.com/wp-content/uploads/2022/09/performance-team-meeting-summary-20-september-2022-768x1187.png 768w" sizes="(max-width: 850px) 100vw, 850px" /></div><div>
<p><a href="https://make.wordpress.org/core/2022/09/19/performance-chat-agenda-20-september-2022/">Meeting agenda here</a> and the full chat log is available <a href="https://wordpress.slack.com/archives/C02KGN5K076/p1663686041968009">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>: WebP feature was reverted following Matt’s post. Still trying to determine what a canonical plugin is and if it would work for WebP by default. Still have some fixes to land for 6.1 around image quality when WebPs are output via Performance Lab plugin.</li>
<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>
<ul>
<li>We’ve run out of time to merge before Beta 1 cutoff</li>
<li>Feedback process was a lot slower than we thought it would be</li>
<li>Should continue to work on this and try to get it in for 6.2</li>
<li><a href="https://profiles.wordpress.org/pbearne/" class="mention"><span class="mentions-prefix">@</span>pbearne</a>: Version with theme flag could be merged</li>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a>: Merging now doesn’t feel great as there are still unanswered questions. Code is ready, but not sure what feedback will push this across the line. May need to push early in 6.2 cycle and see what happens.</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: Feels like another merge proposal post with a concrete timeline on a merge date could be good to put out right after 6.1, so people can provide any additional feedback. Should also note the new theme support flag approach.</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>
<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>
</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/mehulkaklotar/" class="mention"><span class="mentions-prefix">@</span>mehulkaklotar</a>: Working on <a href="https://core.trac.wordpress.org/ticket/53450">#53450</a> and it is <a href="https://github.com/WordPress/wordpress-develop/pull/3293">ready for review here</a></li>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a>: Merged:
<ul>
<li><a rel="noreferrer noopener" href="https://core.trac.wordpress.org/ticket/55802" target="_blank">https://core.trac.wordpress.org/ticket/55802</a></li>
<li><a rel="noreferrer noopener" href="https://core.trac.wordpress.org/ticket/55392" target="_blank">https://core.trac.wordpress.org/ticket/55392</a></li>
<li><a rel="noreferrer noopener" href="https://core.trac.wordpress.org/ticket/36905" target="_blank">https://core.trac.wordpress.org/ticket/36905</a></li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a>: Focusing on dev notes next week</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/shetheliving/" class="mention"><span class="mentions-prefix">@</span>shetheliving</a>: <a href="https://core.trac.wordpress.org/ticket/56040">#56040</a> and <a href="https://core.trac.wordpress.org/ticket/56041">#56041</a> (two Site Health checks from Performance Lab) have been merged for 6.1 and dev notes are in progress</li>
<li><a href="https://profiles.wordpress.org/mukesh27/" class="mention"><span class="mentions-prefix">@</span>mukesh27</a>: <a href="https://github.com/WordPress/performance/pull/543">PR #543</a> for adding <code>can-load.php</code> to these Health Checks is ready for review</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>: Reminder about the performance testing environment work started back in March: https://make.wordpress.org/core/2022/03/22/performance-team-meeting-summary-22-march-2022/. This has stalled out since then; if anyone is interested in picking it back up, let us know.</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: Working on a proposal to integrate the <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Server-Timing">Server Timing API</a> into Performance Lab. We have a lack of awareness for how WP is performing server-side and this simple piece of infrastructure would allow us to measure specific features/modules of the plugin to see who they are affecting PHP performance. Should an open an issue this week or next.</li>
<li><a href="https://profiles.wordpress.org/mehulkaklotar/" class="mention"><span class="mentions-prefix">@</span>mehulkaklotar</a>: Continuing to work on a proposal for the plugin performance checker tool</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>N/A</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://github.com/WordPress/performance/issues/531">Bumping minimum requirement to WP 6.0</a> – <a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>
<ul>
<li><a href="https://profiles.wordpress.org/olliejones/" class="mention"><span class="mentions-prefix">@</span>olliejones</a>: <a href="https://wordpress.org/about/stats/">Stats</a> show that 44% of sites are on pre-6.0 versions, does it make sense to leave them behind?</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: Because this is a feature plugin, implications here are quite different from WP overall – see <a href="https://github.com/WordPress/performance/blob/trunk/docs/Version-support-policy.md#wordpress-core-versions">https://github.com/WordPress/performance/blob/trunk/docs/Version-support-policy.md#wordpress-core-versions</a></li>
<li><a href="https://profiles.wordpress.org/masteradhoc/" class="mention"><span class="mentions-prefix">@</span>masteradhoc</a>: Don’t think a lot of users on older versions would be using a feature plugin, seems like a different target group</li>
<li><a href="https://profiles.wordpress.org/markjaquith/" class="mention"><span class="mentions-prefix">@</span>markjaquith</a>: Yeah, suspect that the sites using this plugin are more likely to be using 6.0x and even if not, the goal of the plugin is to move things forward</li>
<li><a href="https://profiles.wordpress.org/robinwpdeveloper/" class="mention"><span class="mentions-prefix">@</span>robinwpdeveloper</a>: Also think this is a good call</li>
<li><strong><a href="https://github.com/WordPress/performance/issues/531#issuecomment-1252550889">Vote here</a></strong> by next Friday, September 30</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: Ran into <a href="https://github.com/WordPress/performance/issues/539">this bug</a> yesterday during the release, which we should fix before the next one</li>
<li><a href="https://profiles.wordpress.org/mukesh27/" class="mention"><span class="mentions-prefix">@</span>mukesh27</a>: Fix broken command for readme changelog <a rel="noreferrer noopener" href="https://github.com/WordPress/performance/pull/542" target="_blank">#542</a> and Add JavaScript coding standard workflow <a rel="noreferrer noopener" href="https://github.com/WordPress/performance/pull/515" target="_blank">#515</a> need review</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> (5 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>
<li><a href="https://github.com/WordPress/performance/issues?q=is%3Aopen+project%3AWordPress%2Fperformance%2F2+label%3A%22Needs+Decision%22+">Needs Decision</a> (1 issue)</li>
</ul>
<h2>Discussion: <a href="https://github.com/WordPress/performance/issues/526">Module proposal: Optimized autoloaded options</a></h2>
<p><a href="https://profiles.wordpress.org/markjaquith/" class="mention"><span class="mentions-prefix">@</span>markjaquith</a></p>
<ul>
<li>Options are autoloaded by default, and most options stay autoloaded even after the plugin or theme that uses them has been deactivated</li>
<li>This autoloading has a cost in terms of the performance of the query that loads autoloaded options, and also because the values of these options are kept in memory</li>
<li>Discussed a lot of ways of addressing this at WordCamp US, and the most promising path that would have the most benefit for the most users (and fits in with this group’s philosophy on focusing on automated fixes instead of introducing new APIs) is to dynamically move options in and out of the “autoload” pool based on usage</li>
<li>Options that are used *and* are not past a certain size cutoff should be autoloaded, but large options and options that are not used, should not be autoloaded</li>
<li>Proof of concept is linked in the ticket and we’re looking for additional feedback</li>
<li><a href="https://profiles.wordpress.org/pbearne/" class="mention"><span class="mentions-prefix">@</span>pbearne</a> already brought up the issue of options that are queried BEFORE a module could start “listening” for them to be called, but there are undoubtedly other gotchas and opportunities here</li>
<li>Especially useful would be help in developing a strategy for measuring the performance of this fix for various sizes of autoloaded options
<ul>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: Could leverage the Server Timing API (noted above) to measure the time the autoloaded options query takes, for example</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/pbearne/" class="mention"><span class="mentions-prefix">@</span>pbearne</a>: Think that both <a href="https://profiles.wordpress.org/markjaquith/" class="mention"><span class="mentions-prefix">@</span>markjaquith</a>‘s and my fixes can be used as they work best for different configurations</li>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a>: Could we start adding a limit to the number of autoloaded options, say 250 rows? Or is the issue size in terms of memory?
<ul>
<li><a href="https://profiles.wordpress.org/pbearne/" class="mention"><span class="mentions-prefix">@</span>pbearne</a>: If we can load just what we need, the SQL time is less</li>
<li><a href="https://profiles.wordpress.org/markjaquith/" class="mention"><span class="mentions-prefix">@</span>markjaquith</a>: We do this to avoid hundreds of individual queries</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/rickjames/" class="mention"><span class="mentions-prefix">@</span>rickjames</a>: Is “autoloading” the thing that PHP can do for include files? I thought it was so slow as to be better to always include everything
<ul>
<li><a href="https://profiles.wordpress.org/markjaquith/" class="mention"><span class="mentions-prefix">@</span>markjaquith</a>: No, this is about quering the <code>wp_options</code> table for <code>autoload = 'yes'</code></li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/rickjames/" class="mention"><span class="mentions-prefix">@</span>rickjames</a>: That gets to the lack of adequate indexes for the <code>wp_options</code> table; a simple change can speed up <code>SELECT</code>s
<ul>
<li><a href="https://profiles.wordpress.org/markjaquith/" class="mention"><span class="mentions-prefix">@</span>markjaquith</a>: There’s already an index, it’s more about the volume of data being transferred</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/eugenemanuilov/" class="mention"><span class="mentions-prefix">@</span>eugenemanuilov</a>: Think we should move from defining which option is autoload-able in the database table to the option registration in WP, so a plugin/theme owner will need to register an option similarly to how settings are registered with <code>register_setting</code> and define whether an option is autoload-able there</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a>: Both proposals at a high level have the idea of querying what is needed, but the newer proposal does it globally while still keeping a single place of storage while the latter was aimed at having different “options lists” per template/page. The latter would be great, but it comes with heavy storage implications, so the newer proposal is probably the best place to start since it has no additional storage implications.</li>
<li><a href="https://profiles.wordpress.org/markjaquith/" class="mention"><span class="mentions-prefix">@</span>markjaquith</a>: Do think that the issue is data, not rows – evicting autoloaded options could help wtih both</li>
<li><a href="https://profiles.wordpress.org/rmccue/" class="mention"><span class="mentions-prefix">@</span>rmccue</a>: Have run into performance problems with pulling autoloaded options from object cache, so agreed that this is an issue</li>
<li><a href="https://profiles.wordpress.org/markjaquith/" class="mention"><span class="mentions-prefix">@</span>markjaquith</a>: Also issue with memcache’s default config being size-limited</li>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a>: Could we use <code>register_settings</code> to define if an option should be autoloaded?
<ul>
<li> <a href="https://profiles.wordpress.org/markjaquith/" class="mention"><span class="mentions-prefix">@</span>markjaquith</a>: Won’t help existing sites</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/rmccue/" class="mention"><span class="mentions-prefix">@</span>rmccue</a>: Core problem is that <code>autoload</code> is true by default, which is what causes issues</li>
<li><a href="https://profiles.wordpress.org/markjaquith/" class="mention"><span class="mentions-prefix">@</span>markjaquith</a>: Two approaches – <a href="https://profiles.wordpress.org/pbearne/" class="mention"><span class="mentions-prefix">@</span>pbearne</a> optimized for “literally just what this page needs”; my POC was for “never autoload things that aren’t used”</li>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a>: So will we store an array of used options in options table?
<ul>
<li><a href="https://profiles.wordpress.org/markjaquith/" class="mention"><span class="mentions-prefix">@</span>markjaquith</a>: Current implementation only stores timestamp of last calibration, but with some additional storage we could minimize dynamic re-adding of autoloaded options</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/rmccue/" class="mention"><span class="mentions-prefix">@</span>rmccue</a>: Autoloading options should minimize DB/cache calls, but not necessarily replace them. The heuristic of what <em>should</em> be autoloaded is key to this proposal.
<ul>
<li><a href="https://profiles.wordpress.org/markjaquith/" class="mention"><span class="mentions-prefix">@</span>markjaquith</a>: To me, it’s “things that are used and aren’t unreasonably large.” Can also honor <code>autoload='no'</code> while not honoring <code>autoload='yes'</code> as chosen by developers.</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a>: Don’t love the idea of storing an array of keys. How do you generate the array? What is the average page load?</li>
<li><a href="https://profiles.wordpress.org/rmccue/" class="mention"><span class="mentions-prefix">@</span>rmccue</a>: To move forward, we need a concrete proposal for how the heuristic works. Will look into the network saturation problems we’ve run into get an idea of what “unreasonable” might lok like.</li>
<li>Next steps: <a href="https://profiles.wordpress.org/markjaquith/" class="mention"><span class="mentions-prefix">@</span>markjaquith</a> will work on detailing the heuristic further in <a href="https://github.com/WordPress/performance/issues/526">#526</a> and when it’s ready, we’ll schedule another discussion for a future chat</li>
</ul>
<p><strong>Our next chat will be held on <a href="https://www.timeanddate.com/worldclock/fixedtime.html?iso=20220927T1500"><abbr class="date" title="2022-09-27T15:00:00+00:00">Tuesday, September 27, 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>

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…