Tag Archives: core-performance

Emily Clarke 10:15 am on July 24, 2024
Tags: core-performance, , ,   

Performance Chat Summary: 23 July 2024

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

Announcements

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 (6.7)
    • Future releases
  • 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)
    • Enhanced Responsive Images
    • Embed Optimizer
    • Image Prioritizer
    • Image Placeholders
    • Modern Image Formats
    • Optimization Detective
    • Performant Translations
    • Speculative Loading
  • Active priority projects

WordPress Performance Trac Tickets

  • There are currently 16 performance issues in 6.7
  • @pbearne I need input on this ticketticket Created for both bug reports and feature development on the bug tracker. as I made opinionated changes as to which option should not be autoloaded #61103
    • @joemcgill I plan on digging into that PR to give you feedback, but am going to be out on holiday for a bit. If anyone else has time to look at this in the mean time, please do so.
    • @mukesh27 I will take a look this week
    • @joemcgill One thing that will be good to understand, is that if we aren’t autoloading options that are only needed in the adminadmin (and super admin), how do we make sure the editor experience isn’t negatively affected. I think you’re already planning on priming all of those options in the admin, but would be good to get some performance measurements of the before/after of both the front end and admin.
    • @pbearne I have a patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. to load the admin options in back on wp_int

Performance Lab Plugin (and other Performance Plugins)

  • @mukesh27 I have been working on PRs that ready for review:
    • Performance Lab plugin:
      • PR #1374 – Autoloaded Options Health Check: Disabled options reappear in Site Health after external update
    • Modern Image Formats plugin:
      • PR #1354 – Picture element: The accurate sizes improvement for images not working
  • @westonruter It seems like we’re getting increasing reports of issues with image generation in Modern Image Formats
    • In GitHub and support forums
    • @westonruter Might be related to the issue of AVIF generation taking a very long time sometimes?
    • @joemcgill Ah, I do remember cases a long time ago where image generation could take longer than the max PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher timeout on some hosts and result in the attachment data being created in the DB while the actual image generation failed. I wonder if something like that is happening?
    • @westonruter That’s being discussed here: https://github.com/WordPress/performance/issues/371
    • @adamsilverstein this could also be a support detection issue, (where format support for AVIF gives a false negative or positive), interesting they say it falls back to WebP
    • @westonruter I wonder if the AVIF generation should be moved a background process? Use the JPEG immediately upon upload and then use the AVIF once it is available
    • @adamsilverstein we already have a way of generating images in multiple passes, but it needs to be able to process one image completely before the timeout
    • @joemcgill That’s a good idea. There is prior art for generating missing intermediate sizes that could be referenced.
    • @pbearne Idea: we need a long process control for wp-admin that can be used for any task that takes a long time (images gen, post delete, etc.)
    • @adamsilverstein https://github.com/WordPress/performance/issues/490 was part of that previous effort, there is also a trac ticket
    • @westonruter I thought that was primarily for regenerating the entire media library
    • @adamsilverstein yes, but part of that was the ability to regenerate images in i the background #6814 16 year old ticket
    • @joemcgill It’s not totally accurate anymore, after #40439
    • @adamsilverstein true, we partially solved the issue with that, as long as the user agent remains present to trigger the retries
    • @joemcgill I’ve played with using WP_Cron for this a looooooong time ago, but that can cause failures to affect end-user front-end requests, which we’d want to avoid

Active Priority Projects

Improving the calculation of image size attributes

  • @mukesh27 For Improving the calculation of image size attributes i have been working on:
    • PR #1382 – Update wp_calculate_image_sizes to Reflect Changes in sizes attribute
    • Issue #1389 – Accurate sizes improvement didn’t account for the disable filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. for sizes
    • @joemcgill I’m reviewing those this morning

Plugin Check

Open Floor

  • WordPress 6.6 performance analysis
    • @adamsilverstein Yes… I have been working on a post for 6.6 performance changes and will share a draft here for feedback soon!
    • one challenge has been identifying the source of the slight regressions we see in 6.6 (the numbers haven’t changed much since I shared results here for an 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). a few weeks ago)
    • part of the challenges is tracking changes that originate in the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ project and are then merged over to coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. our automated tests haven’t highlighted issues, nor are the Gutenberg performance tests
    • some ideas: it might be because the regressions are very small and spread out over a number of commits, or it might be related to the difference in how we are doing automated tests. in case, it points to an area we can improve
    • @joemcgill Agreed. There are a number of improvements that we could make to our CI infrastructure in both the GB repo and in Core that would help. We’ve already got https://github.com/WordPress/performance/issues/1380 as a place to discuss a set of improvements we want to focus on next. I’d love to see more discussion there so we can define and prioritize some next steps.
    • One of the questions that I still have is whether the benchmarks that we have been taking at the end of each release are providing us with useful info, or if they are obscuring what is really happening in the field.  @adamsilverstein I’m curious if we could get some HTTPArchive data after 6.6 has been out a while to see if our lab benchmarks relate to real user data or not.
    • @adamsilverstein that is a good point, I’m happy to work on that. we should have enough data in a few months.
    • some performance improvements we are adding will really only become apparent in the field data, and our automated testing can’t really measure those

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

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

Emily Clarke 4:00 pm on July 16, 2024
Tags: core-performance, , ,   

Performance Chat Summary: 16 July 2024

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

Announcements

  • Welcome to our new members of #core-performance
  • Version 3.3.0 of 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 was released yesterday
  • WordPress 6.6 release happening today Tue Jul 16

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
    • Future release
  • Performance Lab plugin (and other performance plugins)
    • Enhanced Responsive Images
    • Embed Optimizer
    • Image Prioritizer
    • Image Placeholders
    • Modern Image Formats
    • Optimization Detective
    • Performant Translations
    • Speculative Loading
  • Active priority projects

WordPress Performance Trac Tickets

  • @joemcgill For visibility: on Friday, I reverted r58334 due to a late reported 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. related to the caching global styles for blocks. This was done as part of #59595. I have a PR that I need to refresh that fixes the issue and reinstates the cache, which I hope to have included in 6.6.1.
  • There are currently 12 performance issues in 6.7 which will be reviewed in tomorrow’s bug scrub

Performance Lab Plugin (and other Performance Plugins)

  • @mukesh27 I have also opened an issue for the Picture element: The accurate sizes improvement for images not working #1349. The new changes from the Enhanced Responsive Images (formerly known as auto-sizes) plugin are not working
    • @westonruter let’s prioritize fixing those and push out short-cycle standalone releases
    • @mukesh27 confirmed it’s Modern Image formats plugin causing the bug and will share more details on issue

Active Priority Projects

Improving the calculation of image size attributes

  • @joemcgill now that we’ve released the first version of Auto-sizes Enhanced Responsive Images that includes those improvements, I think @mukesh27 and I will need to update the overview issue with the main goals for the next priority features. At the same time, we’ll continually iterate on issues that come up during testing.

Improved template loading

  • @joemcgill There were a couple of remaining tasks open on the Improved template loading epic, but at this point, we’ve accomplished the majority of what was originally planned and the remaining items really are iterative improvements to the WP_Theme_JSON system that really could be tracked as part of ongoing CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. work, or as a collaborative issue in the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ repo, so I’m going to close up the related tickets and close that issue.
  • This section will be dropped from the agenda moving forwards

Plugin Check

Open Floor

  • @swissspidy I opened a proposal a while ago for a new PL plugin: https://github.com/WordPress/performance/issues/1324 The idea is to take data collected by Optimization Detective and display them in a nice little dashboard. Not sure yet how useful that would be, but thought I’d share it 🙂
    • @joemcgill I love this idea and wonder if there is an opportunity to surface other kinds of performance data on that dashboard, like CWV scores if available, etc. Though I really like the different use cases we’re finding for the Optimization Detective 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.. “CWV scores if available” meaning from the CrUX API
      • @westonruter I suppose to compare with the CWV metrics from actual visitors as measured by Optimization Detective?
    • @westonruter Yeah, actually storing the CWV metrics in the URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org Metrics custom post typeCustom Post Type WordPress can hold and display many different types of content. A single item of such a content is generally called a post, although post is also a specific post type. Custom Post Types gives your site the ability to have templated posts, to simplify the concept. would be a key part of this. Currently we only store which element was the LCP, not what the LCP metric is.
    • @joemcgill Unless we’re collecting metrics from every visit, I think we’d need to somehow be clear about how those CWV metrics are representative of real users, and not a full picture.
    • @westonruter Yeah. It would be a sampling, for sure. But so is CrUX. Although surely CrUX sampling would be higher, assuming you get enough traffic to qualify
    • @joemcgill It is, but CrUX is a larger sample size than what we’re collecting with OD. The real value is that this would allow sites to get URL level data which can be more difficult for site owners to get from CrUX
    • @swissspidy There was also a proposal to use a separate storage mechanism (e.g. a custom table or CPT) that allows storing the data for more than 30 days
    • @swissspidy Precisely. And also without waiting for next month’s data to arrive etc. You could more quickly see the performance impact of changes made to the site.
    • @joemcgill Rather than making this a separate plugin, I really think we should consider adding this type of data to Performance Lab and integrate OD when available (or bundle the API into that plugin too). Now that all of our Performance features are unbundled into standalone plugins, I think there’s an opportunity for PL to add more value as a tool for collecting and surfacing performance metrics and opportunities for improvement to site owners.
  • @swissspidy Another quick update from my side: I had some very productive discussions with some Gutenberg folks about client-side media processing and they shared some valuable feedback about separation of concerns. I am currently refactoring my Media Experiments plugin based on that feedback, hoping to have something that can be merged into Gutenberg afterwards. The tracking issue on the Gutenberg repo is this one: https://github.com/WordPress/gutenberg/issues/61447

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

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

Emily Clarke 4:04 pm on July 9, 2024
Tags: core-performance, , ,   

Performance Chat Summary: 9 July 2024

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

Announcements

  • Welcome to our new members of #core-performance
  • The next Performance Lab release will take place on Mon Jul 15, see https://github.com/WordPress/performance/milestones
  • 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). 3 happening today, ahead of the main release scheduled for Tue Jul 16

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

WordPress Performance Trac Tickets

Performance Lab Plugin (and other Performance Plugins)

  • @westonruter For Embed Optimizer, this PR will be ready for review this morning. I just need to add the description to detail the changes: https://github.com/WordPress/performance/pull/1302
    • This includes fundamental enhancements to Optimization Detective to make it much more powerful to be able to make optimizations to a document (e.g. what Embed Optimizer requires)
  • @westonruter I think the plugin with the most need is Modern Image Formats as there are a couple bugs needing to be fixed: https://github.com/WordPress/performance/milestone/59
  • @mukesh27 the updated sizes feature from auto-sizes is ready for this release, some final PRs ready for review:
    • PR #1335 – Plugin rename
    • PR #1329 – Merge feature branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch". to trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision.
  • @joemcgill there’s also a proposed name change for the Auto-Sizes plugin

Active Priority Projects

Improving the calculation of image size attributes

  • Discussed above

Improved template loading

  • @joemcgill The template loading work is mainly wrapped up in 6.6. There are a few minor follow-up issues that I think we’ll continue to track but I’ll work on summarizing next steps and closing up those GH issues.
    • The two things that are on my mind in the short term are:
      • Supporting the Plugin Check project as the Plugin Review team are working to get it integrated into their systems.
      • Improving our performance metrics for both CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and GB.

Plugin Check

  • @joemcgill For Plugin Check, I’d like to get more eyes on this conversation., which may end up being a requirement for them to do the integration

Open Floor

  • @mukesh27 Do we have any open issue for Improving our performance metrics for both Core and GB 
  • @joemcgill raised that @swissspidy mentioned one last week that included both misc improvements and shared performance tooling and asked about whether we should separate these issues https://github.com/WordPress/performance/issues/1093
    • I do think it would serve us well to put some focus on this early in the 6.7 cycle so we can more easily pinpoint which commits have server timing performance implications. That’s been a big challenge the past 2 releases. (In the GB repo specifically)
  • @pbearne I am thinking of suggesting that WP has an infrastructure release where we update/re-organize the PHPUnit tests etc. as without core committers actively making the changes it will never get done. The performance testing could be part of this
    • @joemcgill I would suggest proposing the infrastructure changes you have in mind and whether those become a release focus or not, could be secondary.

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

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

Emily Clarke 3:55 pm on July 2, 2024
Tags: core-performance, , ,   

Performance Chat Summary: 2 July 2024

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

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

WordPress Performance Trac Tickets

  • @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)

Performance Lab Plugin (and other Performance Plugins)

Active Priority Projects

Improving the calculation of image size attributes

Improved template loading

  • @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)

Open Floor

  • @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?

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

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

Emily Clarke 10:38 am on June 26, 2024
Tags: core-performance, , ,   

Performance Chat Summary: 25 June 2024

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

Announcements

  • Welcome to our new members of #core-performance
  • Early 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. 2 performance results [GitHub issue]

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
  • 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

  • Last 2 performance tickets for 6.6 #59595 (merged) and #59600 (punted)

Performance Lab Plugin (and other Performance Plugins)

  • @thelovekesh added testing steps on https://github.com/WordPress/performance/pull/1247 which is ongoing PR for adding Web Worker Offloading plugin. As per last discussion on merging it in trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision., this PR is ready for that
  • @westonruter hopes to pick up Web Worker Offloading next week
  • @mukesh27 the Extend core’s Autoloaded Options Site Health test if present (in WP 6.6) is merged
    @mukesh27 opened a couple issues related to Modern Images Formats and the implementation of the picture element. Those are up for grabs for anyone wanting to contribute
  • @westonruter Related to that, I found a downside to using the picture element in the first place, in that it is not currently possible to add fetchpriority=high preload links for picture elements since the link tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) doesn’t replicate all of the picture element’s sourcing features: https://github.com/WordPress/performance/issues/1312
    • @joemcgill Does adding fetchpriority directly to the image not work in this case?
    • @westonruter Yes that does, but the problem occurs when there are varying LCP elements for different breakpoints. So Image Prioritizer will need to explicitly avoid adding a preload link when the LCP element is a picture.
    • @joemcgill I would think that picture would make that easier, because each source would have it’s own media attribute
    • @westonruter Otherwise, it adds preload links for the LCP element in each breakpoint. The problem with the picture element is the type not the media.
      • Unless, would a browser skip requesting a preload link for an image when it has a type that is not supported? I didn’t think it did. But I’ll need to check that
  • @westonruter Related to Image Prioritizer, I’ve opened several other issues for enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. ideas on top of Optimization Detective.

Active Priority Projects

Improving the calculation of image size attributes

Optimized Autoloaded Options

  • 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. has now been psoted https://make.wordpress.org/core/2024/06/18/options-api-disabling-autoload-for-large-options/

Improved template loading

  • @thekt12 I am working on review from @joemcgill here –
    https://github.com/WordPress/gutenberg/pull/62794/files
  • @joemcgill #59600 and #57789 have a lot of overlap and the former is mostly irrelevant at this point. We fixed the biggest problem #59600 with 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. patterns, but still have some things we wanted to progress in 6.7 for the WP_Theme_JSON system. However, the maintenance of that system between the GB repo on the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. repo has made executing and testing changes reliably pretty challenging. I opened this issue to discuss how we can improve this process going forward. I’d be happy for folks here to give feedback.
    • In terms of our tracking issue, I’ll post an update in light of the final 6.6 changes we were able to make and update any remaining tasks we want to pursue.

Open Floor

  • @joemcgill FYI: there’s a new channel, #pluginreview-plugincheck to have discussions related to maintaining the Plugin Check plugin that we helped build.
    • @thekt12 mentioned most PRs show errors
    • @joemcgill I’ve seen that on occasion as well, but not causing any merge checks to fail, and not consistently with the same message. Could be flaky e2e tests. 
  • @mukesh27 As the Performance Lab plugin has added support for WebP, AVIF, and Picture elements, what is the tentative WordPress version we are targeting for merging these features?
    • @joemcgill WP already supports uploading those versions, and gives site owners the ability to convert uploaded files to those formats using a filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output., but there are currently no plans to make either the “default” format that is used for the intermediate sizes that WP creates.
    • @westonruter And merging picture element support will require a lot of testing and there will certainly be many theme and plugin compatibility issues
    • @joemcgill #55443 is probably the best ticketticket Created for both bug reports and feature development on the bug tracker. to revisit for this

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

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

Emily Clarke 9:17 pm on June 18, 2024
Tags: core-performance, , ,   

Performance Chat Summary: 18 June 2024

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

Announcements

  • Welcome to our new members of #core-performance
  • Early 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. 2 performance results [GitHub issue]
  • WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe highlights post [link]
  • Thanks to all who joined Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. at WordCamp Europe! [accomplishments]

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)
  • 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

Performance Lab Plugin (and other Performance Plugins)

  • @joemcgill Chrome 126 went stable last week, which includes support for auto-sizes, so I’d encourage more folks to start testing the Auto-sizes plugin and provide feedback
  • @mukesh27 For PL plugin PR #1298 is ready for review
  • @westonruter I’ve been working on adding integration between Embed Optimizer and Optimization Detective, allowing the collected URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org metrics to inform whether an embed should be lazy-loaded and if not (when in the initial viewport) to add preconnect links. This has exposed some limitations with the current implementation so I’ve been refactoring how the tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) processor is leveraged which will make it much more powerful for extensions to apply optimizations. Currently still a draft but should be ready for review this week: https://github.com/WordPress/performance/pull/1302
  • @westonruter for Speculative Loading, there’s a PR now to implement support for the search form, but this currently requires a hack which has been reported upstream to Chromium to allow speculative loading prerenders for GET forms: https://github.com/WordPress/performance/pull/1297
  • @westonruter ready for review is another PHPStan PR to apply strict rules: https://github.com/WordPress/performance/pull/1241

Active Priority Projects

Improving the calculation of image size attributes

  • @mukesh27 For accurate sizes, we used a different approach for updating the sizes. The PR #1252 is ready with those changes. If anyone has a moment, please take a look

Optimized Autoloaded Options

  • @joemcgill our only remaining task is to publish 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.. I saw that @adamsilverstein provided some minor feedback, which @pbearne has already addressed. I think it’s probably read to go

Improved template loading

  • @thekt12 I have addressed feedback from @joemcgill –  https://github.com/WordPress/wordpress-develop/pull/6781. I still need to move this to GB as this is GB first issue
  • @joemcgill one of the things that I’ve been thinking about, related to these types of caches—where we’re trying to add persistence to all sites via the use of transients—is what is the best way to avoid the extra DB query that gets made when you have a transient with a TTL value. It may be worth updating the transient 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. to allow for autoloading to be specified when setting the transient.

Open Floor

  • @joemcgill reminder about the new project board that we’ve got set up here. I’m curious if anyone is still using the older project boards on a regular basis. If not, I think we can remove them.

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

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

Emily Clarke 4:05 pm on June 11, 2024
Tags: core-performance, , ,   

Performance Chat Summary: 11 June 2024

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

Announcements

  • Welcome to our new members of #core-performance
  • 3.1.0 launched on June 6 to include new performance 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 assets
  • Early 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 performance results [GitHub issue]
    • Early investigations did NOT show a regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. at all, but instead shows that 6.6 Beta 1 is improved from 6.5.3 (conversation to be continued on the GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ issue)
  • Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. at WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe, Turin, Italy on Thursday June 13

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)
  • Performance Lab plugin (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

Performance Lab Plugin (and other Performance Plugins)

  • @mukesh27 PR that ready for review:
    • PR #1298 – Audit Autoloaded Options Site Health should extend CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.’s check if available
  • @joemcgill Also worth noting that Chrome 126 is scheduled to ship today with auto-sizes support turned on, so we should be able to get better testing feedback soon from folks using that feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins..
    • @westonruter opened https://github.com/WordPress/performance/pull/1296 in order to do a quick minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. of Optimization Detective and could use reviews

Active Priority Projects

Improving the calculation of image size attributes

  • @mukesh27 has been working on improved image sizes algorithm
    • PRs merged:
      • PR #1250 – Initial implementation of improved image sizes algorithm
    • PRs ready for review:
      • PR #1290 – improved image sizes for left/right alignment
      • PR #1252 – Use correct sizes for small images

Optimized Autoloaded Options

Improved template loading

  • @thekt12 I have raised a new 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. #61405 (with a POC that currently breaks some tests ). Same pattern was also observed in WP_Theme_JSON_Data::$theme_json, but I am not sure of the performance impact it will have. PR#6781 will address the remainder of #57789 and #59600 ; estimated to give at least 3% improvement.

Open Floor

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

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

Emily Clarke 4:35 pm on June 4, 2024
Tags: core-performance, , ,   

Performance Chat Summary: 4 June 2024

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)

  • @westonruter Milestones for the plugins: https://github.com/WordPress/performance/milestones
  • @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

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.

Open Floor

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

Emily Clarke 11:45 am on May 29, 2024
Tags: core-performance, , ,   

Performance Chat Summary: 28 May 2024

The full chat log is available beginning here on Slack.

Announcements

  • Welcome to our new members of #core-performance
  • Performance Lab 3.2.0 release date is June 6, 2024
  • 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 scheduled for Tuesday June 4

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
    • Improve template loading
    • INP research opportunities
    • Improving the calculation of image size attributes
    • Optimized autoloaded options

WordPress Performance Trac Tickets

  • WordPress 6.6 enhancement tickets:
    • @adamsilverstein to test #53167 and aim to get it in beta 1
    • For #57789 @thekt12 added persistent cache to  get_theme_data . Yet to run it with existing 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. and take performance result. He will add a PR today for testing add it today for testing. Currently he is adding some last changes to https://github.com/WordPress/wordpress-develop/pull/6392 which will fix some unit test
    • @thekt12 has updated #59595 with https://github.com/WordPress/wordpress-develop/pull/6392 with the review changes. Suggest changes weren’t working fully as $metadata[‘name’] was not present for all the block_nodes so updated it even further. Also identified repetitive code in old function which is fixed
    • @mukesh27 has #61276 ready for review, it has lots of testing on this one
      • @johnbillion I think we already have a few site health checks that aren’t particularly actionable by an end user, so this shouldn’t be a blockerblocker A bug which is so severe that it blocks a release., but definitely something to consider
      • @joemcgill In the Performance Lab plugin, we include a way for end users to review the specific options that are being flagged and allow them to turn off autoloading for them. Still unsure if that functionality is ready for all end users, but the fact that this site health check can be enhanced with specific additional details is a nice starting point. We can always adjust the copy during betas as well. I think we’ll likely get more feedback once 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. for #42441 is published. Pairing the health check with this improvement seems like a nice affordance

Performance Lab Plugin (and other Performance Plugins)

  • @westonruter suggested moving the 3.2.0 performance lab plugin release date to June 6 to accommodate the newest designs for the new icons
  • @stellastopfer provided an update on the new Performance Lab icon set, and advised that option 2 is being voted the best set of icons
  • @westonruter On this note… For the onboarding experience I think timing is great to coincide with WP 6.5.4 to introduce redirection to the Performance screen when activating the plugin
  • Decision agreed to move Performance Lab plugin 3.2.0 release until after the WordPress 6.5.4 release on June 5
  • We have the first Performance Lab repo 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. scrub on Wednesday May 29
  • @westonruter Modern Image formats is close to wrapping a couple of PRs for merge – this ticket in particular by @adamsilverstein
  • @westonruter is etting very close to finishing the Optimization Detective refactor/extraction into Image Prioritizer dependent plugin

Active Priority Projects

  • @stellastopfer We now also have one project board that should cover all current and upcoming work. The board is still a bit of a WIP, but should get its final shape over the course of the next couple of weeks.
    • Hopefully, it will serve our team just as well as some of you lurkers out there, so you can get an idea on features added to upcoming releases, bug fixes and other improvements, but also discuss and contribute where you see an opportunity to do so.
    • The first next step would be to add all of the issues that are in progress, but aren’t there. Then we will triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. and align on labels. I think there are some we can do without and others we can simplify.
    • If you click on the arrow in the tab, and go to Slice by > Milestone, it will open a sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme.. There you can choose the milestone you want to see card for and they will filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. on the right.
    • Only one milestone at a time. We could create a filter by due date. That would cover multiple
  • @joemcgill suggested we’ll probably need some follow-up or some documentation on how we want to use the board (best practices, tips, that sort of thing), but this is an amazing start and should help us organize visibility of our work much better.

Improving the calculation of image size attributes

  • @mukesh27 has been working on improved image sizes algorithm. And asked @joemcgill to please review it when you have moment.
    • PR that ready for review:
      • PR #1250 – Initial implementation of improved image sizes algorithm
      • PR #1252 – Use correct sizes for small images

Open Floor

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

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

Emily Clarke 4:01 pm on May 14, 2024
Tags: core-performance, , ,   

Performance Chat Summary: 7 May 2024

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

Announcements

  • Welcome to our new members of #core-performance
  • Performance lab 3.1.0 release scheduled for May 20

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)
  • Active priority projects
    • Improve template loading
    • INP research opportunities
    • Improving the calculation of image size attributes
    • Optimized autoloaded options

WordPress Performance Trac Tickets

  • For WordPress 6.6:
    • @adamsilverstein only 14 tickets milestoned for 6.6 in the performance focus,  the 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. scrubs have been effective at keeping tickets moving
    • @spacedmonkey I would consider adding my ticketticket Created for both bug reports and feature development on the bug tracker. for loading multiple networknetwork (versus site, blog) options at once. I am hoping to get #61053 into this release.
      • @pbearne That would a good add, and we can it to 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.
    • @westonruter Happy to share that post embeds will now get lazy-loaded in 6.6 where previously they were excluded. This was committed yesterday https://core.trac.wordpress.org/changeset/58143

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

  • Modern images: @adamsilverstein for modern images work has continued on adding AVIF support, that is very close to ready – https://github.com/WordPress/performance/pull/1176
  • @ashwinparthasarathi Worked on a couple of features and PRs are underway,
  • @benoitfouc AVIF is now mainly supported, i’m agree with this proposition
    • @adamsilverstein supported in all browsers, however only ~30% of WordPress sites have the server support they need to upload AVIFs (and generate srcset images)
    • @benoitfouc is there a way to control this support on the plugin? Using WebP by default when the server do not support AVIF
    • @westonruter Yes, that’s how it works. And there is a user option to decide which format when AVIF is available
  • @adamsilverstein that would be my preference. then, what happens if users are already outputting WebP, does that change automatically to AVIF when they upgrade the plugin, or do they need to go in and change the output setting?
    • One thing we are trying to decide on that PR is haw to handle the default settings – especially for users who upgrade from the current version
  • @westonruter Would anyone be explicitly wanting WebP instead of AVIF, I guess the question is. Adam suggested doing a major version bump from 1.x to 2 as a signal for this significant change. Might be sufficient as a way to alert users that their attention may be needed. Otherwise, I guess an adminadmin (and super admin) pointer could be added, but that seems noisy. Maybe add an Upgrade Notice in the readme as well?
    • Agreement reached:
    • Going back up to @ashwinparthasarathi PR https://github.com/WordPress/performance/pull/1208 to improve visibility of the features’ Settings screens, take a look at the last comment on the PR. How about adding a link to the settings in the activation notice? “Feature activated. Review settings.”
    • Where settings is a link to the relevant settings screen. A settings link also appears with each feature once activated, but the thinking is that the user may not notice this appear all of a sudden
  • @ashwinparthasarathi yes, it makes sense, and I will make the changes to include it in the Activation notice. I also thought that your earlier idea to make those settings links more visible is a good one. I think if we could make it stand out, it’ll work.
  • @westonruter for Speculative Loading: Whether we should go ahead and prevent speculative loading for logged-in users (and when PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher sessions are being used): https://github.com/WordPress/performance/pull/1178
    • After thinking about it some more, I wonder if it may be premature to add this as we haven’t had any reports in the wild of this being a problem. The one user who reported it did so as part of an overall set of suggestions.
    • Perhaps we sit on this awhile longer to bake
    • There could also be a new setting we could add for turning off speculative loading for logged-in users. But ideally we’d be able to make a decision and not add to the user’s set of tasks. Although there are currently pretty low-level settings for prefetch vs prerender already, so maybe this isn’t a big deal for a feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins. as we figure out what makes sense for coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..
    • Oh, I stand corrected, one user did report wanting to be able to disable speculative loading this in the support forumSupport Forum WordPress Support Forums is a place to go for help and conversations around using WordPress. Also the place to go to report issues that are caused by errors with the WordPress code and implementations.: https://wordpress.org/support/topic/sl-lsc/#post-17699897

Active Priority Projects

Improve template loading

  • @thekt12 Last week I worked on feedback from #59595 and also worked on it’s unittest, just a few more checks and I should be able to give it for review today. I’ll resume back #57789

INP research opportunities

Improving the calculation of image size attributes

Optimized autoloaded options

  • No updates this week

Open Floor

  • @benoitfouc i want to know if somebody are interesting about working on this PR : https://github.com/WordPress/performance/issues/371 This PR make sens, and is on the same way that the new version of Modern Images Formats plugin
  • @clarkeemily I think last week one suggestion was made to have a bug scrub specifically for the Performance Lab plugin – wondered if folks were in favor of this in principle, then we can perhaps work to define the scheduling etc later

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

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