Meeting agenda here and the full chat log is available and the full chat log is available beginning here on Slack.

Announcements

• Welcome to our new members of #core-performance
• WordPress 6.6 betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 is today
• Performance lab 3.2.0 release scheduled for June 6

Priority Items

Structure:

• WordPress performance TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets
  • Current release (WP 6.6)
• Performance Lab pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party (and other performance plugins)
  • Auto-Sizes for Lazy-Loaded Images
  • Embed Optimizer
  • Fetchpriority
  • Image Placeholders
  • Modern Image Formats
  • Optimization Detective
  • Performant Translations
  • Speculative Loading
• Active priority projects

WordPress Performance Trac Tickets

• WordPress 6.6 enhancement tickets
  • #61276 was just re-opened but the enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. is committed
  • @joemcgill The new Site Health check for large autoloaded options is committed https://core.trac.wordpress.org/changeset/58332. I also committed the caching improvements for generating global styles for blocks in https://core.trac.wordpress.org/changeset/58334
  • @spacedmonkey has several issues he would like reviewing #53167 #59595 and #59871
    • @joemcgill I committed the caching improvements that we’ve been working on and left a review on your PR, @spacedmonkey I think we could still consider making your proposed change, but the impact will be much smaller and should most likely start with a GB PR
  • @spacedmonkey I think that #53167 & #59871 are ready for commit IMO but we missed the cut off there
• There are 9 performance tickets for 6.6, all of which are marked as bugs
  • @joemcgill The main one that I want a 2nd opinion on is #55996 and specifically this PR, which fixes a bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. that the .org team ran into when trying to apply filters to blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. content at the template level instead of the block level.

Performance Lab Plugin (and other Performance Plugins)

• Performance Lab plugin and the following performance plugins:
  • Auto-sizes for Lazy-loaded Images
  • Embed Optimizer
  • Fetchpriority
  • Image Placeholders
  • Modern Image Formats
  • Optimization Detective (Developer Preview)
  • Performant Translations
  • Speculative Loading

• @westonruter Milestones for the plugins: https://github.com/WordPress/performance/milestones
  • There’s one issue left for Modern Image Formats currently with @adamsilverstein : https://github.com/WordPress/performance/issues/1258
  • Otherwise, for Performance Lab itself (and metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. items for the repo as a whole) there are currently 8 open issues/PRs: https://github.com/WordPress/performance/milestone/47
• @westonruter For 3.2.0 we’ll at least have the Upgrade Notice – I think we should discuss more what should be done there, whether we bring back the adminadmin (and super admin) pointer whenever there is a big new feature or if something else less obtrusive is warranted
• @ashwinparthasarathi hoping to work on this https://github.com/WordPress/performance/issues/1239
  But it will probably make it in the next release.
• @joemcgill states 1136 the main one that we need to try to get wrapped up
  • @stellastopfer Yes, we should get the last icon and the export today EOD
  • Active discussion on the ticketticket Created for both bug reports and feature development on the bug tracker. regarding the assets and agreed to go with just the “P” for now as we are short on time
• Agreed to puntpunt Contributors sometimes use the verb "punt" when talking about a ticket. This means it is being pushed out to a future release. This typically occurs for lower priority tickets near the end of the release cycle that don't "make the cut." In this is colloquial usage of the word, it means to delay or equivocate. (It also describes a play in American football where a team essentially passes up on an opportunity, hoping to put themselves in a better position later to try again.) the onboarding experience issue https://github.com/WordPress/performance/issues/1032
• The last issue is https://github.com/WordPress/performance/issues/715 but it seems it won’t take much to get it over the finish line, with input from @adamsilverstein
• @westonruter I submitted the Image Prioritizer plugin for review with the plugin review team. This includes the fetchpriority=high for the LCP image, including when there are different LCP image elements for different breakpoints. It also now includes applying correct lazy-loading so that images that appear in the initial viewport in any breakpoint never get lazy-loading whereas images outside the initial viewport in any breakpoint always get lazy-loading.

Active Priority Projects

Improving the calculation of image size attributes

• @mukesh27 has been working on improved image sizes algorithm
  • PR that ready for review:
    • PR #1250 – Initial implementation of improved image sizes algorithm
    • PR #1252 – Use correct sizes for small images

Web Worker Offloading

• @thelovekesh I have added the testing steps on – https://github.com/WordPress/performance/pull/1247

Optimized Autoloaded Options

• @joemcgill now that we’ve included the Site Health check, I think we can update the dev notedev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. draft and then close out that project. I’ve been waiting on the doc release leads to get a process setup that we can add our dev note to.
  • @pbearne to create a draft post here

Open Floor

• @pbearne I am working on https://core.trac.wordpress.org/ticket/36477
  to try an make PNG resizes are always smaller 
• @thelovekesh discuss about WP_DEBUG in test cases – ongoing discussion from here in Slack

Our next chat will be held on Tuesday, June 11, 2024 at 15:00 UTC in the #core-performance channel in Slack.

#core-performance, #performance, #performance-chat, #summary