Performance Lab

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

April’s release 2.3.0 includes further enhancements to creating stand-alone plugins as well as some small bug fixes. 

The second 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 WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party, Fetchpriority has been approved by the WordPress plugin team, awaiting approval of Dominant Color Images. 

The Performance Lab plugin has also reached 70k active installations this month!

Proposals and Discussion

Performance Team chats are held weekly on Tuesdays; check https://make.wordpress.org/meetings/ for current time.

A PR has been created for the work against enhancing the Scripts API with a loading strategy. The focus in May has been on addressing initial feedback which has mainly been completed. There are some final decisions to make around handling deferred and async dependencies, and inline scripts attached to defer/async scripts. 

The Plugin Checker engineering of the infrastructure, admin screens and 2 initial checks has been completed. May’s focus has been around final iterations following the architectural code review, QA testing. Progress can be seen in this GitHub repo, which eventually should be transferred to the WordPress organization. 

A blog post was published outlining the WordPress 6.2 server performance analysis summary to identify the biggest opportunities to target for future performance enhancements, from which a notable inclusion has already landed for 6.3 #58394 resulting in ~7% faster blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. themes and 2% faster classic themes (full results). 

Last week saw the ‘More accurate lazy-loading’ work committed. Related to this, great progress has been made on adding fetchpriority support against #58235 in this pull request.

Additional work across the team has seen Several new TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets have been created for improving the automated performance testing workflow that was introduced in the WP 6.2 release cycle (#58358, #58359 and #58360).

Tickets

In addition to Performance Lab, the Performance Team also works on performance-related tickets in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and holds a fortnightly Bug Bash on Wednesdays; check https://make.wordpress.org/meetings/ for current time.

In the last two weeks, several fixes for more accurate lazy-loading were committed to WordPress core. Here are all the commits and tickets:

• [55816] (see #58213)
• [55821] (see #58212)
• [55825] (see #58089)
• [55847] (see #58211)
• [55850] (see #56588)

The WordPress core pull request mentioned last month, to enhance get_block_templates() performance was committed, and improves overall server response time for sites using a block theme by a significant ~15%.

Some initial improvements to translations have already been applied ahead of a broader performance initiative for translated sites (#58321 and #58317).

Additional improvements have been committed around lazy loading 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 #58185, #5780, #57701, and #58230.

Work continues on #58394 for the performance of wp_maybe_inline_styles ahead of the 6,3 release. The work here demonstrates a significant performance improvement for block themes (~7% faster) and for classic themes (~2% faster).

The team is heavily working on further performance tickets prioritized for the upcoming 6.3 release.

#core-performance, #performance

Performance Lab

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

April’s release 2.2.0 includes a few enhancements relating to the creation of standalone plugins. The Fetchpriority module furthermore had its “experimental” flag removed, now that the underlying HTMLHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites. attribute is standardized.

Engineering continues to progress on 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 WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party (see overview issue). The first step in publishing modules as standalone plugins saw the WebP Uploads plugin published in April. The Fetchpriority plugin is currently awaiting approval from the WordPress plugin team, and Dominant Color Images will follow. An engineering approach to removing these modules from the PL plugin is being discussed. 

Proposals and Discussion

Performance Team chats are held weekly on Tuesdays; check https://make.wordpress.org/meetings/ for current time.

Engineering has continued for enhancing the Scripts API with a loading strategy (work can be seen here), the focus in April has been on testing and iteration. A pull request against WordPress 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 of the infrastructure, admin screens and 2 initial checks has been completed. April’s focus has been around architectural code review, QA testing and iteration. Progress can be seen in this GitHub repo, which eventually should be transferred to the WordPress organization. 

The team continues researching remaining problems with lazy-loading. They have also been finalizing an initial performance profiling analysis of WordPress, which they plan to share with the community, and from which they are planning to identify future actionable items. Other exploration has been taking place on improving option autoloading and also on enhancing the initial automated performance workflow.

Tickets

In addition to Performance Lab, the Performance Team also works on performance-related tickets in core and holds a fortnightly Bug Bash on Wednesdays; check https://make.wordpress.org/meetings/ for current time.

The cadence of the performance bug scrubs has been changed to every 2 weeks, from Wednesday April 26 onwards to ensure issues targeting the next WordPress release are reviewed more frequently.

A blog post for the benefits of prioritizing and measuring performance in 6.2 was released this week as a performance retrospective on the 6.2 release cycle, outlining WordPress 6.2 loads 14-18% faster overall for blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. themes and 2-5% faster overall for classic themes based on lab benchmarks. Work continues on various TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets to further enhance performance for the upcoming 6.3 release.

The WordPress core pull request to enhance get_block_templates() performance is close to being committed, and is expected to improve overall server response time for sites using a block theme by a significant ~15%.

Implementing lazy loading term 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. in WP_Term_Query has been merged for 6.3 (#57645). Other issues that have been completed for 6.3 include Using `wp_theme_has_theme_json` in `_wp_theme_json_webfonts_handler` (#57814) and Remove `wp-nux` CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. as dependency from `wp-edit-post` and `wp-editor` (#57827). The team have also worked on performance of _wp_normalize_relative_css_links() can be increased >2x (#58069). Most recently, a notable performance improvement to the `get_block_templates()` function was committed, which improves server response time for sites using block templates by ~15% (#57756).

The team is heavily working on further performance tickets prioritized for the upcoming 6.3 release.

#core-performance, #performance