Tickets and contributions

The Performance Team 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 Scrub on Wednesdays; check https://make.wordpress.org/meetings/ for current time.

In August, the Performance Team published a post regarding WordPress 6.3 performance improvements, highlighting WordPress 6.3 loads 27% faster 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 18% faster for classic themes compared to WordPress 6.2, based on the Largest Contentful Paint (LCP) metric. These results are a major achievement in terms of performance. 

The focus in August was on tickets prioritized for the upcoming WordPress 6.4 release which will include making use of the new script loading strategy APIs in Core, improving autoloaded options and continuation of work on improving server performance bottlenecks, in particular template loading. WordPress 6.4 will also expand capabilities of the automated performance testing workflows and dashboard, and efforts will continue to improve theme.json APIs.

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 Checker

The Performance Team has successfully completed engineering and discussions have commenced with the Plugin Review Team Reps over the coming weeks to find a path forward for collaborative development. For detailed context and information, please refer to the project’s readme and documentation.

Performant Translations Plugin

Version 1 of the Performant Translations plugin was published to WordPress this week which uses a new approach to handling translation files, based on the in-depth analysis the team conducted earlier this year.

Team headlines and updates

WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. US contributor dayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. saw several people visit the Performance Table, several items were worked on including

• #58962 was completed, introducing new functions prime_options() , prime_options_by_group() and get_options(), to provide a way to load multiple options with a single database request
• #58964 had a pull request implemented, introducing new functions to modify the autoload value for multiple options independently of their values
• #58998 was fixed, to prevent races and stampedes when flush_rewrite_rules() is called on a busy site
• #52579 was fixed by adding a new filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. to avoid a potentially expensive DB query
• #59181 made a performance optimization of register_block_script_handle()
• #55491 progress was made for removing unload event handlers from wp-admin
• #58027 and #59225 had a solution identified via GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/, to fix query loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. bugs by correctly relying on the main query and removing problematic workaround, which is partly related to performance as the underlying bugs affected the image loading optimization logic.

Performance Lab Plugin

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

August’s release 2.6.0 includes infrastructure improvements and enhancements around Server-Timing, which allow controlling which action and filter hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same. to measure through a dedicated UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing.. The release also saw some minor compatibility tweaks implemented for the Dominant Color Images module. The team is currently waiting for the next standalone plugin, Dominant Color Images, to be approved by the plugin review team. Work continues on the next set of enhancements around uncoupling the plugin features from the Performance Lab plugin related to the settings screen UI. 

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

#core-performance, #performance

Tickets and contributions

The Performance Team 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.

For the upcoming WordPress 6.3 release, the WordPress performance team has been focusing on closing several issues for the 6.3 release.

The Performance Team is happy to be able to report that the PR for #12009 was committed to WordPress core, closing a 13 year old ticket. This is a big milestone for the team, thank you to everyone who contributed to get this across the line. There is still a desire to extend support to inline scripts, so a new ticket has been opened (#58632) for that discussion, and several use-cases for the new 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. across WordPress core and GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ are being discussed.

Additionally, the team is excited to share that we landed fetchpriority=”high” support #58235 in WordPress core. The commit [56037] includes notable refactoring to make the logic that was previously scoped to only lazy-loading more broadly available, as it is also required for fetchpriority. With that refactoring it also unblocks a fix to another issue that still needs to be addressed with lazy-loading: #58635

Both of these performance enhancements will launch as part of the upcoming WordPress 6.3 release.

For raw performance enhancements, 3 major highlights are:

• Emoji loader script causes ~100ms long task #58472 (~20% LCP improvement, committed in [56074])
• Performance issue in register_block_style_handle function #58528 (~30% server response time improvement 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, committed in [56044])
• Improve performance of get_block_templates function #57756 (~15% server response time improvement for block themes, committed in [55687])

The Plugin Checker engineering has been completed for milestone 2 which now also includes additional checks. Progress can be seen in this GitHub repo, which eventually should be transferred to the WordPress organization. 

Team headlines and updates

WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe contributor dayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. was a great success – thank you to those who joined! There were 2 performance tables this year; the first focused on the script loading strategy API testing the PR by modifying some plugins and core code to use it, and the second focused on profiling and benchmarking. 

Several new articles were added to the Performance Handbook this month:

• Profiling vs Benchmarking article
• Best practices for performance measurement
• Benchmarking php performance with server timing
• PHP performance with XHProf

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

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

May’s release 2.4.0 includes further enhancements to creating stand-alone plugins and infrastructure, as well as some small bug fixes. 

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

#core-performance, #performance

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