Closed felixarntz closed 8 months ago
Sharing a few projects here which are already clear as they're a continuation of efforts already started:
sizes
attribute
sizes="auto"
where relevant and supported: Lazy-loaded images don’t need sizes attributes to be calculated prior to layout, and can be made more accurate.Reduce CLS by reserving space for variable-height elements while loading
Improves metric: CLS
cc @thelovekesh
Thanks for kicking this off, @felixarntz. Some additional ideas I'd like to see us explore next year:
Improvements to page caching strategies Focuses on metric: TTFB
get_template_part()
(example code is in https://github.com/johnbillion/extended-template-parts) and introducing enhancements that make block template and template parts more cacheable.API for registering scripts on a Web Worker Focuses on metric: LCP|INP
Improve Core Automated Performance Tests Focuses on: infrastructure
Eliminating jQuery usage from the frontend in WordPress default themes Focuses on metric: LCP
Client-side image compression
Focuses on metric: LCP
Interactivity API Adoption
Focuses on metric: INP
Scale reusable testing environment usage
Not focusing on a particular metric.
oEmbed Lazy Loading Focuses on metric: INP, LCP
AVIF support Focuses on metric: LCP
<picture>
element support for adoptionSpeculative prerendering and prefetching Focuses on metric: LCP, INP
link
tags approach for prefetching and prerenderingInteractivity API enhancements Focuses on metric: INP
Thank you everyone for contributing ideas! 🙌
Closing this issue now as initially announced. We'll start a draft for the roadmap very soon and will share for public review. Let's aim to get it published before end of the month.
It's time to work on the WordPress Performance Team roadmap for 2024! 🎉
The team roadmap should capture what we want to primarily focus on this year. This issue is an open call to share your personal or collective priorities for the year, so that we can aggregate them in an eventual public roadmap to share with the wider WordPress community.
This roadmap should eventually be published as the new "Roadmap" menu item on https://make.wordpress.org/performance/, replacing the current 2023 roadmap. (The 2023 roadmap won't be completely removed, it'll only be removed from the menu.)
For reference, see the similar issue that led to the 2023 roadmap.
If you're actively contributing to the WordPress Performance Team or plan to do so this year, please share your priorities for 2024 as a comment on this issue!
For every priority that you would like to focus on this year, preferably include the following:
Last but not least, note that this roadmap is of course not set in stone. Priorities can shift over the year, and the roadmap should remain a living document over time that we keep updating as needed. So this initial set of priorities for 2024 acts as a solid starting point.
This issue will remain open for project priorities until January 5, 2024. Afterwards, the public roadmap will be drafted based on the priorities shared here. The roadmap draft will be shared for review in a future #core-performance chat, to allow for feedback and iterations before it is published.