Title: Performance team meeting summary – November, 16 2021 Author: Justin Ahinon Published: November 18, 2021 Last modified: December 1, 2021 --- [ ](https://profiles.wordpress.org/justinahinon/) [Justin Ahinon](https://profiles.wordpress.org/justinahinon/) 12:01 pm _on_ November 18, 2021 Tags: [meeting ( 405 )](https://make.wordpress.org/core/tag/meeting/), [performance ( 419 )](https://make.wordpress.org/core/tag/performance/), [performance-chat ( 345 )](https://make.wordpress.org/core/tag/performance-chat/), [summary ( 981 )](https://make.wordpress.org/core/tag/summary/)    # Performance team meeting summary – November, 16 2021 [This is the agenda for the meeting](https://make.wordpress.org/core/2021/11/15/performance-chat-agenda-november-16-2021/). You can read the logs [here on Slack](https://wordpress.slack.com/archives/C02KGN5K076/p1637074847326700). ## Focus group projects discussion [@audrasjb](https://profiles.wordpress.org/audrasjb/) made an update about the progress for the **Site Health** group. [Here’s the document](https://docs.google.com/document/d/1RAqArmU4yQwyXI_IrOCYwsuj7kTE1c0i2u8SVQcc72I/edit?usp=sharing) with details about two projects for the focus group. The next step for this group is to use the next Site Health meeting time slot (November 22, 2021, at 16:00 UTC) to discuss these 2 projects. [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/) shared that the **Images** focus group has [a long list of ideas](https://docs.google.com/document/d/1KKlJ3_sZA_AWVXOba2NbuxhS9nz0M5gx52utab7WUt4). The next task for this group would be to describe these ideas based on the template; listing their impact, complexity etc. and then based on that prioritizing the work of the group. ## Should the performance team have its own Make blogblog (versus network, site)? [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/) raised this question about having a Make blog for the Performance team. [@flixos90](https://profiles.wordpress.org/flixos90/) mentioned that performance encompasses all areas of WordPress. And that having a dedicated performance blog is likely less impactful than posting in the area(s) where a certain topic mostly applies to – a dedicated performance blog may end up in some sort of silo, where only people who are into it anyway become aware of it. ## Weekly meeting time The team has voted to move the meeting time one hour later, at 4:00 PM UTC. The new meeting times are also updated [here](https://make.wordpress.org/meetings/#performance). ## Object caching focus group The object caching focus now has 7 contributor votes on the [focus groups spreadsheet](https://docs.google.com/spreadsheets/d/16N5oZ9wE6AkiqMz7b_707eh24vvpjMwsEG67XFAbxy8/edit#gid=0). With so many interested contributors, it is relevant to make it a focus group. [@tillkruess](https://profiles.wordpress.org/tillkruess/) and [@dustinrue](https://profiles.wordpress.org/dustinrue/) will be the POCs for this focus group. [#meeting](https://make.wordpress.org/core/tag/meeting/), [#performance](https://make.wordpress.org/core/tag/performance/), [#performance-chat](https://make.wordpress.org/core/tag/performance-chat/), [#summary](https://make.wordpress.org/core/tag/summary/) ### Share this: * [ Threads ](https://make.wordpress.org/core/2021/11/18/performance-team-meeting-summary-november-16-2021/?share=threads) * [ Mastodon ](https://make.wordpress.org/core/2021/11/18/performance-team-meeting-summary-november-16-2021/?share=mastodon) * [ Bluesky ](https://make.wordpress.org/core/2021/11/18/performance-team-meeting-summary-november-16-2021/?share=bluesky) * [ X ](https://make.wordpress.org/core/2021/11/18/performance-team-meeting-summary-november-16-2021/?share=x) * [ Facebook ](https://make.wordpress.org/core/2021/11/18/performance-team-meeting-summary-november-16-2021/?share=facebook) * [ LinkedIn ](https://make.wordpress.org/core/2021/11/18/performance-team-meeting-summary-november-16-2021/?share=linkedin) 1. ![](https://secure.gravatar.com/avatar/807c709d4142e246c32a82d4f675a7d88ada930e468525567a32806e0746e870? s=32&d=mm&r=g) 2. [titsmaker](https://profiles.wordpress.org/titsmaker/) 1:05 pm _on_ November 19, 2021 3. It’s great that there’s a performance team now, but I am a bit concerned with your approach to improving performance. I mean most focus groups are devoted to some peripheral areas (which are often already well served by plugins), while in the meantime there are dozens of stale performance tickets on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. addressing some fundamental issues of WordPress architecture and they are still being punted from version to version. There’s no group responsible for making the whole architecture better and more efficient. Also what about focus areas that don’t have enough people to form a working group – they are just not getting any attention until there are more people involved? Comments are closed. # Post navigation [← WordPress 5.9 Beta 1 delayed](https://make.wordpress.org/core/2021/11/17/wordpress-5-9-beta-1-delayed/) [CSS Chat Summary: 11 November 2021 →](https://make.wordpress.org/core/2021/11/18/css-chat-summary-11-november-2021/)