Meeting agenda here and the full chat log is available beginning here on Slack.

Announcements

• Welcome to our new members of #core-performance
• WordPress 6.5 Release Candidate 3 is today (Mar 19)
• Reminder on timezone difference for the next week, this chat will remain at 16:00 UTC and then shift to 15:00 UTC from April 2, 2024

Priority Items

Structure:

• WordPress performance Trac tickets
  • Current release
  • Future release
• Performance Lab plugin (and other performance plugins)
• Active priority projects
  • INP research opportunities
  • Improve template loading
  • Plugin checker

WordPress Performance Trac Tickets

• For WordPress 6.5:
  • No open items remain
• For Future Releases:
  • We already have 16 items in the 6.6 milestone (2 already closed)

Performance Lab Plugin (and other Performance Plugins)

• @mukesh27 for standalone plugins:
  • PRs that are ready for review:
    • PR #1048 – Support changing autoload value for largest autoloaded options
    • PR #1060 – Remove modules infrastructure
    • PR #1062 – Bump minimum required WP version to 6.4
• @thelovekesh https://github.com/WordPress/performance/pull/1033 just landed on trunk, now we have https://github.com/WordPress/performance/issues/1061 to brainstorm on release process for Performance Lab and standalone plugins
• @adamsilverstein Embed Optimizer is progressing towards release – https://github.com/WordPress/performance/pull/1059

Active Priority Projects

Plugin Checker

• No updates this week, will be removed from agenda moving forwards unless there are proactive updates on release 1.1

Improve template loading

• @thekt12 I should be able to raise a PR for review today, for #59600 including template part caching

INP research opportunities

• @adamsilverstein I have continued working on INP research in a colab nostly by querying httparchive data. Recently I added a few new queries that gather:
  • Plugins on WordPress sites with not good INP (based on Wapalyzer detection)
  • Long task scripts on WordPress sites with not good INP (using the long task audit)
  • Long task scripts on WordPress sites overall
• I then focused in on scripts by path and ran some group queries that only look at the path. Removing the host part ensures we catch common scripts that run across many WordPress sites. Finally, I am grouping by host to see if any 3p stand out at a top level. I’m collecting all the resulting data in a sheet and will soon be ready to summarize the findings in a doc and share everything!

Open Floor

• @thelovekesh Waiting for more feedback and/or approval – https://github.com/WordPress/performance/pull/981
• @joemcgill Friendly reminder that we’re still seeing a slight regression in 6.5 RCs. This week is the last chance we’ll have at correcting things, so if anyone has time to help review, I’d appreciate it.
• @thelovekesh I have one question reg. https://github.com/WordPress/performance/tree/trunk/build-cs build-cs directory in the PL plugin root. Was it added for standalone plugin tests purpose? I am not sure.
  • @mukesh27 For lint and phpstan https://github.com/WordPress/performance/blob/trunk/composer.json#L26-L28
• REMINDER: This meeting will continue at 16:00 UTC for the next 1 week, then it will switch to 15:00 UTC from April 2 onwards

Our next chat will be held on Tuesday, March 26, 2024 at 16:00 UTC in the #core-performance channel in Slack.

#core-performance, #performance, #performance-chat, #summary