Performance Chat Summary: 18 June 2024

Announcements

Table of Contents

@joemcgill keeping an eye on #61451 which is one potential place where there is still an opportunity to improve performance
@joemcgill also waiting feedback on https://github.com/WordPress/wordpress-develop/pull/6626 in order to close #61112

@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 URL 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 tag 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

@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

@joemcgill our only remaining task is to publish the dev note. I saw that @adamsilverstein provided some minor feedback, which @pbearne has already addressed. I think it’s probably read to go

@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 API to allow for autoloading to be specified when setting the transient.

@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.
- @stellastopfer will help remove these if everyone agrees