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 Beta 2 performance results [GitHub issue]
Priority Items
- WordPress performance Trac tickets
- Current release (WP 6.6) [Trac tickets]
- 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)
- Performance Lab plugin and the following 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 trunk, 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 tag doesn’t replicate all of the picture element’s sourcing features: https://github.com/WordPress/performance/issues/1312
- @joemcgill Does adding
fetchprioritydirectly 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
typenot themedia.- Unless, would a browser skip requesting a preload link for an image when it has a
typethat is not supported? I didn’t think it did. But I’ll need to check that
- Unless, would a browser skip requesting a preload link for an image when it has a
- @joemcgill Does adding
- @westonruter Related to Image Prioritizer, I’ve opened several other issues for enhancement ideas on top of Optimization Detective.
Active Priority Projects
Improving the calculation of image size attributes
- @mukesh27 We have some good progress on this project, The Use correct sizes for small images PR is ready for final review and merge. Once it merge i will working on blocked PR improved image
sizesfor left/right/center alignment.- @joemcgill I just saw your update to the PR and will review again today. I think we’re on good track to have a first version ready for the next PL release date
Optimized Autoloaded Options
- The dev note 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 block 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 Core 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 filter, 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 ticket 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.
nnnn
Announcements
nnnn
- n
- Welcome to our new members of #core-performance nnnn
- Early WordPress 6.6u00a0Betau00a02 performance results [GitHub issue] n
nnnn
Priority Items
nnnn
- n
- WordPress performance Trac ticketsn
- n
- Current release (WP 6.6) [Trac tickets] n
nnnn - Performance Lab plugin (and other performance plugins)n
- n
- Auto-Sizes for Lazy-Loaded Images nnnn
- Embed Optimizer nnnn
- Fetchpriority nnnn
- Image Placeholders nnnn
- Modern Image Formats nnnn
- Optimization Detective nnnn
- Performant Translations nnnn
- Speculative Loading n
nnnn - Active priority projects n
nnnn
WordPress Performance Trac Tickets
nnnn
- n
- Last 2 performance tickets for 6.6 #59595 (merged) and #59600 (punted) n
nnnn
Performance Lab Plugin (and other Performance Plugins)
nnnn
- n
- Performance Lab plugin and the following performance plugins:nn n
nnnn
- n
- @thelovekesh added testing steps onu00a0https://github.com/WordPress/performance/pull/1247u00a0which is ongoing PR for adding Web Worker Offloading plugin. As per last discussion on merging it in trunk, this PR is ready for that nnnn
- @westonruter hopes to pick up Web Worker Offloading next week nnnn
- @mukesh27 theu00a0Extend core's Autoloaded Options Site Health test if present (in WP 6.6)u00a0is 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 contributenn nnnn - @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 tag doesn't replicate all of the picture element's sourcing features:u00a0https://github.com/WordPress/performance/issues/1312n
- n
- @joemcgill Does addingu00a0
fetchpriorityu00a0directly to the image not work in this case? nnnn - @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. nnnn
- @joemcgill I would think that picture would make that easier, because each source would have it's own media attribute nnnn
- @westonruter Otherwise, it adds preload links for the LCP element in each breakpoint. The problem with the picture element is theu00a0
typeu00a0not theu00a0media.n- n
- Unless, would a browser skip requesting a preload link for an image when it has au00a0
typeu00a0that is not supported? I didn't think it did. But I'll need to check that n
n - Unless, would a browser skip requesting a preload link for an image when it has au00a0
nnnn - @joemcgill Does addingu00a0
- @westonruter Related to Image Prioritizer, I've openedu00a0several other issuesu00a0for enhancement ideas on top of Optimization Detective. n
nnnn
Active Priority Projects
nnnn
Improving the calculation of image size attributes
nnnn
- n
- @mukesh27 We have some good progress on this project, Theu00a0Use correct sizes for small imagesu00a0PR is ready for final review and merge. Once it merge i will working on blocked PRu00a0improved imageu00a0
sizesu00a0for left/right/center alignment.n- n
- @joemcgill I just saw your update to the PR and will review again today. I think we're on good track to have a first version ready for the next PL release date n
n
nnnn
Optimized Autoloaded Options
nnnn
- n
- The dev note has now been psoted https://make.wordpress.org/core/2024/06/18/options-api-disabling-autoload-for-large-options/ n
nnnn
Improved template loading
nnnn
- n
- @thekt12 I am working on review from @joemcgill here -
https://github.com/WordPress/gutenberg/pull/62794/files nnnn - @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 block 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 Core repo has made executing and testing changes reliably pretty challenging. I openedu00a0this issueu00a0to discuss how we can improve this process going forward. I'd be happy for folks here to give feedback.n
- n
- In terms of ouru00a0tracking 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. n
n
nnnn
Open Floor
nnnn
- n
- @joemcgill FYI: there's a new channel,u00a0#pluginreview-pluginchecku00a0to have discussions related to maintaining the Plugin Check plugin that we helped build.n
- n
- @thekt12 mentioned most PRs show errors nnnn
- @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.u00a0 n
nnnn - @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?n
- n
- @joemcgill WP already supportsu00a0uploadingu00a0those versions, and gives site owners the ability to convert uploaded files to those formats using a filter, but there are currently no plans to make either the "default" format that is used for the intermediate sizes that WP creates. nnnn
- @westonruter And merging picture element support will require a lot of testing and there will certainly be many theme and plugin compatibility issues nnnn
- @joemcgill #55443 is probably the best ticket to revisit for this n
n
nnnn
Our next chat will be held on [time]Tuesday, July 2, 2024 at 15:00 UTC[/time] in the #core-performance channel in Slack.
nnnn
nnn#core-performance, #performance, #performance-chat, #summary","contentFiltered":"Meeting agenda here and the full chat log is available beginning here on Slack.
nnnn
Announcements
nnnn
- n
- Welcome to our new members ofu00a0#core-performance nnnn
- Early WordPress 6.6u00a0Betau00a02 performance results [GitHub issue] n
nnnn
Priority Items
nnnn
- n
- WordPress performance Trac ticketsn
- n
- Current release (WP 6.6) [Trac tickets] n
nnnn - Performance Lab plugin (and other performance plugins)n
- n
- Auto-Sizes for Lazy-Loaded Images nnnn
- Embed Optimizer nnnn
- Fetchpriority nnnn
- Image Placeholders nnnn
- Modern Image Formats nnnn
- Optimization Detective nnnn
- Performant Translations nnnn
- Speculative Loading n
nnnn - Active priority projects n
nnnn
WordPress Performance Trac Tickets
nnnn
nnnn
Performance Lab Plugin (and other Performance Plugins)
nnnn
- n
- Performance Lab plugin and the following performance plugins:nn n
nnnn
- n
- @thelovekesh added testing steps onu00a0https://github.com/WordPress/performance/pull/1247u00a0which is ongoing PR for adding Web Worker Offloading plugin. As per last discussion on merging it in trunk, this PR is ready for that nnnn
- @westonruter hopes to pick up Web Worker Offloading next week nnnn
- @mukesh27 theu00a0Extend coreu2019s Autoloaded Options Site Health test if present (in WP 6.6)u00a0is 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 contributenn nnnn - @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 tag doesnu2019t replicate all of the picture elementu2019s sourcing features:u00a0https://github.com/WordPress/performance/issues/1312n
- n
- @joemcgill Does addingu00a0
fetchpriorityu00a0directly to the image not work in this case? nnnn - @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. nnnn
- @joemcgill I would think that picture would make that easier, because each source would have itu2019s own media attribute nnnn
- @westonruter Otherwise, it adds preload links for the LCP element in each breakpoint. The problem with the picture element is theu00a0
typeu00a0not theu00a0media.n- n
- Unless, would a browser skip requesting a preload link for an image when it has au00a0
typeu00a0that is not supported? I didnu2019t think it did. But Iu2019ll need to check that n
n - Unless, would a browser skip requesting a preload link for an image when it has au00a0
nnnn - @joemcgill Does addingu00a0
- @westonruter Related to Image Prioritizer, Iu2019ve openedu00a0several other issuesu00a0for enhancement ideas on top of Optimization Detective. n
nnnn
Active Priority Projects
nnnn
Improving the calculation of image size attributes
nnnn
- n
- @mukesh27 We have some good progress on this project, Theu00a0Use correct sizes for small imagesu00a0PR is ready for final review and merge. Once it merge i will working on blocked PRu00a0improved imageu00a0
sizesu00a0for left/right/center alignment.n- n
- @joemcgill I just saw your update to the PR and will review again today. I think weu2019re on good track to have a first version ready for the next PL release date n
n
nnnn
Optimized Autoloaded Options
nnnn
- n
- The dev note has now been psoted https://make.wordpress.org/core/2024/06/18/options-api-disabling-autoload-for-large-options/ n
nnnn
Improved template loading
nnnn
- n
- @thekt12 I am working on review from @joemcgill here u2013
https://github.com/WordPress/gutenberg/pull/62794/files nnnn - @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 block 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 Core repo has made executing and testing changes reliably pretty challenging. I openedu00a0this issueu00a0to discuss how we can improve this process going forward. Iu2019d be happy for folks here to give feedback.n
- n
- In terms of ouru00a0tracking issue, Iu2019ll 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. n
n
nnnn
Open Floor
nnnn
- n
- @joemcgill FYI: thereu2019s a new channel,u00a0#pluginreview-pluginchecku00a0to have discussions related to maintaining the Plugin Check plugin that we helped build.n
- n
- @thekt12 mentioned most PRs show errors nnnn
- @joemcgill Iu2019ve 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.u00a0 n
nnnn - @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?n
- n
- @joemcgill WP already supportsu00a0uploadingu00a0those versions, and gives site owners the ability to convert uploaded files to those formats using a filter, but there are currently no plans to make either the u201cdefaultu201d format that is used for the intermediate sizes that WP creates. nnnn
- @westonruter And merging picture element support will require a lot of testing and there will certainly be many theme and plugin compatibility issues nnnn
- @joemcgill #55443 is probably the best ticket to revisit for this n
n
nnnn
Our next chat will be held on Tuesday, July 2, 2024 at 15:00 UTC in the #core-performance channel in Slack.
nnnn
n","permalink":"https://make.wordpress.org/core/2024/06/26/performance-chat-summary-25-june-2024/","unixtime":1719398313,"unixtimeModified":1719398313,"entryHeaderMeta":"","linkPages":"","footerEntryMeta":"","tagsRaw":"core-performance, performance, performance-chat, summary","tagsArray":[{"label":"core-performance","count":85,"link":"https://make.wordpress.org/core/tag/core-performance/"},{"label":"performance","count":325,"link":"https://make.wordpress.org/core/tag/performance/"},{"label":"performance-chat","count":262,"link":"https://make.wordpress.org/core/tag/performance-chat/"},{"label":"summary","count":841,"link":"https://make.wordpress.org/core/tag/summary/"}],"loginRedirectURL":"https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2024%2F06%2F26%2Fperformance-chat-summary-25-june-2024%2F&locale=en_US","hasPrevPost":false,"prevPostTitle":"","prevPostURL":"","hasNextPost":false,"nextPostTitle":"","nextPostURL":"","commentsOpen":true,"is_xpost":false,"editURL":null,"postActions":"","comments":[{"type":"comment","id":"46858","postID":"114052","postTitleRaw":"Performance Chat Summary: 25 June 2024","cssClasses":"comment byuser comment-author-westonruter odd alt thread-odd thread-alt depth-1","parentID":"0","contentRaw":"
Fetchpriority
nn@clarkeemily I think what was meant here is the Image Prioritizer plugin. The Fetchpriority plugin is obsolete and closed.","contentFiltered":"
Fetchpriority
n
@clarkeemily I think what was meant here is the Image Prioritizer plugin. The Fetchpriority plugin is obsolete and closed.
n","permalink":"https://make.wordpress.org/core/2024/06/26/performance-chat-summary-25-june-2024/#comment-46858","unixtime":1719422555,"loginRedirectURL":"https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2024%2F06%2F26%2Fperformance-chat-summary-25-june-2024%2F%23comment-46858&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":1,"commentDropdownActions":"","commentFooterActions":"
","commentTrashedActions":"","mentions":["clarkeemily"],"mentionContext":"","commentCreated":"1719422555","hasChildren":false,"userLogin":"westonruter","userNicename":"westonruter"}],"postFormat":"standard","postMeta":{"isSticky":false},"postTerms":{"category":[{"label":"Meetings","count":1387,"link":"https://make.wordpress.org/core/category/meetings/"}],"post_tag":[{"label":"core-performance","count":85,"link":"https://make.wordpress.org/core/tag/core-performance/"},{"label":"performance","count":325,"link":"https://make.wordpress.org/core/tag/performance/"},{"label":"performance-chat","count":262,"link":"https://make.wordpress.org/core/tag/performance-chat/"},{"label":"summary","count":841,"link":"https://make.wordpress.org/core/tag/summary/"}],"post_format":[]},"pluginData":[],"isPage":false,"mentions":["thelovekesh","westonruter","mukesh27","joemcgill","thekt12"],"mentionContext":"","isTrashed":false,"userLogin":"clarkeemily","userNicename":"clarkeemily"}]
