Core Performance Team Update: March 27, 2023

Performance Lab

Performance Lab plugin updates are released monthly on the third Monday of the month.

March’s release 2.1.0 includes a few enhancements and interoperability fixes for the Server-Timing 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. and general module loading.

Engineering is in progress for creating standalone plugins and unbundling the 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 Plugin Directory or can be cost-based plugin from a third-party (see overview issue), the team are aiming to publish the initial set of standalone plugins mid-April.

Proposals and Discussion

Performance Team chats are held weekly on Tuesdays; check for current time.

In late February, @mxbclang resigned from the Team RepTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. position. @clarkeemily was voted as the second Team Rep, alongside @flixos90

Following the 2023 performance roadmap being published, the performance team SlackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at chats have focused discussions around the priorities agreed. To note, this is a living document and new projects are welcomed. 

Work is almost complete for Enhancing the Scripts API with a loading strategy (work can be seen here), and a pull request against WP CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. will be opened soon. 

The Plugin Checker engineering is progressing very well, with the infrastructure, admin screens and 2 initial checks targeted to be complete by mid-April. Progress can be seen in this GitHub repo

Other areas of focus continue to be on gathering some profiling data on the most recent release candidateRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. to support the server response time analysis. The team is also working on a high-level review of our approach to calculating sizes attribute for images and also researching remaining problems with lazy-loading. 


In addition to Performance Lab, the Performance Team also works on performance-related tickets in core and holds a monthly Bug Bash on the first Wednesday of every month; check for current time.

WordPress 6.2 contains many performance improvements and analysis demonstrates it is notably faster than 6.1, both on the server-side and the client-side, as seen in early Web Vitals metrics from the lab. After several weeks of different testing methodologies being trialed, we now have an approach that works well for this type of benchmarking (expect a blog post sharing this soon!). 

The automated performance testing CI workflow has been committed to core [55459]. We’re successfully getting automated performance data on every commit to core now available in the dashboard here

The team are now conducting discovery around lazy loading all metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. data in WordPress (#57645, #57801 and #57496).

#core-performance, #performance