Title: meta – Page 3 – Make WordPress Core --- # Tag Archives: meta [ ](https://profiles.wordpress.org/mxbclang/) [Bethany Chobanian Lang](https://profiles.wordpress.org/mxbclang/) 5:07 pm _on_ November 8, 2022 Tags: [core-js ( 131 )](https://make.wordpress.org/core/tag/core-js/), [core-media ( 116 )](https://make.wordpress.org/core/tag/core-media/), [hosting-community ( 31 )](https://make.wordpress.org/core/tag/hosting-community/), meta, [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 Chat Summary: 8 November 2022](https://make.wordpress.org/core/2022/11/08/performance-team-meeting-summary-8-november-2022/)󠁿 [Meeting agenda here](https://make.wordpress.org/core/2022/11/07/performance-chat-agenda-8-november-2022/) and the full chat log is available [beginning here on Slack](https://wordpress.slack.com/archives/C02KGN5K076/p1667923220186119). ## Mini bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrub of performance issues for 6.1.1 * [See here](https://core.trac.wordpress.org/query?status=accepted&status=assigned&status=new&status=reopened&status=reviewing&focuses=~performance&milestone=6.1.1&order=priority) * https://core.trac.wordpress.org/ticket/56923 – PR committed; should become available when [@mamaduka](https://profiles.wordpress.org/mamaduka/) syncs 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/](https://wordpress.org/gutenberg/) to coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. on Thursday * https://core.trac.wordpress.org/ticket/56815 – assigned to [@flixos90](https://profiles.wordpress.org/flixos90/) for review * https://core.trac.wordpress.org/ticket/56900 – assigned to [@peterwilsoncc](https://profiles.wordpress.org/peterwilsoncc/) for commit * https://core.trac.wordpress.org/ticket/56945 – [@flixos90](https://profiles.wordpress.org/flixos90/) has PR in progress at https://github.com/WordPress/wordpress-develop/pull/3536 that needs review and feedback, especially from Gutenberg team. [@annezazu](https://profiles.wordpress.org/annezazu/) working to 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](https://codex.wordpress.org/The_Loop) someone in there. * https://core.trac.wordpress.org/ticket/56948 – ready for commit, just needs a final review; assigned to [@peterwilsoncc](https://profiles.wordpress.org/peterwilsoncc/) * https://core.trac.wordpress.org/ticket/56952 – [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/) to look into * https://core.trac.wordpress.org/ticket/56974 – [@flixos90](https://profiles.wordpress.org/flixos90/) took a first look at the PR last week and will give it a comprehensive review today * https://core.trac.wordpress.org/ticket/56990 – [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/)‘ s changes need review/testing * https://core.trac.wordpress.org/ticket/56991 – [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/)‘ s fix at https://github.com/WordPress/wordpress-develop/pull/3575 needs review * https://core.trac.wordpress.org/ticket/57012 – ready for commit by [@peterwilsoncc](https://profiles.wordpress.org/peterwilsoncc/) ## Focus area updates ### Images [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/) [@mikeschroder](https://profiles.wordpress.org/mikeschroder/) [GitHub project](https://github.com/WordPress/performance/projects/1) * [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/): Discovered a library, [jSquash](https://github.com/jamsinclair/jSquash), that brings image format encoding/decoding to the web. Tested a bit and oping to use it to enhance the core image 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. with modern image capabilitiescapability A **capability** is permission to perform one or more types of task. Checking if a user has a capability is performed by the `current_user_can` function. Each user of a WordPress site might have some permissions but not others, depending on their role. For example, users who have the Author role usually have permission to edit their own posts (the “edit_posts” capability), but not permission to edit other users’ posts (the “edit_others_posts” capability).. If successful, would let us introduce AVIF support without depending on server-side support. * [@mehulkaklotar](https://profiles.wordpress.org/mehulkaklotar/): Working on [#563](https://github.com/WordPress/performance/issues/563) for Performance Lab to change default WebP quality to 82; [PR needs review](https://github.com/WordPress/performance/pull/571/). #### Feedback requested * See above * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+project%3AWordPress%2Fperformance%2F1+label%3A%22Needs+Discussion%22)( 10 issues) * [Needs Review](https://github.com/WordPress/performance/issues?q=is%3Aopen+project%3AWordPress%2Fperformance%2F1+label%3A%22Needs+Review%22+)( 5 issues) ### Object Cache [@tillkruess](https://profiles.wordpress.org/tillkruess/) [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/) [GitHub project](https://github.com/WordPress/performance/projects/6) * [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/): Working mostly on 6.1.1 issues, but a few for 6.2, as well: - https://github.com/WordPress/wordpress-develop/pull/3544 - https://github.com/WordPress/wordpress-develop/pull/3528 - https://github.com/WordPress/wordpress-develop/pull/3534 - https://github.com/WordPress/wordpress-develop/pull/3366 - https://github.com/WordPress/wordpress-develop/pull/3365 - https://github.com/WordPress/wordpress-develop/pull/3178 * [@tillkruess](https://profiles.wordpress.org/tillkruess/): Chatted with [@johnjamesjacoby](https://profiles.wordpress.org/johnjamesjacoby/) about adding a health check for the new `wp_cache_supports()` function to show which object caching features are supported/not supported but recommended. See https://github.com/WordPress/wordpress-develop/pull/3347. For example, `get_multiple()` is quite important. Any feedback on adding as a health check? - [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/): Now have `wp_cache_supports` in core that we could use and `wp_cache_supports( 'get_multiple')` in all options. Instead of loading all options in one cache key, load each in their own cache key and all in single call. #### Feedback requested * See above * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F6+)( 4 issues) * [Needs Review](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Review%22+project%3AWordPress%2Fperformance%2F6+)( 1 issue) ### Measurement N/A [GitHub project](https://github.com/WordPress/performance/projects/5) * No updates #### Feedback requested * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F5+)( 5 issues) * [Needs Review](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Review%22+project%3AWordPress%2Fperformance%2F5+)( 1 issue) ### JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. & CSSCSS Cascading Style Sheets. [@aristath](https://profiles.wordpress.org/aristath/) [@sergiomdgomes](https://profiles.wordpress.org/sergiomdgomes/) [GitHub project](https://github.com/WordPress/performance/projects/3) * No updates #### Feedback requested * [Tree-shaking block styles on the frontend #41020](https://github.com/WordPress/gutenberg/pull/41020) * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F3+)( 4 issues) * [Needs Review](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Review%22+project%3AWordPress%2Fperformance%2F3+)( 2 issues) ### Database [@olliejones](https://profiles.wordpress.org/olliejones/) [GitHub project](https://github.com/WordPress/performance/projects/7) * [@olliejones](https://profiles.wordpress.org/olliejones/): Ready for a vote on https://github.com/WordPress/performance/issues/132 - Voting now open at https://github.com/WordPress/performance/issues/132#issuecomment- 1307557009 through November 29 * [@aristath](https://profiles.wordpress.org/aristath/): [SQLite module PR is ready for review](https://github.com/WordPress/performance/pull/547) #### Feedback requested * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F7)( 3 issues) * [Needs Review](https://github.com/WordPress/performance/issues?q=is%3Aopen+project%3AWordPress%2Fperformance%2F2+label%3A%22Needs+Review%22+)( 3 issues) ## Infrastructure [@flixos90](https://profiles.wordpress.org/flixos90/) [GitHub project](https://github.com/WordPress/performance/projects/2) * [@flixos90](https://profiles.wordpress.org/flixos90/): Plugin codebase is now updated to reflect our recent modifications to the focus areas per https://github. com/WordPress/performance/pull/566, thanks to [@mukesh27](https://profiles.wordpress.org/mukesh27/) #### Feedback requested * See above * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F2+)( 5 issues) * [Needs Review](https://github.com/WordPress/performance/issues?q=is%3Aopen+project%3AWordPress%2Fperformance%2F2+label%3A%22Needs+Review%22+)( 3 issues) **Our next chat will be held on [Tuesday, November 15, 2022 at 16:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20221115T1600) in the [#core-performance channel](https://wordpress.slack.com/messages/core-performance/) in [Slack](https://make.wordpress.org/chat/).** [#core-js](https://make.wordpress.org/core/tag/core-js/), [#core-media](https://make.wordpress.org/core/tag/core-media/), [#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/), [#hosting-community](https://make.wordpress.org/core/tag/hosting-community/) [#meta](https://make.wordpress.org/core/tag/meta/) [ ](https://profiles.wordpress.org/mxbclang/) [Bethany Chobanian Lang](https://profiles.wordpress.org/mxbclang/) 5:00 pm _on_ November 1, 2022 Tags: [core-js ( 131 )](https://make.wordpress.org/core/tag/core-js/), [core-media ( 116 )](https://make.wordpress.org/core/tag/core-media/), [hosting-community ( 31 )](https://make.wordpress.org/core/tag/hosting-community/), meta, [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 Chat Summary: 1 November 2022](https://make.wordpress.org/core/2022/11/01/performance-team-meeting-summary-1-november-2022/)󠁿 [Meeting agenda here](https://make.wordpress.org/core/2022/10/31/performance-chat-agenda-1-november-2022/) and the full chat log is available [beginning here on Slack](https://wordpress.slack.com/archives/C02KGN5K076/p1667318404021459). ## Announcements * [@mxbclang](https://profiles.wordpress.org/mxbclang/): Upcoming time change - US changes next week (w/c 6 November) – meeting will shift ahead by **one hour** to stay at our regular time, so Nov 8 meeting will be at [Tuesday, November 8, 2022 at 10:00 AM EST](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20221108T1500) ## Focus area updates ### Images [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/) [@mikeschroder](https://profiles.wordpress.org/mikeschroder/) [GitHub project](https://github.com/WordPress/performance/projects/1) * [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/): On the AVIF front, it looks like Apple is building support right into WebKit, which means AVIFs will work on older iOSiOS The operating system used on iPhones and iPads./ MacOS as long as users upgrade Safari (currently support depends on the underlying OS). See [https://github.com/WebKit/WebKit/pull/5669](https://github.com/WebKit/WebKit/pull/5669). The coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. ticketticket Created for both bug reports and feature development on the bug tracker. is [https://core.trac.wordpress.org/ticket/51228](https://core.trac.wordpress.org/ticket/51228); the only outlier for AVIF support is now Microsoft Edge. In addition to 50%+ improvement over JPEG compression, AVIF images add support for HDR on the web; a contributor linked some sample images from the TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticket that are quite impressive. * [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/): When working on the PR for setting `fetchpriority=high` on the [non-lazy-loaded LCP image](https://github.com/WordPress/performance/pull/528), noticed the first image on 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 isn’t having the lazy-loading attribute omitted as expected. Opened [#56930](https://core.trac.wordpress.org/ticket/56930) and [PR #3538](https://github.com/WordPress/wordpress-develop/pull/3538) to resolve; reviews appreciated. Also related: [#56927](https://core.trac.wordpress.org/ticket/56927), [#55996](https://core.trac.wordpress.org/ticket/55996). - [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/): Also flagging https://github.com/WordPress/gutenberg/issues/45224 as related; [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/) will add link to the Trac ticket * [@mehulkaklotar](https://profiles.wordpress.org/mehulkaklotar/): Working on some improvements to Performance Lab: - Issue [#560](https://github.com/WordPress/performance/issues/560) – PR [#565](https://github.com/WordPress/performance/pull/565)– WebP upload configuration checkbox not showing in Settings > Media for multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also **network**, **blog**, **site** -> Merged - Issue [#563](https://github.com/WordPress/performance/issues/563) – PR [#571](https://github.com/WordPress/performance/pull/571/)– Change default WebP quality to 82 * [@masteradhoc](https://profiles.wordpress.org/masteradhoc/): Any updates on WebP? - [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/): There has been some communication with Matt, repeating what he said on his post about concerns about WebP not being ready to be default mostly because it is hard to use outside of the web context. Hopefully in the future we’ll be able to get this kind of feedback earlier in a feature’s lifecycle. To move WebP further, we would need to address the underlying issue, either by improving ecosystem compatibility (which is happening naturally over time) or by improving browser capabilitiescapability A **capability** is permission to perform one or more types of task. Checking if a user has a capability is performed by the `current_user_can` function. Each user of a WordPress site might have some permissions but not others, depending on their role. For example, users who have the Author role usually have permission to edit their own posts ( the “edit_posts” capability), but not permission to edit other users’ posts( the “edit_others_posts” capability). (e.g. save as JPEG). - [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/): In multisite, we used to proxy all attachments through PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher. Could we do that here? Proxy to see if there is WebP support, and if not, return JPEG. Has its downsides but thinking out loud. * [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/): Didn’t know about that; could potentially only handle “missing” images that way using `htaccess` * [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/): It’s still part of core: https://github.com/WordPress/wordpress-develop/blob/trunk/ src/wp-includes/ms-files.php - [@masteradhoc](https://profiles.wordpress.org/masteradhoc/): Could we open a ticket in the Chromium GH for save as JPEG to see if they could add? Would help the biggest part of the web. * [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/): Yes, think it’s worth asking them to consider. - [@flixos90](https://profiles.wordpress.org/flixos90/): We can’t really solve the problem in a clean way in WP though, since the right-click Save As behavior can’t be modified via PHP or JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors.. Wish browsers supported some way of achieving a JPEG download of a WebP image on the web, e.g. if you use a `` element it could be default download as JPEG even when WebP is served in the browser. Or there could be some kind of `download-src` attribute. * [@rmccue](https://profiles.wordpress.org/rmccue/): Have run into this while serving images dynamically, no great way to handle * [@flixos90](https://profiles.wordpress.org/flixos90/): Looking to see if there’s anyone we can work with on this internally at Google #### Feedback requested * See above * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+project%3AWordPress%2Fperformance%2F1+label%3A%22Needs+Discussion%22)( 10 issues) * [Needs Review](https://github.com/WordPress/performance/issues?q=is%3Aopen+project%3AWordPress%2Fperformance%2F1+label%3A%22Needs+Review%22+)( 1 issue) ### Object Cache [@tillkruess](https://profiles.wordpress.org/tillkruess/) [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/) [GitHub project](https://github.com/WordPress/performance/projects/6) * [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/): Tickets: - https://core.trac.wordpress.org/ticket/56923 - https://github.com/WordPress/gutenberg/issues/45309 - https://github.com/WordPress/wordpress-develop/pull/3528 - https://github.com/WordPress/wordpress-develop/pull/3544 - https://github.com/WordPress/wordpress-develop/pull/3534 * [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/): Reviewed performance in 6.1-RC3 and [updated results here](https://docs.google.com/spreadsheets/d/1O_76ErpsjUZzEcJLez3GrXhQQyNC-nndTJ61WMYnmj4/edit?usp=sharing); looking good. FSE themes are still slower than classic themes. Created some tickets related to issues found; have been working on https://github.com/WordPress/wordpress- develop/pull/3540. * [@flixos90](https://profiles.wordpress.org/flixos90/): Also did an analysis on RC3 last week; major improvement over RC1 and RC2. Still a few areas that were slightly worse than 6.0, but some of that is due to added functionality. Still a few quirks where regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or [blockers](https://make.wordpress.org/core/tag/meta/page/3/?output_format=md#blocker). Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. is noticeably worse, namely in the` wp_head` action. Have tracked down the particular change that makes `wp_head` slower even in classic themes; PR with a potential fix here: https://github.com/ WordPress/wordpress-develop/pull/3536. * [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/): Biggest issue is that class is static methods and variables, which makes it hard to review and test. #### Feedback requested * See above * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F6+)( 4 issues) * [Needs Review](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Review%22+project%3AWordPress%2Fperformance%2F6+)( 1 issue) ### Measurement N/A [GitHub project](https://github.com/WordPress/performance/projects/5) * [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/): Digging back into the testing environment work that started awhile ago to see what we can pick up and use and what an MVPMinimum Viable Product "A minimum viable product( MVP) is a product with just enough features to satisfy early customers, and to provide feedback for future product development." - [WikiPedia](https://en.wikipedia.org/wiki/Minimum_viable_product) could look like. Still researching/documenting, but more to come. #### Feedback requested * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F5+)( 5 issues) * [Needs Review](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Review%22+project%3AWordPress%2Fperformance%2F5+)( 1 issue) ### JS & CSSCSS Cascading Style Sheets. [@aristath](https://profiles.wordpress.org/aristath/) [@sergiomdgomes](https://profiles.wordpress.org/sergiomdgomes/) [GitHub project](https://github.com/WordPress/performance/projects/3) * No updates #### Feedback requested * [Tree-shaking block styles on the frontend #41020](https://github.com/WordPress/gutenberg/pull/41020) * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F3+)( 4 issues) * [Needs Review](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Review%22+project%3AWordPress%2Fperformance%2F3+)( 2 issues) ### Database [@olliejones](https://profiles.wordpress.org/olliejones/) [GitHub project](https://github.com/WordPress/performance/projects/7) * [@mxbclang](https://profiles.wordpress.org/mxbclang/): [@aristath](https://profiles.wordpress.org/aristath/) is continuing to work on the SQLite integration module in https://github.com/ WordPress/performance/pull/547; feedback welcome * [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/): Thoughts on running core unit tests against SQLite, similar to how tests are run against memcache? Could allow the tests to fail for now, but would highlight where we need to fix issues. - [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/): Great idea, curious about performance as well - [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/): Is this Trac or 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.? - [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/): Neither, Performance Lab only right now; [proposal here](https://make.wordpress.org/core/2022/09/12/lets-make-wordpress-officially-support-sqlite/) - [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/): Yes, but add official support for testing against SQLite, so in the test run, install the drop-in for SQLite and run tests - [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/): I see, I think that is still core since it’s all in the main `develop` repo - [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/): Will create a ticket for this #### Feedback requested * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F7)( 2 issues) * [Needs Review](https://github.com/WordPress/performance/issues?q=is%3Aopen+project%3AWordPress%2Fperformance%2F2+label%3A%22Needs+Review%22+)( 3 issues) ## Infrastructure [@flixos90](https://profiles.wordpress.org/flixos90/) [GitHub project](https://github.com/WordPress/performance/projects/2) * [@flixos90](https://profiles.wordpress.org/flixos90/): Planning to review https:// github.com/WordPress/performance/pull/566 today, which brings the focus areas up-to-date. * [@mehulkaklotar](https://profiles.wordpress.org/mehulkaklotar/): I have worked on issue [#561](https://github.com/WordPress/performance/issues/561) – PR [#570](https://github.com/WordPress/performance/pull/570)– Investigate unexpected input `Warning` message during release build process - > Needs review and testing both #### Feedback requested * See above * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F2+)( 5 issues) * [Needs Review](https://github.com/WordPress/performance/issues?q=is%3Aopen+project%3AWordPress%2Fperformance%2F2+label%3A%22Needs+Review%22+)( 3 issues) **Our next chat will be held on [Tuesday, November 8, 2022 at 10am EST](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20221108T1500) in the [#core-performance channel](https://wordpress.slack.com/messages/core-performance/) in [Slack](https://make.wordpress.org/chat/).** [#core-js](https://make.wordpress.org/core/tag/core-js/), [#core-media](https://make.wordpress.org/core/tag/core-media/), [#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/), [#hosting-community](https://make.wordpress.org/core/tag/hosting-community/) [#meta](https://make.wordpress.org/core/tag/meta/) [ ](https://profiles.wordpress.org/mxbclang/) [Bethany Chobanian Lang](https://profiles.wordpress.org/mxbclang/) 3:38 pm _on_ October 25, 2022 Tags: [core-js ( 131 )](https://make.wordpress.org/core/tag/core-js/), [core-media ( 116 )](https://make.wordpress.org/core/tag/core-media/), [hosting-community ( 31 )](https://make.wordpress.org/core/tag/hosting-community/), meta, [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 Chat Summary: 25 October 2022](https://make.wordpress.org/core/2022/10/25/performance-team-meeting-summary-25-october-2022/)󠁿 [Meeting agenda here](https://make.wordpress.org/core/2022/10/24/performance-chat-agenda-25-october-2022/) and the full chat log is available [beginning here on Slack](https://wordpress.slack.com/archives/C02KGN5K076/p1666710082936079). ## Announcements * [@mxbclang](https://profiles.wordpress.org/mxbclang/): Upcoming time change - Europe changes w/c 30 October before US does – Nov 1 meeting will be **one hour later** at [Tuesday, November 1, 2022 at 12:00 PM EDT](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20221101T1600) - US changes w/c 6 November – meeting will shift ahead by **one hour** to stay at our regular time, so Nov 8 meeting will be at [Tuesday, November 8, 2022 at 10:00 AM EST](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20221108T1500) ## Focus area updates * [@mxbclang](https://profiles.wordpress.org/mxbclang/): Results of [focus area updates vote](https://github.com/WordPress/performance/issues/554) - Added new Database focus area – see [GH label](https://github.com/WordPress/performance/labels/%5BFocus%5D%20Database) and [Project](https://github.com/WordPress/performance/projects/7) - Renamed JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. [https://www.javascript.com](https://www.javascript.com/) focus area to JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. & CSSCSS Cascading Style Sheets. – see [GH label](https://github.com/WordPress/performance/labels/%5BFocus%5D%20JS%20%26%20CSS) and [Project](https://github.com/WordPress/performance/projects/3) - Removed Site Health focus area – added “LEGACY” to [GH label](https://github.com/WordPress/performance/labels/%5BFocus%5D%20Site%20Health%20LEGACY) and [Project](https://github.com/WordPress/performance/projects/4) and moved all active issues to an appropriate new focus area - Working on adding a list of focus areas to the Handbook - Call for leads for Database – [@olliejones](https://profiles.wordpress.org/olliejones/) volunteered! Will update GH accordingly ### Images [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/) [@mikeschroder](https://profiles.wordpress.org/mikeschroder/) [GitHub project](https://github.com/WordPress/performance/projects/1) * [@mxbclang](https://profiles.wordpress.org/mxbclang/): Working on changing the image quality for WebPs in Performance Lab from 86 to 82: [https://github.com/WordPress/performance/issues/563](https://github.com/WordPress/performance/issues/563) * [@pbearne](https://profiles.wordpress.org/pbearne/): Will investigate [https://github.com/WordPress/performance/issues/562](https://github.com/WordPress/performance/issues/562) this week #### Feedback requested * See above * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+project%3AWordPress%2Fperformance%2F1+label%3A%22Needs+Discussion%22)( 10 issues) * [Needs Review](https://github.com/WordPress/performance/issues?q=is%3Aopen+project%3AWordPress%2Fperformance%2F1+label%3A%22Needs+Review%22+)( 1 issue) ### Object Cache [@tillkruess](https://profiles.wordpress.org/tillkruess/) [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/) [GitHub project](https://github.com/WordPress/performance/projects/6) * No updates #### Feedback requested * See above * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F6+)( 4 issues) * [Needs Review](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Review%22+project%3AWordPress%2Fperformance%2F6+)( 1 issue) ### Measurement N/A [GitHub project](https://github.com/WordPress/performance/projects/5) * **We’re seeking 1-2 POCs for this group; if you’re interested, please comment here or pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of“ Ping me when the meeting starts.” in SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/)** * [@mxbclang](https://profiles.wordpress.org/mxbclang/): Work continuing on defining the 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/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. Checker plugin and getting close to engineering; more updates soon #### Feedback requested * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F5+)( 5 issues) * [Needs Review](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Review%22+project%3AWordPress%2Fperformance%2F5+)( 1 issue) ### JS & CSS [@aristath](https://profiles.wordpress.org/aristath/) [@sergiomdgomes](https://profiles.wordpress.org/sergiomdgomes/) [GitHub project](https://github.com/WordPress/performance/projects/3) * No updates #### Feedback requested * [Tree-shaking block styles on the frontend #41020](https://github.com/WordPress/gutenberg/pull/41020) * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F3+)( 4 issues) * [Needs Review](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Review%22+project%3AWordPress%2Fperformance%2F3+)( 2 issues) ### Database [@olliejones](https://profiles.wordpress.org/olliejones/) [GitHub project](https://github.com/WordPress/performance/projects/7) * No updates #### Feedback requested * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F7)( 2 issues) * [Needs Review](https://github.com/WordPress/performance/issues?q=is%3Aopen+project%3AWordPress%2Fperformance%2F2+label%3A%22Needs+Review%22+)( 2 issues) ## Infrastructure [@flixos90](https://profiles.wordpress.org/flixos90/) [GitHub project](https://github.com/WordPress/performance/projects/2) * [@flixos90](https://profiles.wordpress.org/flixos90/): Planning to get back to 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. work this week and reviewing focus area updates in [https://github.com/WordPress/performance/pull/566](https://github.com/WordPress/performance/pull/566) today #### Feedback requested * See above * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F2+)( 6 issues) * [Needs Review](https://github.com/WordPress/performance/issues?q=is%3Aopen+project%3AWordPress%2Fperformance%2F2+label%3A%22Needs+Review%22+)( 3 issues) ## Open Floor * [@flixos90](https://profiles.wordpress.org/flixos90/): Identified and validated the main cause of the regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or [blockers](https://make.wordpress.org/core/tag/meta/page/3/?output_format=md#blocker). Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. with [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/) and it has been fixed. Will run another iteration of the same analysis for 6.1- RC3 today or tomorrow to verify that results have improved. - [@olliejones](https://profiles.wordpress.org/olliejones/): What was it? - [@flixos90](https://profiles.wordpress.org/flixos90/): Was caused by a bug in https://core.trac.wordpress.org/ticket/39210. Research has not yet been published as wanted to see how the situation evolves, but fair to say that we got the perfect outcome and it shows how important performance analyses are. Will write a summary with concrete numbers up next week and publish after 6.1 launch. **Our next chat will be held on [Tuesday, November 1, 2022 at 12pm EDT](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20221101T1600) in the [#core-performance channel](https://wordpress.slack.com/messages/core-performance/) in [Slack](https://make.wordpress.org/chat/).** [#core-js](https://make.wordpress.org/core/tag/core-js/), [#core-media](https://make.wordpress.org/core/tag/core-media/), [#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/), [#hosting-community](https://make.wordpress.org/core/tag/hosting-community/) [#meta](https://make.wordpress.org/core/tag/meta/) [ ](https://profiles.wordpress.org/mxbclang/) [Bethany Chobanian Lang](https://profiles.wordpress.org/mxbclang/) 4:06 pm _on_ October 18, 2022 Tags: [core-js ( 131 )](https://make.wordpress.org/core/tag/core-js/), [core-media ( 116 )](https://make.wordpress.org/core/tag/core-media/), [hosting-community ( 31 )](https://make.wordpress.org/core/tag/hosting-community/), meta, [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 Chat Summary: 18 October 2022](https://make.wordpress.org/core/2022/10/18/performance-team-meeting-summary-18-october-2022/)󠁿 [Meeting agenda here](https://make.wordpress.org/core/2022/10/17/performance-chat-agenda-18-october-2022/) and the full chat log is available [beginning here on Slack](https://wordpress.slack.com/archives/C02KGN5K076/p1666105217616379). ## Announcements * [@mxbclang](https://profiles.wordpress.org/mxbclang/): Reminder: [Focus area updates vote](https://github.com/WordPress/performance/issues/554) and call for leads * [@mxbclang](https://profiles.wordpress.org/mxbclang/): Upcoming time change - Europe changes w/c 30 October before US does – Nov 1 meeting will be **one hour later** at [Tuesday, November 1, 2022 at 12:00 PM EDT](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20221101T1600) - US changes w/c 6 November – meeting will shift ahead by **one hour** to stay at our regular time, so Nov 8 meeting will be at [Tuesday, November 8, 2022 at 10:00 AM EST](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20221108T1500) * [@mxbclang](https://profiles.wordpress.org/mxbclang/): [New Handbook](https://make.wordpress.org/performance/handbook/) on our CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Performance site - Some new content, some ported over from the `/docs` folder of 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/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party.. If you have changes or updates, please contact Bethany directly; workflow for updates to come. - [@flixos90](https://profiles.wordpress.org/flixos90/): All new documentation related to Performance Lab should go into this Handbook, not `/docs` as that folder has been removed ## Focus area updates ### Images [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/) [@mikeschroder](https://profiles.wordpress.org/mikeschroder/) [GitHub project](https://github.com/WordPress/performance/projects/1) * [@flixos90](https://profiles.wordpress.org/flixos90/): [Found a bug](https://github.com/WordPress/performance/issues/560) during yesterday’s release party where the WebP upload configuration checkbox is not displaying in Settings > Media on multisites * [@joegrainger](https://profiles.wordpress.org/joegrainger/): #[527](https://github.com/WordPress/performance/pull/527) and #[537](https://github.com/WordPress/performance/pull/537) we’re part of the 1.6.0 release yesterday, which bring us to parity with the planned WebP implementation in core #### Feedback requested * See above * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+project%3AWordPress%2Fperformance%2F1+label%3A%22Needs+Discussion%22)( 9 issues) * [Needs Review](https://github.com/WordPress/performance/issues?q=is%3Aopen+project%3AWordPress%2Fperformance%2F1+label%3A%22Needs+Review%22+)( 1 issue) ### Object Cache [@tillkruess](https://profiles.wordpress.org/tillkruess/) [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/) [GitHub project](https://github.com/WordPress/performance/projects/6) * [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/): Just committed [https://github.com/WordPress/wordpress-develop/commit/7b176e6deaeb54249f7096c8ef8415d3edb46e39](https://github.com/WordPress/wordpress-develop/commit/7b176e6deaeb54249f7096c8ef8415d3edb46e39) * [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/): Spent some time [testing RC2](https://docs.google.com/spreadsheets/d/1O_76ErpsjUZzEcJLez3GrXhQQyNC-nndTJ61WMYnmj4/edit?usp=sharing) and seeing better numbers for page performance than for Beta2. Regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or [blockers](https://make.wordpress.org/core/tag/meta/page/3/?output_format=md#blocker). Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. appears to have come from a change to PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher related to 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/](https://wordpress.org/gutenberg/). Numbers are better than Beta2 but not as good as 6.0 – 0.6325s for Beta2, 0.4014s for RC2, and 0.2929s for 6.0. - [@flixos90](https://profiles.wordpress.org/flixos90/): We’ve been working on a separate performance analysis comparing 6.1 RC1 to 6.0 and will follow up today to do RC2. Unfortunately results haven’t been looking as good as 6.0 in our analysis, either. Hopefully RC2 is improving in our tests, too. - [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/): Have been using Blackfire for testing. You can get a free open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. license; if anyone is interested, can help them get set up. - [@flixos90](https://profiles.wordpress.org/flixos90/): Been using WebPageTest in combination with custom-measured `Server Timing`s, so these two analyses can complement each other well. - [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/): Don’t think we will have time to fix these issues before 6.1 release; these would require big changes so doesn’t feel like a good idea to get merges committed without testing. Maybe possible for 6.1.1. - [@aristath](https://profiles.wordpress.org/aristath/): Been using Xdebug and webgrind and pushed a few tweaks to core in the last few weeks as the result of those tests. [Setup instructions are here](https://github.com/WordPress/wordpress-develop/pull/3418) if anyone’s interested in getting started easily. - [@johnbillion](https://profiles.wordpress.org/johnbillion/): For anyone who wants timing information and doesn’t have access to Xdebug/Cachegrind/XHProf/ Blackfire etc., you can do rough timing with the [Query Monitor plugin](https://querymonitor.com/blog/2018/07/profiling-and-logging/) - [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/): One issue I’ve found is that a lot of code related to `theme.json` is being loaded even if the active theme does not support these features - [@mukesh27](https://profiles.wordpress.org/mukesh27/): Agreed - [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/): Would like to work on conditionally loading these features on classic themes; much of this has been an issue since 5.9 - [@johnbillion](https://profiles.wordpress.org/johnbillion/): There are a few issues on that topic in the Gutenberg repo, e.g. https://github.com/WordPress/ gutenberg/issues/38299 #### Feedback requested * See above * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F6+)( 4 issues) * [Needs Review](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Review%22+project%3AWordPress%2Fperformance%2F6+)( 1 issue) ### Site Health N/A [GitHub project](https://github.com/WordPress/performance/projects/4) * **We’re seeking 1-2 POCs for this group; if you’re interested, please comment here or pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of“ Ping me when the meeting starts.” in SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/)** * [@mxbclang](https://profiles.wordpress.org/mxbclang/): Yesterday’s Performance Lab release included functionality to only load the two new SH checks that will be in 6.1 (persistent cache and full page cache) when they are not available in core: [https://github.com/WordPress/performance/pull/543](https://github.com/WordPress/performance/pull/543) #### Feedback requested * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F4+)( 8 issues) ### Measurement N/A [GitHub project](https://github.com/WordPress/performance/projects/5) * **We’re seeking 1-2 POCs for this group; if you’re interested, please comment here or ping in Slack** #### Feedback requested * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F5+)( 5 issues) * [Needs Review](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Review%22+project%3AWordPress%2Fperformance%2F5+)( 1 issue) ### JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. 󠀁[https://www.javascript.com](https://www.javascript.com/)󠁿 [@aristath](https://profiles.wordpress.org/aristath/) [@sergiomdgomes](https://profiles.wordpress.org/sergiomdgomes/) [GitHub project](https://github.com/WordPress/performance/projects/3) * No updates #### Feedback requested * [Tree-shaking block styles on the frontend #41020](https://github.com/WordPress/gutenberg/pull/41020) * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F3+)( 2 issues) * [Needs Review](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Review%22+project%3AWordPress%2Fperformance%2F3+)( 3 issues) ## Infrastructure [@flixos90](https://profiles.wordpress.org/flixos90/) [GitHub project](https://github.com/WordPress/performance/projects/2) * [@flixos90](https://profiles.wordpress.org/flixos90/): Got 4 non-critical debug warnings during the release deployment yesterday, which we should look into: https://github.com/WordPress/performance/issues/561 * [@flixos90](https://profiles.wordpress.org/flixos90/): Want to highlight the [`Server-Timing` API proposal again](https://github.com/WordPress/performance/issues/551). Been working on a proof of concept in [https://github.com/WordPress/performance/pull/553](https://github.com/WordPress/performance/pull/553) which would be great to get some first reviews on. Also added some example usage code and linked a Gist with several examples for how we could leverage that 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. to expose specific timings. Exact API seems a bit clunky to use and already have some ideas on how to simplify it better to fit the usage. Still works well technically though, so it’s okay to be reviewed. #### Feedback requested * See above * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F2+)( 6 issues) * [Needs Review](https://github.com/WordPress/performance/issues?q=is%3Aopen+project%3AWordPress%2Fperformance%2F2+label%3A%22Needs+Review%22+)( 3 issues) ## **󠀁[Module proposal: SQLite](https://github.com/WordPress/performance/pull/547)󠁿 **– 󠀁[@aristath](https://profiles.wordpress.org/aristath/)󠁿 * [@mxbclang](https://profiles.wordpress.org/mxbclang/): Related to the [broader proposal to make WP officially support SQLite](https://make.wordpress.org/core/2022/09/12/lets-make-wordpress-officially-support-sqlite/) * [@aristath](https://profiles.wordpress.org/aristath/): The SQLite implementation can be found on the [PR linked above](https://github.com/WordPress/performance/pull/547). A couple of minor issues with the implementation, but they don’t have anything to do with the SQLite code itself. The issues I have in that PR are related to the module’s activation and deactivation: when enabling/disabling the module, WP switches DBs and subsequently all options regarding the activation/deactivation of the module are difficult to handle because on option-save, we switch databases. It’s a solvable UXUX User experience issue, but could definitely use some assistance. At this stage, believe it’s time to start collaborating on the PR, test it, and merge relatively early so we can urge more people to test. * [@flixos90](https://profiles.wordpress.org/flixos90/): Re-sharing one idea mentioned when discussing this previously ([see Slack](https://wordpress.slack.com/archives/C02KGN5K076/p1664495614406519)): Present a warning that this will result in an empty DB. If the user clicks Activate, show a modal where they have to enter SQLite config data, then put that into ` wp-config.php` and install the DB before they activate. This way, they could remain on the same screen and continue to use WP or deactivate if they want to. Would avoid an overly confusing experience. * [@aristath](https://profiles.wordpress.org/aristath/): Added a note next to the module (not a modal). SQLite doesn’t currently require any user-provided config, so didn’t want to make things more complicated. Agree that we should have something more user-friendly and be clear about what will happen and why. * [@flixos90](https://profiles.wordpress.org/flixos90/): So there would not be _any_ constant to add to `wp-config.php`? * [@aristath](https://profiles.wordpress.org/aristath/): At this stage, no – the module automatically copies a `db.php` file in `wp-content`, assuming that if the file is there, you want to use SQLite. On deactivation of the module, the file is deleted so you go back to your MySQLMySQL MySQL is a relational database management system. A database is a structured collection of data where content, configuration and other options are stored. [https://www.mysql.com](https://www.mysql.com/) database. * [@flixos90](https://profiles.wordpress.org/flixos90/): There are other use-cases for `db.php`, though, so wary of the existence of the file being the only thing that we rely on. Should probably also back up any existing `db.php` file in case and restore it on deactivation of the module. - [@rickjames](https://profiles.wordpress.org/rickjames/): Will there be a migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. path from SQLite to MySQL? Thinking of a case where someone starts out with a “small” site but it grows “too big” for SQLite * [@aristath](https://profiles.wordpress.org/aristath/): If SQLite is included in core, there will definitely be a migration path. Most likely it would be in the form a canonical plugin and not core. Don’t think it will be the nightmare we envision it to be – just connect both DBs and copy data between them. - [@aristath](https://profiles.wordpress.org/aristath/): If they have a different` db.php` file, then they’re already using a custom DB somehow – if it’s detected, the module does not overwrite and instead exits * [@rickjames](https://profiles.wordpress.org/rickjames/): Don’t think there is any way to keep the DBs “in sync” - [@aristath](https://profiles.wordpress.org/aristath/): There is a way, but wouldn’t want to do it. This is intended to be a module to test the stability of SQLite in WP and work toward implementation in core. Not intended to take care of syncing dbs, using them to back up data, etc. * [@mxbclang](https://profiles.wordpress.org/mxbclang/): Feel free to leave comments on https://github.com/WordPress/performance/pull/547 and we can always discuss this further in a future chat, as well **Our next chat will be held on [Tuesday, October 25, 2022 at 11am EDT](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20221025T1500) in the [#core-performance channel](https://wordpress.slack.com/messages/core-performance/) in [Slack](https://make.wordpress.org/chat/).** [#core-js](https://make.wordpress.org/core/tag/core-js/), [#core-media](https://make.wordpress.org/core/tag/core-media/), [#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/), [#hosting-community](https://make.wordpress.org/core/tag/hosting-community/) [#meta](https://make.wordpress.org/core/tag/meta/) [ ](https://profiles.wordpress.org/mxbclang/) [Bethany Chobanian Lang](https://profiles.wordpress.org/mxbclang/) 4:19 pm _on_ October 11, 2022 Tags: [core-js ( 131 )](https://make.wordpress.org/core/tag/core-js/), [core-media ( 116 )](https://make.wordpress.org/core/tag/core-media/), [hosting-community ( 31 )](https://make.wordpress.org/core/tag/hosting-community/), meta, [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 11 October 2022](https://make.wordpress.org/core/2022/10/11/performance-team-meeting-summary-11-october-2022/)󠁿 [Meeting agenda here](https://make.wordpress.org/core/2022/10/07/performance-chat-agenda-11-october-2022/) and the full chat log is available [beginning here on Slack](https://wordpress.slack.com/archives/C02KGN5K076/p1665500425205239). ## Focus area updates ### Images [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/) [@mikeschroder](https://profiles.wordpress.org/mikeschroder/) [GitHub project](https://github.com/WordPress/performance/projects/1) * [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/): Committed two small fixes related to the existing `image_editor_output_format` filterFilter Filters are one of the two types of Hooks [https://codex.wordpress.org/Plugin_API/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. – [#54476](https://core.trac.wordpress.org/ticket/54476) and [#56442](https://core.trac.wordpress.org/ticket/56442) * [@mukesh27](https://profiles.wordpress.org/mukesh27/): Added checkbox to Settings > Media to control whether to generate JPEG in addition to WebP in [#537](https://github.com/WordPress/performance/pull/537) - [@flixos90](https://profiles.wordpress.org/flixos90/): This is unlikely to ever make it into coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., but it is useful in the 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/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. to test either of the two behaviors * [@ankitgade](https://profiles.wordpress.org/ankitgade/): Continuing to work on background processing infrastructure - `Background process runner` class PR is up for review: [https://github.com/WordPress/performance/pull/512](https://github.com/WordPress/performance/pull/512) - Working on job status check cron: [https://github.com/WordPress/performance/pull/552](https://github.com/WordPress/performance/pull/552) - Working on adminadmin (and super admin) queue screen: [https://github.com/WordPress/performance/pull/533](https://github.com/WordPress/performance/pull/533) #### Feedback requested * See above * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+project%3AWordPress%2Fperformance%2F1+label%3A%22Needs+Discussion%22)( 9 issues) * [Needs Review](https://github.com/WordPress/performance/issues?q=is%3Aopen+project%3AWordPress%2Fperformance%2F1+label%3A%22Needs+Review%22+)( 1 issue) ### Object Cache [@tillkruess](https://profiles.wordpress.org/tillkruess/) [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/) [GitHub project](https://github.com/WordPress/performance/projects/6) * [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/): Published and helped with several dev notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. for 6.1: - https://make.wordpress.org/core/2022/10/10/performance-improvements-to-the- rest-api/ - https://make.wordpress.org/core/2022/10/10/multisite-improvements-in-wordpress- 6-1/ - https://make.wordpress.org/core/2022/10/07/improvements-to-wp_query-performance- in-6-1/ - https://make.wordpress.org/core/2022/10/06/new-cache-site-health-checks-in- wordpress-6-1/ - https://make.wordpress.org/core/2022/10/11/performance-field-guide-for-wordpress- 6-1/ * [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/): Also merged https:// github.com/WordPress/wordpress-develop/pull/3424 and https://github.com/WordPress/ wordpress-develop/pull/3403 and need code review for https://github.com/WordPress/ wordpress-develop/commit/832b6c35f36d5f1ca84feadc49b0e5424af0ad6c, which will add a new function to core called `wp_cache_supports` to allow object caches to support different functionality * [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/): Been investigating the performance regression seen in Beta 2, particularly new caching issues in block themes – see https://github.com/WordPress/gutenberg/issues/44772 for details. PR in the works https://github.com/WordPress/wordpress-develop/pull/3418 that needs review ASAP before the RC1 cutoff. #### Feedback requested * See above * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F6+)( 4 issues) * [Needs Review](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Review%22+project%3AWordPress%2Fperformance%2F6+)( 1 issue) ### Site Health N/A [GitHub project](https://github.com/WordPress/performance/projects/4) * **We’re seeking 1-2 POCs for this group; if you’re interested, please comment here or pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of“ Ping me when the meeting starts.” in SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/)** * [@mxbclang](https://profiles.wordpress.org/mxbclang/): Dev note for new Site Health checks has been published: https://make.wordpress.org/core/2022/10/06/ new-cache-site-health-checks-in-wordpress-6-1/ #### Feedback requested * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F4+)( 8 issues) ### Measurement N/A [GitHub project](https://github.com/WordPress/performance/projects/5) * **We’re seeking 1-2 POCs for this group; if you’re interested, please comment here or ping in Slack** #### Feedback requested * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F5+)( 5 issues) * [Needs Review](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Review%22+project%3AWordPress%2Fperformance%2F5+)( 1 issue) ### JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. 󠀁[https://www.javascript.com](https://www.javascript.com/)󠁿 [@aristath](https://profiles.wordpress.org/aristath/) [@sergiomdgomes](https://profiles.wordpress.org/sergiomdgomes/) [GitHub project](https://github.com/WordPress/performance/projects/3) * No updates #### Feedback requested * [Tree-shaking block styles on the frontend #41020](https://github.com/WordPress/gutenberg/pull/41020) * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F3+)( 2 issues) * [Needs Review](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Review%22+project%3AWordPress%2Fperformance%2F3+)( 3 issues) ## Infrastructure [@flixos90](https://profiles.wordpress.org/flixos90/) [GitHub project](https://github.com/WordPress/performance/projects/2) * [@flixos90](https://profiles.wordpress.org/flixos90/): Our next release, 1.6.0, will be this coming Monday, October 17. Any feature or enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. that you want to include in this release should be completed and merged by **tomorrow** (Wednesday, October 12, see [#548](https://github.com/WordPress/performance/issues/548)). #### Feedback requested * See above * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F2+)( 6 issues) * [Needs Review](https://github.com/WordPress/performance/issues?q=is%3Aopen+project%3AWordPress%2Fperformance%2F2+label%3A%22Needs+Review%22+)( 3 issues) ## Focus area updates [@flixos90](https://profiles.wordpress.org/flixos90/) * [@flixos90](https://profiles.wordpress.org/flixos90/): Three proposed changes that have come up in recent weeks to align focus areas. First is to introduce a new Database focus area; there are several module proposals (SQLite, optimized autoloaded options, database health checks) and some core optimizations that would also fit into this - [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/): Should Object Caching and Database be the same? - [@olliejones](https://profiles.wordpress.org/olliejones/): Suggest keeping them separate - [@flixos90](https://profiles.wordpress.org/flixos90/): Don’t think so, some are pure database optimizations while sometimes object caching works around DB requests. I’d say adding caching around DB queries is still “Object Caching,” but there’s also room to improve some queries themselves and other DB issues - [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/) agrees * [@flixos90](https://profiles.wordpress.org/flixos90/): Second: We have a JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. focus, but there’s also a lot of work going on in 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/](https://wordpress.org/gutenberg/) to improve CSSCSS Cascading Style Sheets. loading. Should we introduce a CSS area, or alternatively broaden the existing focus to be Assets (including CSS& JS)? - [@mxbclang](https://profiles.wordpress.org/mxbclang/): Makes sense to me to broaden JS to both unless we have someone who is really interested in leading CSS - [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/): Think they should be separate; if no one leads CSS, then it is not a “focus” - [@mxbclang](https://profiles.wordpress.org/mxbclang/): That’s not entirely true; there’s some maintenance around designating something as a “focus,” e.g. having it on our weekly agenda, GH labels, updating the `CODEOWNERS` file, etc. - [@olliejones](https://profiles.wordpress.org/olliejones/): Is the scope of the JS focus intended to cover ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. [https://reactjs.org](https://reactjs.org/) apps and XHR/ fetch performance? - [@flixos90](https://profiles.wordpress.org/flixos90/): FWIW the JS focus has barely made any updates here since it was established, but it’s a noticeable aspect of performance and some projects have been kicked off so would not want to remove it; [@aristath](https://profiles.wordpress.org/aristath/) has been quite involved with CSS though - [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/): What does the JS focus mean right now? - [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/): We do have some work around enabling better loading strategies for scripts that falls under JavaScript; I’ve been working on researching the benefits of using defer - [@flixos90](https://profiles.wordpress.org/flixos90/): Generally most of our focus is on website front-end performance, so the JS focus is also focused on front-end – things like deferring scripts, not loading JS that isn’t used, etc. - [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/): How about a“ Front-End” focus then? - [@flixos90](https://profiles.wordpress.org/flixos90/): Don’t think that would make sense, since everything we do is about front-end. Even DB queries and object caching improvements affect the front-end a lot. Let’s discuss later. * [@flixos90](https://profiles.wordpress.org/flixos90/): Last one: Suggest removing the Site Health focus – not because we shouldn’t work on Site Health, but more because any Site Health check actually fits into other areas and would be better suited as part of the other focus areas as opposed to it’s own area. There has not been a focus lead for Site Health, which is maybe another indicator that we should retire this area and consider checks to be part of other focus areas moving forward. - [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/): So like an object caching-related Site Health check would be part of the Object Caching focus, right? Yes - [@flixos90](https://profiles.wordpress.org/flixos90/): Looking at our current SH modules: * Autoloaded options audit > Database * Enqueued assets > JS/CSS (TBD) * Full page cache > Object Caching * WebP support > Images * Vote on all through proposals here through [Tuesday, October 18, 2022 at 1pm EDT](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20221018T1700): https://github.com/WordPress/performance/issues/554 **Our next chat will be held on [Tuesday, October 18, 2022 at 11am EDT](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20221018T1500) in the [#core-performance channel](https://wordpress.slack.com/messages/core-performance/) in [Slack](https://make.wordpress.org/chat/).** [#core-js](https://make.wordpress.org/core/tag/core-js/), [#core-media](https://make.wordpress.org/core/tag/core-media/), [#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/), [#hosting-community](https://make.wordpress.org/core/tag/hosting-community/) [#meta](https://make.wordpress.org/core/tag/meta/) [ ](https://profiles.wordpress.org/mxbclang/) [Bethany Chobanian Lang](https://profiles.wordpress.org/mxbclang/) 4:02 pm _on_ October 4, 2022 Tags: [core-js ( 131 )](https://make.wordpress.org/core/tag/core-js/), [core-media ( 116 )](https://make.wordpress.org/core/tag/core-media/), [hosting-community ( 31 )](https://make.wordpress.org/core/tag/hosting-community/), meta, [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 4 October 2022](https://make.wordpress.org/core/2022/10/04/performance-team-meeting-summary-4-october-2022/)󠁿 [Meeting agenda here](https://make.wordpress.org/core/2022/10/03/performance-chat-agenda-4-october-2022/) and the full chat log is available [beginning here on Slack](https://wordpress.slack.com/archives/C02KGN5K076/p1664895645634169). ## Announcements * [@mxbclang](https://profiles.wordpress.org/mxbclang/): [Mission and philosophies](https://docs.google.com/document/d/1X04VyZ5j-UaGchXqWnZNER3arGv1XXo3abw4YfSnN3M/edit#) review - Drafting a Handbook for [our site](https://make.wordpress.org/performance/) and would like to include overall mission for the team - Please review and leave comments on the doc with your thoughts ## Focus group updates ### Images [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/) [@mikeschroder](https://profiles.wordpress.org/mikeschroder/) [GitHub project](https://github.com/WordPress/performance/projects/1) * [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/): Not much to update, worked on a bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. fix for [#56442](https://core.trac.wordpress.org/ticket/56442) * [@eugenemanuilov](https://profiles.wordpress.org/eugenemanuilov/): [#524](https://github.com/WordPress/performance/issues/524) to disable JPEG subsizes generation for WebP images has been updated based on feedback from [@flixos90](https://profiles.wordpress.org/flixos90/) * [@mukesh27](https://profiles.wordpress.org/mukesh27/): Working on [#525](https://github.com/WordPress/performance/issues/525) to add a checkbox to the Media screen to enable multi-MIME type output, to match with the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. WebP implementation * [@ankitgade](https://profiles.wordpress.org/ankitgade/): Working on background processing infrastructure related to image regeneration - Background job class PR [#507](https://github.com/WordPress/performance/pull/507) is merged - Background process runner [PR](https://github.com/WordPress/performance/pull/512) is in progress and will be ready to review tonight - Adminadmin (and super admin) queue screen [PR](https://github.com/WordPress/performance/pull/533) is work in progress * [@khoipro](https://profiles.wordpress.org/khoipro/): Any updates on SVG uploads? - [@mxbclang](https://profiles.wordpress.org/mxbclang/): No one is actively working on this at the moment, so anyone can pick it up if they have time [https://github.com/WordPress/performance/issues/427](https://github.com/WordPress/performance/issues/427) - [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/): Not working on this right now, but may in the future. Biggest blockerblocker A bug which is so severe that it blocks a release. is that the library that everyone uses for cleaning SVGs requires PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher 7+, so it would need to be forked/rewritten if we wanted backwards compatibility. If we wanted to make it a PHP 7+-only feature, it would make things a lot easier. - [@flixos90](https://profiles.wordpress.org/flixos90/): WP hasn’t really done that before, but don’t think it’s a no-go as long as it’s a non-critical feature - [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/): PHP 5.6 is only 4% of WP installs, per https://wordpress.org/about/stats/ - [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/): We already do something like this with server support for images where you can’t use a format unless your server supports it - [@flixos90](https://profiles.wordpress.org/flixos90/): As long it gracefully falls back if unsupported and doesn’t break anything on older versions, would be totally onboard - [@khoipro](https://profiles.wordpress.org/khoipro/): What about sanitize and escape file uploading, and styling SVG in media preview? - [@flixos90](https://profiles.wordpress.org/flixos90/): Matt also mentioned a few years back that he would be open to WP offering certain features only to sites with HTTPSHTTPS HTTPS is an acronym for Hyper Text Transfer Protocol Secure. HTTPS is the secure version of HTTP, the protocol over which data is sent between your browser and the website that you are connected to. The' S' at the end of HTTPS stands for 'Secure'. It means all communications between your browser and the website are encrypted. This is especially helpful for protecting sensitive data like banking information., kind of similar - [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/): The creator of the library was open to support, not sure how much work we would need to do to port back to 5.6 - [@flixos90](https://profiles.wordpress.org/flixos90/): Unless backporting would be super straightforward, I would say it’s not worth our effort and we make it 7+ only - [@ankitgade](https://profiles.wordpress.org/ankitgade/): We can analyze what issues we see on 5.6 to evaluate how difficult this would be #### Feedback requested * See above * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+project%3AWordPress%2Fperformance%2F1+label%3A%22Needs+Discussion%22)( 9 issues) * [Needs Review](https://github.com/WordPress/performance/issues?q=is%3Aopen+project%3AWordPress%2Fperformance%2F1+label%3A%22Needs+Review%22+)( 2 issues) ### Object Cache [@tillkruess](https://profiles.wordpress.org/tillkruess/) [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/) [GitHub project](https://github.com/WordPress/performance/projects/6) * [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/): Committed https:// core.trac.wordpress.org/ticket/56721 and need review and commit on https://github. com/WordPress/wordpress-develop/pull/3403 * [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/): Also been profiling and testing WP 6.1 betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 2 – [profiling data](https://docs.google.com/spreadsheets/d/1O_76ErpsjUZzEcJLez3GrXhQQyNC-nndTJ61WMYnmj4/edit?usp=sharing) - [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/): WP6.1 beta 2 has a slower page generation time than 6.0, in some cases by a lot (0.6325 vs. 0.2929 seconds), even with fewer DB calls in a lot of cases - [@flixos90](https://profiles.wordpress.org/flixos90/): Did you test 1 for each scenario, or multiple and then use average/median results? * - [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/): Ran at least three times and did median - [@flixos90](https://profiles.wordpress.org/flixos90/): If we could automate, maybe do something like 5-10 runs to make it more accurate * Also working on dev notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase.( [1](https://docs.google.com/document/d/1leEkWUxvcoHd52-lxglz3lX-pS9Fc4nVRGRrH4m9GKk/edit?usp=sharing), [2](https://docs.google.com/document/d/1EFKmDd97jo0St9bIMZ82EDFd2_mDfDEheJ3VuVJUUG0/edit?usp=sharing), [3](https://docs.google.com/document/d/1_D3_J1BwWQ8_zpc7TWWypR-29dHC6l7HZ7eNX0eeMZs/edit?usp=sharing))– [@mxbclang](https://profiles.wordpress.org/mxbclang/) has reviewed and [@flixos90](https://profiles.wordpress.org/flixos90/) will take a look today or tomorrow * [@khoipro](https://profiles.wordpress.org/khoipro/): Will assign someone from their back-end team to take a look at profiling and testing, as well #### Feedback requested * See above * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F6+)( 4 issues) * [Needs Review](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Review%22+project%3AWordPress%2Fperformance%2F6+)( 1 issue) ### Site Health N/A [GitHub project](https://github.com/WordPress/performance/projects/4) * **We’re seeking 1-2 POCs for this group; if you’re interested, please comment here or pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of“ Ping me when the meeting starts.” in SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/)** * [@furi3r](https://profiles.wordpress.org/furi3r/): Draft Make post is in progress for the new SH checks in 6.1, waiting for a final review before publishing #### Feedback requested * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F4+)( 8 issues) ### Measurement N/A [GitHub project](https://github.com/WordPress/performance/projects/5) * **We’re seeking 1-2 POCs for this group; if you’re interested, please comment here or ping in Slack** * [@mxbclang](https://profiles.wordpress.org/mxbclang/): Getting closer to starting engineering on the 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/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. performance checker thanks to [@mehulkaklotar](https://profiles.wordpress.org/mehulkaklotar/) and [@jjgrainger](https://profiles.wordpress.org/jjgrainger/)‘ s work on a design doc #### Feedback requested * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F5+)( 5 issues) * [Needs Review](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Review%22+project%3AWordPress%2Fperformance%2F5+)( 1 issue) ### JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. 󠀁[https://www.javascript.com](https://www.javascript.com/)󠁿 [@aristath](https://profiles.wordpress.org/aristath/) [@sergiomdgomes](https://profiles.wordpress.org/sergiomdgomes/) [GitHub project](https://github.com/WordPress/performance/projects/3) * No updates #### Feedback requested * [Tree-shaking block styles on the frontend #41020](https://github.com/WordPress/gutenberg/pull/41020) * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F3+)( 2 issues) * [Needs Review](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Review%22+project%3AWordPress%2Fperformance%2F3+)( 3 issues) ## Infrastructure [@flixos90](https://profiles.wordpress.org/flixos90/) [GitHub project](https://github.com/WordPress/performance/projects/2) * [@flixos90](https://profiles.wordpress.org/flixos90/): Per the [vote to bump the Performance Lab plugin minimum requirement to WP 6.0](https://github.com/WordPress/performance/issues/531), our next release will require 6.0 * [@flixos90](https://profiles.wordpress.org/flixos90/): Our next release, 1.6.0, will be Monday, October 17, less than two weeks from now. Any feature or enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. that you want to include in this release should be completed and merged by next Wednesday, October 12 (see [#548](https://github.com/WordPress/performance/issues/548)). #### Feedback requested * See above * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F2+)( 6 issues) * [Needs Review](https://github.com/WordPress/performance/issues?q=is%3Aopen+project%3AWordPress%2Fperformance%2F2+label%3A%22Needs+Review%22+)( 3 issues) ## Module proposal: 󠀁[Server-Timing API](https://github.com/WordPress/performance/issues/551)󠁿 [@flixos90](https://profiles.wordpress.org/flixos90/) * [@rickjames](https://profiles.wordpress.org/rickjames/): For server-side performance measurement, MySQLMySQL MySQL is a relational database management system. A database is a structured collection of data where content, configuration and other options are stored. [https://www.mysql.com](https://www.mysql.com/)’s “slowlog” can be useful * [@flixos90](https://profiles.wordpress.org/flixos90/): Not familiar with that tool, but worth exploring another time and feel free to draft a proposal. The current proposal leaves the actual measurement agnostic so it would leave room to introduce a more flexible and opinionated system later. * [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/): Overall love the proposal, are you proposing that this would be included in the response by default once this is added? - [@flixos90](https://profiles.wordpress.org/flixos90/): Yes, envision that it would be added by default * [@johnbillion](https://profiles.wordpress.org/johnbillion/): Added a comment on the issue about headers: headers need to be sent before any output, and a lot of processing that happens in WordPress that would ideally be measured occurs after the output begins - [@flixos90](https://profiles.wordpress.org/flixos90/): Definitely a fair point. Even with that limitation, still a lot of benefit to having the headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. to measure everything until WP begins to render the output. This will be a known limitation eventually, but also think this will become a smaller issue with FSE sites because they typically generate all content and then it is just “printed” out, so less “work” happening after headers are sent. - [@johnbillion](https://profiles.wordpress.org/johnbillion/): Maybe, but `< head>` still gets filled up by plugins and core doing processing. Would be good to think of what metrics would be useful to see and whether exposing those metrics via this 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. makes sense. - [@flixos90](https://profiles.wordpress.org/flixos90/): One example would be the autoloaded options query given the recent module proposal to improve that - [@johnbillion](https://profiles.wordpress.org/johnbillion/): Does FSE actually construct its output before it’s all sent? * [@aristath](https://profiles.wordpress.org/aristath/): Yes, the whole content/ template gets rendered internally prior to sending any headers - [@johnbillion](https://profiles.wordpress.org/johnbillion/): Like the idea of using the Server-Timing API header, but not sure if it necessarily works for WP - [@flixos90](https://profiles.wordpress.org/flixos90/): Isn’t it worth pursuing to be able to cover anything that happens prior to page output, which is a lot? - [@johnbillion](https://profiles.wordpress.org/johnbillion/): It could well be, but would be good to see real world examples of what would be good to measure. Output buffering may not be the worst idea if the API is restricted to the plugin; definitely worth investigating. - [@flixos90](https://profiles.wordpress.org/flixos90/) will think about examples ## Open floor * [@aristath](https://profiles.wordpress.org/aristath/): Started porting SQLite as a module: https://github.com/WordPress/performance/pull/547; will discuss further next week * [@josklever](https://profiles.wordpress.org/josklever/): https://core.trac.wordpress. org/ticket/55344 is related to the performance of the WP dashboard. Resources are loaded for dashboard widgets that are disabled via Screen Options, which can cause unwanted delays or issues for other widgets if there are conflicts. **Our next chat will be held on [Tuesday, October 11, 2022 at 11am EDT](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20221011T1500) in the [#core-performance channel](https://wordpress.slack.com/messages/core-performance/) in [Slack](https://make.wordpress.org/chat/).** [#core-js](https://make.wordpress.org/core/tag/core-js/), [#core-media](https://make.wordpress.org/core/tag/core-media/), [#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/), [#hosting-community](https://make.wordpress.org/core/tag/hosting-community/) [#meta](https://make.wordpress.org/core/tag/meta/) [ ](https://profiles.wordpress.org/mxbclang/) [Bethany Chobanian Lang](https://profiles.wordpress.org/mxbclang/) 3:56 pm _on_ September 27, 2022 Tags: [core-js ( 131 )](https://make.wordpress.org/core/tag/core-js/), [core-media ( 116 )](https://make.wordpress.org/core/tag/core-media/), [hosting-community ( 31 )](https://make.wordpress.org/core/tag/hosting-community/), meta, [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 27 September 2022](https://make.wordpress.org/core/2022/09/27/performance-team-meeting-summary-27-september-2022/)󠁿 [Meeting agenda here](https://make.wordpress.org/core/2022/09/26/performance-chat-agenda-27-september-2022/) and the full chat log is available [beginning here on Slack](https://wordpress.slack.com/archives/C02KGN5K076/p1664290812652609). ## Announcements * [@mxbclang](https://profiles.wordpress.org/mxbclang/): [Mission and philosophies](https://docs.google.com/document/d/1X04VyZ5j-UaGchXqWnZNER3arGv1XXo3abw4YfSnN3M/edit#) review - Drafting a Handbook for [our site](https://make.wordpress.org/performance/) and would like to include overall mission for the team - Please review and leave comments on the doc with your thoughts ## Focus group updates ### Images [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/) [@mikeschroder](https://profiles.wordpress.org/mikeschroder/) [GitHub project](https://github.com/WordPress/performance/projects/1) * [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/): Need dev notes for https://core.trac.wordpress.org/ticket/53232 - [@mxbclang](https://profiles.wordpress.org/mxbclang/): Will work with Adam to see if he can pick this up * [@eugenemanuilov](https://profiles.wordpress.org/eugenemanuilov/): Worked on [#524](https://github.com/WordPress/performance/issues/524) to disable JPEG subsizes generation for WebP images; [#525](https://github.com/WordPress/performance/issues/525) also in progress and almost ready for CR * [@ankitgade](https://profiles.wordpress.org/ankitgade/): Working on background processing infrastructure related to image regeneration - 1. Job class PR is awaiting review: [https://github.com/WordPress/performance/pull/507](https://github.com/WordPress/performance/pull/507) 2. Background process runner PR is in draft as it has dependency on #507:  [https://github.com/WordPress/performance/pull/512](https://github.com/WordPress/performance/pull/512) 3. Adminadmin (and super admin) queue screen PR is in progress: [https://github.com/WordPress/performance/pull/533](https://github.com/WordPress/performance/pull/533) * [@mxbclang](https://profiles.wordpress.org/mxbclang/): No updates on next steps on WebP just yet; discussions still ongoing #### Feedback requested * See above * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+project%3AWordPress%2Fperformance%2F1+label%3A%22Needs+Discussion%22)( 9 issues) * [Needs Review](https://github.com/WordPress/performance/issues?q=is%3Aopen+project%3AWordPress%2Fperformance%2F1+label%3A%22Needs+Review%22+)( 2 issues) ### Object Cache [@tillkruess](https://profiles.wordpress.org/tillkruess/) [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/) [GitHub project](https://github.com/WordPress/performance/projects/6) * [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/): Working on dev notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. for 6.1 - **Improvements to WP_Query** – [https://docs.google.com/document/d/1_D3_J1BwWQ8_zpc7TWWypR-29dHC6l7HZ7eNX0eeMZs/edit?usp=sharing ](https://docs.google.com/document/d/1_D3_J1BwWQ8_zpc7TWWypR-29dHC6l7HZ7eNX0eeMZs/edit?usp=sharing) * [https://core.trac.wordpress.org/ticket/22176](https://core.trac.wordpress.org/ticket/22176) * [https://core.trac.wordpress.org/ticket/55716](https://core.trac.wordpress.org/ticket/55716) * [https://core.trac.wordpress.org/ticket/55620](https://core.trac.wordpress.org/ticket/55620) * [https://core.trac.wordpress.org/ticket/36905](https://core.trac.wordpress.org/ticket/36905) - **Improvements to multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog( wp_posts becomes wp_0_posts). See also network, blog, site** –[https://docs.google.com/document/d/1EFKmDd97jo0St9bIMZ82EDFd2_mDfDEheJ3VuVJUUG0/edit?usp=sharing ](https://docs.google.com/document/d/1EFKmDd97jo0St9bIMZ82EDFd2_mDfDEheJ3VuVJUUG0/edit?usp=sharing) * [https://core.trac.wordpress.org/ticket/37181](https://core.trac.wordpress.org/ticket/37181) * [https://core.trac.wordpress.org/ticket/55802](https://core.trac.wordpress.org/ticket/55802) - **Site Health** –[https://docs.google.com/document/d/11ekflhRTZjxwuXBBDBcvvrRNDL0Gy2NobsuKrHSXdb8/edit?usp=sharing ](https://docs.google.com/document/d/11ekflhRTZjxwuXBBDBcvvrRNDL0Gy2NobsuKrHSXdb8/edit?usp=sharing) * [https://core.trac.wordpress.org/ticket/56040](https://core.trac.wordpress.org/ticket/56040) * [https://core.trac.wordpress.org/ticket/56041](https://core.trac.wordpress.org/ticket/56041) * [@mxbclang](https://profiles.wordpress.org/mxbclang/): Mostly ready to go; waiting for [@furi3r](https://profiles.wordpress.org/furi3r/) to return and publish - **Performance improvements to REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application( think “phone app” or “website”) can communicate with the data store (think“ database” or “file system”) [https://developer.wordpress.org/rest-api/](https://developer.wordpress.org/rest-api/)** * [https://core.trac.wordpress.org/ticket/55677](https://core.trac.wordpress.org/ticket/55677) * [https://core.trac.wordpress.org/ticket/55620](https://core.trac.wordpress.org/ticket/55620) * [https://core.trac.wordpress.org/ticket/55674](https://core.trac.wordpress.org/ticket/55674) * [https://core.trac.wordpress.org/ticket/52992](https://core.trac.wordpress.org/ticket/52992) * [https://core.trac.wordpress.org/ticket/56272](https://core.trac.wordpress.org/ticket/56272) * [https://core.trac.wordpress.org/ticket/55592](https://core.trac.wordpress.org/ticket/55592) * [https://core.trac.wordpress.org/ticket/55716](https://core.trac.wordpress.org/ticket/55716) * [https://core.trac.wordpress.org/ticket/56019](https://core.trac.wordpress.org/ticket/56019) * [https://core.trac.wordpress.org/ticket/56020](https://core.trac.wordpress.org/ticket/56020) * Can [@tillkruess](https://profiles.wordpress.org/tillkruess/) work on this dev notedev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/ theme authors and WordPress developers need to be aware of those changes. In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase.? - **Improvements to caching 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.** * [https://core.trac.wordpress.org/ticket/4476](https://core.trac.wordpress.org/ticket/4476) * [https://core.trac.wordpress.org/ticket/56198](https://core.trac.wordpress.org/ticket/56198) * [https://core.trac.wordpress.org/ticket/56386](https://core.trac.wordpress.org/ticket/56386) - **Script improvements** * [https://core.trac.wordpress.org/ticket/42438](https://core.trac.wordpress.org/ticket/42438) - **Images** * [https://core.trac.wordpress.org/ticket/53232](https://core.trac.wordpress.org/ticket/53232) - [@zzap](https://profiles.wordpress.org/zzap/) will help with doc review - Want to make sure that these changes are listed in the field notes and on the 6.1 about page, since they weren’t included on the betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 announcement blogblog( versus network, site) * Changes like added caching to `WP_Query` have a big impact and need to be called out * [@zzap](https://profiles.wordpress.org/zzap/): These will all be added to the field guideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the [WordPress release cycle](https://make.wordpress.org/core/handbook/about/release-cycle/). The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. #### Feedback requested * See above * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F6+)( 4 issues) * [Needs Review](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Review%22+project%3AWordPress%2Fperformance%2F6+)( 1 issue) ### Site Health N/A [GitHub project](https://github.com/WordPress/performance/projects/4) * **We’re seeking 1-2 POCs for this group; if you’re interested, please comment here or pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of“ Ping me when the meeting starts.” in SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/)** * No updates #### Feedback requested * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F4+)( 8 issues) ### Measurement N/A [GitHub project](https://github.com/WordPress/performance/projects/5) * **We’re seeking 1-2 POCs for this group; if you’re interested, please comment here or ping in Slack** * [@robinwpdeveloper](https://profiles.wordpress.org/robinwpdeveloper/): [Incorrect message about the status of WP_AUTO_UPDATE_CORE #51041](https://core.trac.wordpress.org/ticket/51041) was committed today #### Feedback requested * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F5+)( 5 issues) * [Needs Review](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Review%22+project%3AWordPress%2Fperformance%2F5+)( 1 issue) ### JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. 󠀁[https://www.javascript.com](https://www.javascript.com/)󠁿 [@aristath](https://profiles.wordpress.org/aristath/) [@sergiomdgomes](https://profiles.wordpress.org/sergiomdgomes/) [GitHub project](https://github.com/WordPress/performance/projects/3) * [@aristath](https://profiles.wordpress.org/aristath/): No movement on the JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. front recently, so focusing on general performance improvements instead, including [#56636](https://core.trac.wordpress.org/ticket/56636), [#56637](https://core.trac.wordpress.org/ticket/56637), [#56654](https://core.trac.wordpress.org/ticket/56654) and just a few minutes ago [#56666](https://core.trac.wordpress.org/ticket/56666). The process I’ve been following is to basically run vanilla WP using Xdebug-profiling, examine the results using _webgrind_ and try to reduce the amount of function calls – as well as their cost. Generally small tweaks, with relatively big benefits. Last week [#55005](https://core.trac.wordpress.org/ticket/55005) was also merged in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., so overall I believe WP 6.1 contains a lot of nice and impactful performance changes – as highlighted by all the updates from other folks above. #### Feedback requested * [Tree-shaking block styles on the frontend #41020](https://github.com/WordPress/gutenberg/pull/41020) * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F3+)( 2 issues) * [Needs Review](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Review%22+project%3AWordPress%2Fperformance%2F3+)( 3 issues) ## Infrastructure [@flixos90](https://profiles.wordpress.org/flixos90/) [GitHub project](https://github.com/WordPress/performance/projects/2) * [@mxbclang](https://profiles.wordpress.org/mxbclang/): [Vote about bumping minimum requirement to WP 6.0](https://github.com/WordPress/performance/issues/531) open through this Friday; please vote if you haven’t already * [@mukesh27](https://profiles.wordpress.org/mukesh27/): Add JavaScript coding standard workflow [#515](https://github.com/WordPress/performance/pull/515) and Update `@wordpress/env` to latest version [#546](https://github.com/WordPress/performance/pull/546) need review #### Feedback requested * See above * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F2+)( 5 issues) * [Needs Review](https://github.com/WordPress/performance/issues?q=is%3Aopen+project%3AWordPress%2Fperformance%2F2+label%3A%22Needs+Review%22+)( 3 issues) * [Needs Decision](https://github.com/WordPress/performance/issues?q=is%3Aopen+project%3AWordPress%2Fperformance%2F2+label%3A%22Needs+Decision%22+)( 1 issue) ## Discussion: 󠀁[SQLite support](https://make.wordpress.org/core/2022/09/12/lets-make-wordpress-officially-support-sqlite/)󠁿 [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/) and [@aristath](https://profiles.wordpress.org/aristath/) * [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/): Think this is a great idea and could be useful in core for running unit tests and for other projects like [wordpress-wasm](https://github.com/WordPress/wordpress-wasm). Wonder if the performance team should help take on this problem, even if it is to review the solution and ensure that there’s no performance regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or [blockers](https://make.wordpress.org/core/tag/meta/page/3/?output_format=md#blocker). Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5.. * [@aristath](https://profiles.wordpress.org/aristath/): Understand that testing could be difficult, so currently converting it to work as a 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/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. in [this repository](https://github.com/aristath/sqlite). Trying to convert to something that would make sense for core and then publish in the .org repo as a featured plugin. Hoping if this is in the form of the plugin, more people will test and provide feedback. Also noting that the initial proposal focused on small-to-medium sites, but there’s great potential for growth in other areas as well where large sites can take advantage of SQLite. - [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/): I’ve forked hyperdb and run very large multisites, can provide context here - [@aristath](https://profiles.wordpress.org/aristath/): We’ll need lots of context once we get rolling – the prospect of pairing SQLite and hyperdb is very exciting **Our next chat will be held on [Tuesday, October 4, 2022 at 11am EDT](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20221004T1500) in the [#core-performance channel](https://wordpress.slack.com/messages/core-performance/) in [Slack](https://make.wordpress.org/chat/).** [#core-js](https://make.wordpress.org/core/tag/core-js/), [#core-media](https://make.wordpress.org/core/tag/core-media/), [#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/), [#hosting-community](https://make.wordpress.org/core/tag/hosting-community/) [#meta](https://make.wordpress.org/core/tag/meta/) [ ](https://profiles.wordpress.org/mxbclang/) [Bethany Chobanian Lang](https://profiles.wordpress.org/mxbclang/) 4:59 pm _on_ September 20, 2022 Tags: [core-js ( 131 )](https://make.wordpress.org/core/tag/core-js/), [core-media ( 116 )](https://make.wordpress.org/core/tag/core-media/), [hosting-community ( 31 )](https://make.wordpress.org/core/tag/hosting-community/), meta, [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 20 September 2022](https://make.wordpress.org/core/2022/09/20/performance-team-meeting-summary-20-september-2022/)󠁿 [Meeting agenda here](https://make.wordpress.org/core/2022/09/19/performance-chat-agenda-20-september-2022/) and the full chat log is available [beginning here on Slack](https://wordpress.slack.com/archives/C02KGN5K076/p1663686041968009). ## Announcements * [@mxbclang](https://profiles.wordpress.org/mxbclang/): [Mission and philosophies](https://docs.google.com/document/d/1X04VyZ5j-UaGchXqWnZNER3arGv1XXo3abw4YfSnN3M/edit#) review - Drafting a Handbook for [our site](https://make.wordpress.org/performance/) and would like to include overall mission for the team - Please review and leave comments on the doc with your thoughts ## Focus group updates ### Images [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/) [@mikeschroder](https://profiles.wordpress.org/mikeschroder/) [GitHub project](https://github.com/WordPress/performance/projects/1) * [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/): WebP feature was reverted following Matt’s post. Still trying to determine what a canonical 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/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. is and if it would work for WebP by default. Still have some fixes to land for 6.1 around image quality when WebPs are output via Performance Lab plugin. * [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/): Next steps for [Dominant color feature](https://make.wordpress.org/core/2022/07/21/proposal-add-a-dominant-color-background-to-images/) - We’ve run out of time to merge before BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 cutoff - Feedback process was a lot slower than we thought it would be - Should continue to work on this and try to get it in for 6.2 - [@pbearne](https://profiles.wordpress.org/pbearne/): Version with theme flag could be merged - [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/): Merging now doesn’t feel great as there are still unanswered questions. Code is ready, but not sure what feedback will push this across the line. May need to push early in 6.2 cycle and see what happens. - [@flixos90](https://profiles.wordpress.org/flixos90/): Feels like another merge proposal post with a concrete timeline on a merge date could be good to put out right after 6.1, so people can provide any additional feedback. Should also note the new theme support flag approach. #### Feedback requested * See above * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+project%3AWordPress%2Fperformance%2F1+label%3A%22Needs+Discussion%22)( 9 issues) * [Needs Review](https://github.com/WordPress/performance/issues?q=is%3Aopen+project%3AWordPress%2Fperformance%2F1+label%3A%22Needs+Review%22+)( 2 issues) * [Needs Dev](https://github.com/WordPress/performance/issues?q=is%3Aopen+project%3AWordPress%2Fperformance%2F1+label%3A%22Needs+Dev%22+)( 1 issue) ### Object Cache [@tillkruess](https://profiles.wordpress.org/tillkruess/) [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/) [GitHub project](https://github.com/WordPress/performance/projects/6) * [@mehulkaklotar](https://profiles.wordpress.org/mehulkaklotar/): Working on [#53450](https://core.trac.wordpress.org/ticket/53450) and it is [ready for review here](https://github.com/WordPress/wordpress-develop/pull/3293) * [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/): Merged: - [https://core.trac.wordpress.org/ticket/55802](https://core.trac.wordpress.org/ticket/55802) - [https://core.trac.wordpress.org/ticket/55392](https://core.trac.wordpress.org/ticket/55392) - [https://core.trac.wordpress.org/ticket/36905](https://core.trac.wordpress.org/ticket/36905) * [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/): Focusing on dev notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. next week #### Feedback requested * See above * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F6+)( 4 issues) * [Needs Review](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Review%22+project%3AWordPress%2Fperformance%2F6+)( 1 issue) ### Site Health N/A [GitHub project](https://github.com/WordPress/performance/projects/4) * **We’re seeking 1-2 POCs for this group; if you’re interested, please comment here or pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of“ Ping me when the meeting starts.” in SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/)** * [@mxbclang](https://profiles.wordpress.org/mxbclang/): [#56040](https://core.trac.wordpress.org/ticket/56040) and [#56041](https://core.trac.wordpress.org/ticket/56041) (two Site Health checks from Performance Lab) have been merged for 6.1 and dev notes are in progress * [@mukesh27](https://profiles.wordpress.org/mukesh27/): [PR #543](https://github.com/WordPress/performance/pull/543) for adding `can-load.php` to these Health Checks is ready for review #### Feedback requested * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F4+)( 8 issues) ### Measurement N/A [GitHub project](https://github.com/WordPress/performance/projects/5) * **We’re seeking 1-2 POCs for this group; if you’re interested, please comment here or ping in Slack** * [@mxbclang](https://profiles.wordpress.org/mxbclang/): Reminder about the performance testing environment work started back in March: https://make.wordpress.org/core/ 2022/03/22/performance-team-meeting-summary-22-march-2022/. This has stalled out since then; if anyone is interested in picking it back up, let us know. * [@flixos90](https://profiles.wordpress.org/flixos90/): Working on a proposal to integrate the [Server Timing API](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Server-Timing) into Performance Lab. We have a lack of awareness for how WP is performing server- side and this simple piece of infrastructure would allow us to measure specific features/modules of the plugin to see who they are affecting PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher performance. Should an open an issue this week or next. * [@mehulkaklotar](https://profiles.wordpress.org/mehulkaklotar/): Continuing to work on a proposal for the plugin performance checker tool #### Feedback requested * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F5+)( 5 issues) * [Needs Review](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Review%22+project%3AWordPress%2Fperformance%2F5+)( 1 issue) ### JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. 󠀁[https://www.javascript.com](https://www.javascript.com/)󠁿 [@aristath](https://profiles.wordpress.org/aristath/) [@sergiomdgomes](https://profiles.wordpress.org/sergiomdgomes/) [GitHub project](https://github.com/WordPress/performance/projects/3) * N/A #### Feedback requested * [Tree-shaking block styles on the frontend #41020](https://github.com/WordPress/gutenberg/pull/41020) * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F3+)( 2 issues) * [Needs Review](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Review%22+project%3AWordPress%2Fperformance%2F3+)( 3 issues) ## Infrastructure [@flixos90](https://profiles.wordpress.org/flixos90/) [GitHub project](https://github.com/WordPress/performance/projects/2) * [Bumping minimum requirement to WP 6.0](https://github.com/WordPress/performance/issues/531)– [@flixos90](https://profiles.wordpress.org/flixos90/) - [@olliejones](https://profiles.wordpress.org/olliejones/): [Stats](https://wordpress.org/about/stats/) show that 44% of sites are on pre-6.0 versions, does it make sense to leave them behind? - [@flixos90](https://profiles.wordpress.org/flixos90/): Because this is a feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See [Features as Plugins](https://make.wordpress.org/core/handbook/about/release-cycle/features-as-plugins/), implications here are quite different from WP overall – see [https://github.com/WordPress/performance/blob/trunk/docs/Version-support-policy.md#wordpress-core-versions](https://github.com/WordPress/performance/blob/trunk/docs/Version-support-policy.md#wordpress-core-versions) - [@masteradhoc](https://profiles.wordpress.org/masteradhoc/): Don’t think a lot of users on older versions would be using a feature plugin, seems like a different target group - [@markjaquith](https://profiles.wordpress.org/markjaquith/): Yeah, suspect that the sites using this plugin are more likely to be using 6.0x and even if not, the goal of the plugin is to move things forward - [@robinwpdeveloper](https://profiles.wordpress.org/robinwpdeveloper/): Also think this is a good call - **[Vote here](https://github.com/WordPress/performance/issues/531#issuecomment-1252550889)** by next Friday, September 30 * [@flixos90](https://profiles.wordpress.org/flixos90/): Ran into [this bug](https://github.com/WordPress/performance/issues/539) yesterday during the release, which we should fix before the next one * [@mukesh27](https://profiles.wordpress.org/mukesh27/): Fix broken command for readme changelog [#542](https://github.com/WordPress/performance/pull/542) and Add JavaScript coding standard workflow [#515](https://github.com/WordPress/performance/pull/515) need review #### Feedback requested * See above * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F2+)( 5 issues) * [Needs Review](https://github.com/WordPress/performance/issues?q=is%3Aopen+project%3AWordPress%2Fperformance%2F2+label%3A%22Needs+Review%22+)( 3 issues) * [Needs Decision](https://github.com/WordPress/performance/issues?q=is%3Aopen+project%3AWordPress%2Fperformance%2F2+label%3A%22Needs+Decision%22+)( 1 issue) ## Discussion: 󠀁[Module proposal: Optimized autoloaded options](https://github.com/WordPress/performance/issues/526)󠁿 [@markjaquith](https://profiles.wordpress.org/markjaquith/) * Options are autoloaded by default, and most options stay autoloaded even after the plugin or theme that uses them has been deactivated * This autoloading has a cost in terms of the performance of the query that loads autoloaded options, and also because the values of these options are kept in memory * Discussed a lot of ways of addressing this at 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](https://central.wordcamp.org/about/). US, and the most promising path that would have the most benefit for the most users (and fits in with this group’s philosophy on focusing on automated fixes instead of introducing new APIs) is to dynamically move options in and out of the “autoload” pool based on usage * Options that are used *and* are not past a certain size cutoff should be autoloaded, but large options and options that are not used, should not be autoloaded * Proof of concept is linked in the ticketticket Created for both bug reports and feature development on the bug tracker. and we’re looking for additional feedback * [@pbearne](https://profiles.wordpress.org/pbearne/) already brought up the issue of options that are queried BEFORE a module could start “listening” for them to be called, but there are undoubtedly other gotchas and opportunities here * Especially useful would be help in developing a strategy for measuring the performance of this fix for various sizes of autoloaded options - [@flixos90](https://profiles.wordpress.org/flixos90/): Could leverage 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. (noted above) to measure the time the autoloaded options query takes, for example * [@pbearne](https://profiles.wordpress.org/pbearne/): Think that both [@markjaquith](https://profiles.wordpress.org/markjaquith/)‘ s and my fixes can be used as they work best for different configurations * [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/): Could we start adding a limit to the number of autoloaded options, say 250 rows? Or is the issue size in terms of memory? - [@pbearne](https://profiles.wordpress.org/pbearne/): If we can load just what we need, the SQL time is less - [@markjaquith](https://profiles.wordpress.org/markjaquith/): We do this to avoid hundreds of individual queries * [@rickjames](https://profiles.wordpress.org/rickjames/): Is “autoloading” the thing that PHP can do for include files? I thought it was so slow as to be better to always include everything - [@markjaquith](https://profiles.wordpress.org/markjaquith/): No, this is about quering the `wp_options` table for `autoload = 'yes'` * [@rickjames](https://profiles.wordpress.org/rickjames/): That gets to the lack of adequate indexes for the `wp_options` table; a simple change can speed up ` SELECT`s - [@markjaquith](https://profiles.wordpress.org/markjaquith/): There’s already an index, it’s more about the volume of data being transferred * [@eugenemanuilov](https://profiles.wordpress.org/eugenemanuilov/): Think we should move from defining which option is autoload-able in the database table to the option registration in WP, so a plugin/theme owner will need to register an option similarly to how settings are registered with `register_setting` and define whether an option is autoload-able there * [@flixos90](https://profiles.wordpress.org/flixos90/): Both proposals at a high level have the idea of querying what is needed, but the newer proposal does it globally while still keeping a single place of storage while the latter was aimed at having different “options lists” per template/page. The latter would be great, but it comes with heavy storage implications, so the newer proposal is probably the best place to start since it has no additional storage implications. * [@markjaquith](https://profiles.wordpress.org/markjaquith/): Do think that the issue is data, not rows – evicting autoloaded options could help wtih both * [@rmccue](https://profiles.wordpress.org/rmccue/): Have run into performance problems with pulling autoloaded options from object cache, so agreed that this is an issue * [@markjaquith](https://profiles.wordpress.org/markjaquith/): Also issue with memcache’s default config being size-limited * [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/): Could we use ` register_settings` to define if an option should be autoloaded? - [@markjaquith](https://profiles.wordpress.org/markjaquith/): Won’t help existing sites * [@rmccue](https://profiles.wordpress.org/rmccue/): CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. problem is that `autoload` is true by default, which is what causes issues * [@markjaquith](https://profiles.wordpress.org/markjaquith/): Two approaches – [@pbearne](https://profiles.wordpress.org/pbearne/) optimized for “literally just what this page needs”; my POC was for “never autoload things that aren’t used” * [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/): So will we store an array of used options in options table? - [@markjaquith](https://profiles.wordpress.org/markjaquith/): Current implementation only stores timestamp of last calibration, but with some additional storage we could minimize dynamic re-adding of autoloaded options * [@rmccue](https://profiles.wordpress.org/rmccue/): Autoloading options should minimize DB/cache calls, but not necessarily replace them. The heuristic of what _should_ be autoloaded is key to this proposal. - [@markjaquith](https://profiles.wordpress.org/markjaquith/): To me, it’s “ things that are used and aren’t unreasonably large.” Can also honor `autoload ='no'` while not honoring `autoload='yes'` as chosen by developers. * [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/): Don’t love the idea of storing an array of keys. How do you generate the array? What is the average page load? * [@rmccue](https://profiles.wordpress.org/rmccue/): To move forward, we need a concrete proposal for how the heuristic works. Will look into the networknetwork( versus site, blog) saturation problems we’ve run into get an idea of what “unreasonable” might lok like. * Next steps: [@markjaquith](https://profiles.wordpress.org/markjaquith/) will work on detailing the heuristic further in [#526](https://github.com/WordPress/performance/issues/526) and when it’s ready, we’ll schedule another discussion for a future chat **Our next chat will be held on [Tuesday, September 27, 2022 at 11am EDT](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20220927T1500) in the [#core-performance channel](https://wordpress.slack.com/messages/core-performance/) in [Slack](https://make.wordpress.org/chat/).** [#core-js](https://make.wordpress.org/core/tag/core-js/), [#core-media](https://make.wordpress.org/core/tag/core-media/), [#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/), [#hosting-community](https://make.wordpress.org/core/tag/hosting-community/) [#meta](https://make.wordpress.org/core/tag/meta/) [ ](https://profiles.wordpress.org/mxbclang/) [Bethany Chobanian Lang](https://profiles.wordpress.org/mxbclang/) 4:07 pm _on_ August 16, 2022 Tags: [core-js ( 131 )](https://make.wordpress.org/core/tag/core-js/), [core-media ( 116 )](https://make.wordpress.org/core/tag/core-media/), [hosting-community ( 31 )](https://make.wordpress.org/core/tag/hosting-community/), meta, [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 16 August 2022](https://make.wordpress.org/core/2022/08/16/performance-team-meeting-summary-16-august-2022/)󠁿 [Meeting agenda here](https://make.wordpress.org/core/2022/08/15/performance-chat-agenda-16-august-2022/) and the full chat log is available [beginning here on Slack](https://wordpress.slack.com/archives/C02KGN5K076/p1660662019930129). ## Announcements * [@mxbclang](https://profiles.wordpress.org/mxbclang/): [Team Rep nominations reminder](https://make.wordpress.org/performance/2022/08/09/core-performance-team-rep-nominations/) * [@mxbclang](https://profiles.wordpress.org/mxbclang/): Offline August 22 – September 9 ## Focus group updates ### Images [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/) [@mikeschroder](https://profiles.wordpress.org/mikeschroder/) [GitHub project](https://github.com/WordPress/performance/projects/1) * [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/): Continued work refining our follow up patches for the multi-mime/WebP feature - Ready: [Fixes for unit tests](https://github.com/WordPress/wordpress-develop/pull/3060) - Nearing completion: * [Updating “add_image_size” to support mime types](https://github.com/WordPress/wordpress-develop/pull/3028) * [Plugin integration points](https://github.com/WordPress/wordpress-develop/pull/3036) * [Edit/restore flows multi-mime support](https://github.com/WordPress/wordpress-develop/pull/3030)– ready for review * [Shim for non-supporting browsers](https://github.com/WordPress/wordpress-develop/pull/3034)– ready for review * [PDF support](https://github.com/WordPress/wordpress-develop/pull/3048)– ready for review * Work to add support for multiple mime types across coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. media functions continues in [https://github.com/WordPress/wordpress-develop/pull/3074](https://github.com/WordPress/wordpress-develop/pull/3074)( for [https://core.trac.wordpress.org/ticket/56349](https://core.trac.wordpress.org/ticket/56349)) * [@joegrainger](https://profiles.wordpress.org/joegrainger/): Working on further updates and feedback on [Module Proposal: Regenerate Existing Images #445](https://github.com/WordPress/performance/issues/445) and core patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a **diff**. A patch can be _applied_ to a codebase for testing. for [Update core functions to support multiple mime types #3074](https://github.com/WordPress/wordpress-develop/pull/3074) * Follow-up on [SVG uploads](https://github.com/WordPress/performance/issues/427) - [Last week’s discussion](https://make.wordpress.org/core/2022/08/09/performance-team-meeting-summary-9-august-2022/) - [@pbearne](https://profiles.wordpress.org/pbearne/): We could support both by a toggle/filterFilter Filters are one of the two types of Hooks [https://codex.wordpress.org/Plugin_API/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. setting - @antelaca: Each of the third party solutions are using the same library for SVG sanitization, https://github.com/darylldoyle/svg-sanitizer. Idea is to use the same approach and simplify the implementation a bit using one class. - [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/): Some concerns on the original ticketticket Created for both bug reports and feature development on the bug tracker. about how effective the sanitizer is; are we willing to accept the risk of enabling SVGs? “Static” SVGs implies that there’s a blocked list of tags that’s excluded - [@masteradhoc](https://profiles.wordpress.org/masteradhoc/): Yes, but using a sanitizing library makes a lot of sense - [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/): Library looks well-tested. Maybe initial approach could enable only SVGs as images. * Follow-up on [Dominant Color in core](https://make.wordpress.org/core/2022/07/21/proposal-add-a-dominant-color-background-to-images/) - [@pbearne](https://profiles.wordpress.org/pbearne/): Flagged some feedback on that post - [@mxbclang](https://profiles.wordpress.org/mxbclang/): General concern seems to be that this is not actually a performance improvement but an improvement to UXUX User experience in terms of how a site _feels_ it’s performing - [@pbearne](https://profiles.wordpress.org/pbearne/): Found that it does provide a web vitals boost and believe it’s best practice - [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/): Agree that this helps perceived performance; though it may not have a measurable effect, how users experience a site is actually a performance concern so this is a real improvement. Other [technical concern was from David](https://make.wordpress.org/core/2022/07/21/proposal-add-a-dominant-color-background-to-images/#comment-43411) about potential bloating of the `meta` table, which we should respond to directly. [@pbearne](https://profiles.wordpress.org/pbearne/) will reply. #### Feedback requested * See above * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+project%3AWordPress%2Fperformance%2F1+label%3A%22Needs+Discussion%22)( 10 issues) ### Object Cache [@tillkruess](https://profiles.wordpress.org/tillkruess/) [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/) [GitHub project](https://github.com/WordPress/performance/projects/6) * [@tillkruess](https://profiles.wordpress.org/tillkruess/): Focused on getting the Object Cache Site Health test merged into core in https://github.com/WordPress/ wordpress-develop/pull/2890 with [@furi3r](https://profiles.wordpress.org/furi3r/); core developer feedback appreciated #### Feedback requested * See above * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F6+)( 3 issues) * [Needs Review](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Review%22+project%3AWordPress%2Fperformance%2F6+)( 1 issue) ### Site Health N/A [GitHub project](https://github.com/WordPress/performance/projects/4) * **We’re seeking 1-2 POCs for this group; if you’re interested, please comment here or pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of“ Ping me when the meeting starts.” in SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/)** * See above re: Object Cache Site Health check #### Feedback requested * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F4+)( 9 issues) ### Measurement N/A [GitHub project](https://github.com/WordPress/performance/projects/5) * **We’re seeking 1-2 POCs for this group; if you’re interested, please comment here or ping in Slack** * [@mxbclang](https://profiles.wordpress.org/mxbclang/): Reminder about the performance testing environment work started back in March: https://make.wordpress.org/core/ 2022/03/22/performance-team-meeting-summary-22-march-2022/. This has stalled out since then; if anyone is interested in picking it back up, let us know. #### Feedback requested * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F5+)( 5 issues) * [Needs Review](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Review%22+project%3AWordPress%2Fperformance%2F5+)( 1 issue) ### JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. 󠀁[https://www.javascript.com](https://www.javascript.com/)󠁿 [@aristath](https://profiles.wordpress.org/aristath/) [@sergiomdgomes](https://profiles.wordpress.org/sergiomdgomes/) [GitHub project](https://github.com/WordPress/performance/projects/3) * [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/): For the preload resources work, proposed a new, more declarative way to specify preloads in https://github.com/WordPress/wordpress-develop/pull/3089; appreciate any feedback. #### Feedback requested * [Tree-shaking block styles on the frontend #41020](https://github.com/WordPress/gutenberg/pull/41020) * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F3+)( 2 issues) * [Needs Review](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Review%22+project%3AWordPress%2Fperformance%2F3+)( 3 issues) ## Infrastructure [@flixos90](https://profiles.wordpress.org/flixos90/) [GitHub project](https://github.com/WordPress/performance/projects/2) * N/A #### Feedback requested * See above * [Needs Discussion](https://github.com/WordPress/performance/issues?q=is%3Aopen+label%3A%22Needs+Discussion%22+project%3AWordPress%2Fperformance%2F2+)( 5 issues) * [Needs Review](https://github.com/WordPress/performance/issues?q=is%3Aopen+project%3AWordPress%2Fperformance%2F2+label%3A%22Needs+Review%22+)( 3 issues) ## Open Floor * [@olliejones](https://profiles.wordpress.org/olliejones/): There’s a[ Site Health and Troubleshooting plugin](https://wordpress.org/plugins/health-check/), and similar but not identical functionality in core. Is there any plan to incorporate that 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/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. into core? Or do Performance Lab modules need to target both environments? - [@mxbclang](https://profiles.wordpress.org/mxbclang/): Someone manages that plugin, but not sure who; might be worth asking in the [#meta](https://make.wordpress.org/core/tag/meta/) channel **Our next chat will be held on [Tuesday, August 23, 2022 at 11am EDT](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20220823T1500) in the [#core-performance channel](https://wordpress.slack.com/messages/core-performance/) in [Slack](https://make.wordpress.org/chat/).** [#core-js](https://make.wordpress.org/core/tag/core-js/), [#core-media](https://make.wordpress.org/core/tag/core-media/), [#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/), [#hosting-community](https://make.wordpress.org/core/tag/hosting-community/) [ ](https://profiles.wordpress.org/danfarrow/) [Dan Farrow](https://profiles.wordpress.org/danfarrow/) 2:53 pm _on_ March 25, 2021 Tags: [core-css ( 192 )](https://make.wordpress.org/core/tag/core-css/), meta, [summary ( 981 )](https://make.wordpress.org/core/tag/summary/)    # 󠀁[CSS Chat Summary: 18 March 2021](https://make.wordpress.org/core/2021/03/25/css-chat-summary-18-march-2021/)󠁿 [The meeting took place here on Slack](https://wordpress.slack.com/archivesj/CQ7V4966Q/p1616104974005200). [@notlaura](https://profiles.wordpress.org/notlaura/) facilitated and [@danfarrow](https://profiles.wordpress.org/danfarrow/) wrote up these notes. ## Housekeeping * Following last week’s discussion we agreed that, from 01 April onwards, the meeting time will advance from 10pm to 9pm UTC to accommodate daylight saving time * The bugscrub time will similarly be brought forward one hour from 01 April onwards ## Project updates ### CSSCSS Cascading Style Sheets. audit (󠀁[#49582](https://core.trac.wordpress.org/ticket/49582)󠁿) * [@ryelle](https://profiles.wordpress.org/ryelle/)‘s audit tool is nearly ready to share with the wider community once the “container audit” feature is in place * The PostCSS PR is tested & ready to merge. UPDATE: Now merged, thanks [@ryelle](https://profiles.wordpress.org/ryelle/)! * [@notlaura](https://profiles.wordpress.org/notlaura/) asked if the tool is ready to have its repo moved into the WordPress org. [@ryelle](https://profiles.wordpress.org/ryelle/) will ask in [#meta](https://make.wordpress.org/core/tag/meta/) ### Colour scheming (󠀁[#49999](https://core.trac.wordpress.org/ticket/49999)󠁿) * We will have another mock-up share at the next meeting (25 March). If you’re able to please bring a mock-up of a component of your choice using custom properties * [@ryelle](https://profiles.wordpress.org/ryelle/) reported having [updated her mockup](https://codepen.io/ryelle/project/editor/AooEky) to use a roughly `--prefix--location--property--state` naming pattern e.g. `-- wp-admin--button-primary--hover` * In [@ryelle](https://profiles.wordpress.org/ryelle/)’s example some custom properties are derived from other custom properties e.g. `--wp-admin--button-secondary-- text: var(--wp-admin--button-primary)`. Users could override these derived values as required ## Open Floor + CSS Link Share * [@notlaura](https://profiles.wordpress.org/notlaura/) shared [this Lea Verou article](https://lea.verou.me/2020/07/the-cicada-principle-revisited-with-css-variables/) describing a way to create apparant organic randomness in CSS using prime numbers&` nth-child`, * [@danfarrow](https://profiles.wordpress.org/danfarrow/) shared [this Kevin Powell video](https://www.youtube.com/watch?v=McC4QkCvbaY) introducing the CSS `is()` pseudo-class & how it can reduce selector complexity * [@notlaura](https://profiles.wordpress.org/notlaura/) shared [this page of anti-racism resources](https://wwhatsup.wordpress.com/2021/03/18/stop-asian-hate-and-aapi-solidarity-resources/), following the tragic attacks in northeast Atlanta, Georgia With that the meeting drew to a close. Thanks everyone! [#core-css](https://make.wordpress.org/core/tag/core-css/), [#summary](https://make.wordpress.org/core/tag/summary/) # Post navigation [← Older posts](https://make.wordpress.org/core/tag/meta/page/4/?output_format=md) [Newer posts →](https://make.wordpress.org/core/tag/meta/page/2/?output_format=md)