Announcements

Welcome to our new members of #core-performance
WordPress 6.6 RCrelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). 2 happening today

Priority Items

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)
- Future release
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
- Image Prioritizer
- Image Placeholders
- Modern Image Formats
- Optimization Detective
- Performant Translations
- Speculative Loading
Active priority projects

@spacedmonkey flagging this Slack thread This cache is using networknetwork (versus site, blog) wide cache, when the cache should be site wide. @joemcgill was working on this
@adamsilverstein will be running some performance metrics against RC2 when it is out (I missed testing RC1 because I was away)

@adamsilverstein There have been a couple of comments recently requesting support for transforming uploaded PNGs in the Modern Images plugin. We can add this, my biggest question is about the best UIUI User interface. I left a comment asking for feedback – https://github.com/WordPress/performance/issues/371
@adamsilverstein also wanted to call attention to this recent comment from @swissspidy about next steps for performance testing: https://github.com/WordPress/performance/issues/1093#issuecomment-2199717649 – this work is a long term project so its great to see this summary of how we can continue to progress
- @swissspidy Maybe we need to split it up into two issues. As it’s half about improving coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress./GB tests, and half about ecosystem adoption.
- @mukesh27 Hopes soon that we get server-timing data from GB repo also
- @swissspidy It’s actually collected, just not in the dashboard yet (Added in https://github.com/WordPress/gutenberg/pull/61450)

@mukesh27 The Use correct sizes for small images PR is merged. I’m working on PR improved image sizes for left/right/center alignment and it ready for review. Once it’s merged we are ready to release these changes in upcoming plugin release.

@thekt12 I was addressing feedback from Joe and also implementing unit testunit test Code written to test a small piece of code or functionality within a larger application. Everything from themes to WordPress core have a series of unit tests. Also see regression. for https://github.com/WordPress/gutenberg/pull/62794/files ( had some issues with unit test, will connect with Joe to help here)

@adamsilverstein wanted to call attention to this post – https://make.wordpress.org/hosting/2024/06/19/the-image-revolution-avif-and-webp/ from @javiercasares and the hosting team about how hosts can enable AVIF / modern image support for their customers – and why they should consider doing it!
- Only something like 30% of sites are on hosts that currently support AVIF so this is great to see
@pbearne We have a question on autoload and the setting APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways.. “Is there a way to set an option to not autoload if I am using Settings API?” I created a ticketticket Created for both bug reports and feature development on the bug tracker. for this #61522 – Is this something we should look at?
@pbearne And a second opinion on adding a 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. option load to wp-adminadmin (and super admin)
https://github.com/WordPress/wordpress-develop/commit/75d83b656609ad6092146fb7183b58beb859feae Is this the right action? Should we have one for Front-end?