Performance Chat Summary: 10 February 2026

The full chat log is available beginning here on Slack.

WordPress Performance TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets

  • @westonruter shared query, noting that there are currently 12 total tickets when including defects and enhancements, and 9 non-defect tickets specifically.
  • @westonruter pointed out that PR #10855, which improves the robustness of page cache detection logic in Site Health, could use another review.
  • @spacedmonkey shared that PR #10531 had just been approved and would be committed shortly.
    • @westonruter asked about a review comment on that PR regarding password-protected posts.
    • @spacedmonkey replied that the current implementation does not account for password-protected posts, but functionally behaves the same as before, while now benefiting from using WP_Query.
    • @spacedmonkey added that switching to WP_Query opens up additional possibilities beyond caching, including filters and extensibility.
  • @westonruter also highlighted that the PR #9260 appears ready for commit and shared plans to commit it later that day.

Performance Lab PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party (and other performance plugins)

  • @westonruter shared that there had been no responses yet on the Performance Lab CODEOWNERS audit issue #2374.
    • @b1ink0 shared that they would like to be added as a CODEOWNER for the Modern Image Formats plugin, as well as for Site Health tests they had added or updated.
    • @westonruter replied that this sounded good and asked @b1ink0 to update the CODEOWNERS file directly in the PR to add themselves as appropriate.
  • @westonruter mentioned interest in merging the PR #2352 to better observe Copilot’s impact in practice.
  • @westonruter pointed out that there are several open View Transitions plugin PRs that still need review.
    • @b1ink0 shared that they plan to address recent feedback on PR #2336 by the end of the week.

Open Floor

  • @westonruter raised a question about whether the GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/ SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. integration for the Performance repository is proving helpful or if it is becoming too noisy, noting a personal impression that it may be more noise than signal.
    • @b1ink0 shared that the integration feels noisy, particularly due to Dependabot pull requests.
    • @westonruter experimented during the meeting with subscribing and unsubscribing from the GitHub integration and observed that Slack does not currently support filtering out Dependabot notifications.
    • @westonruter suggested that creating a separate “firehose” channel could be an option if the team wants to preserve visibility without overwhelming the main channel, while also noting that they are already subscribed to all issues and pull requests directly in the repository.

Our next chat will be held on Tuesday, February 24, 2026 at 16:00 UTC in the #core-performance channel in Slack.

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

Performance Chat Summary: 27 January 2026

The full chat log is available beginning here on Slack.

WordPress Performance TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets

  • @westonruter shared a Trac query covering performance-related tickets milestoned for WordPress 6.9.1 and 7.0.
  • @westonruter shared that for ticketticket Created for both bug reports and feature development on the bug tracker. #61500, some work was done recently as part of the CodeMirror upgrade effort.
    • @westonruter explained that ideally there would be a declarative way to add script modules as dependencies for classic scripts, and noted that a workable approach is to register an empty script module that declares module dependencies, and then enqueue that module whenever the classic script is enqueued. @westonruter shared reference to example diffs demonstrating this workaround and mentioned being glad to find a quick solution.
  • @mukesh27 asked whether @westonruter had reviewed the latest comment on #64229, where @wildworks raised a minor point and opened a PR.
    • @westonruter replied that the comment had been seen the night before and initially mentioned not having a 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. yet, then noted that a PR already existed and shared PR #10799. @westonruter reviewed the PR, said it looked good, and approved it.
  • @westonruter brought up #64066 and shared that @gilbertococchi is actively working on collecting data to support switching to moderate prefetch by default on sites with caching.
    • @westonruter referenced a Slack thread where LCP passing rates for conservative versus moderate prefetch were discussed and noted that additional data is being gathered by flipping a few CrUX-eligible sites from conservative to moderate to compare LCP passing rates and page hit increases over time.
    • @westonruter added that landing #64066 is related to #64370, noting that the latter needs to land to ensure reliable detection.
  • @mukesh27 asked about the review status of PR #10606 and mentioned seeing comments from @westonruter.

Performance Lab PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party (and other performance plugins)

Open Floor

  • @westonruter shared recent experience using GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/ Copilot together with Gemini CLICLI Command Line Interface. Terminal (Bash) in Mac, Command Prompt in Windows, or WP-CLI for WordPress. locally, describing it as immensely useful both for review and implementation work. @westonruter described Copilot as significantly better than a traditional linter during reviews and noted that it can provide strong first-pass implementations. @westonruter shared PR #10778 as an example of using Gemini CLI during the CodeMirror upgrade and explained that a detailed historical and technical specification was provided to the tool.
    • @westonruter also shared that Copilot was used to draft a Performance Lab fix while on public transit using only a phone, referencing PR #2346.
    • @dmsnell cautioned that Copilot can sometimes reintroduce defects during PR reviews, sharing an anecdote where Copilot repeatedly flagged and reintroduced a PCRE-related 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. even after it had been fixed.
    • @justlevine added that this behavior can indicate ambiguities in code and suggested that improving self-documentation helps both humans and LLMs.
    • @dmsnell emphasized the need for extra care when LLMs introduce defects, as they can confidently repeat mistakes if the surrounding code does not change enough.
    • @westonruter agreed, noting that while hallucinations occur, the tools still provide good feedback most of the time and help shift focus away from minutiae like coding standards toward higher-level problem solving.
  • @dmsnell raised the topic of memoizing wp_normalize_path, noting observed performance improvements of roughly 1ms during WordPress startup in certain environments. @dmsnell explained that while this is a micro-optimization, it can have meaningful impact at scale and shared that @josephscott has been investigating early startup costs using production measurements. @dmsnell mentioned having tested earlier versions without caching and discussed trade-offs between caching and alternative approaches, including replacing PCRE calls and addressing what may be a latent bug.
    • @westonruter asked whether similar performance benefits were observed across different approaches.
    • @dmsnell replied that while direct testing had not yet been done for all variants, prior comparisons suggested the cache provided most of the benefit at a fraction of the cost, and that both approaches could potentially coexist.
    • @westonruter summarized this as a “both/and” situation rather than an either/or choice.

Our next chat will be held on Tuesday, February 10, 2026 at 16:00 UTC in the #core-performance channel in Slack.

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

Performance Chat Summary: 13 January 2026

The full chat log is available beginning here on Slack.

WordPress Performance TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets

  • @westonruter shared that an issue related to Modern Image Formats in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. had surfaced, pointing to #60480.
  • @westonruter shared the reports covering performance-related tickets for WordPress 6.9.1 and 7.0 specifically enhancements/features.
    • @westonruter highlighted #64066 as potentially the most impactful open ticketticket Created for both bug reports and feature development on the bug tracker., which proposes changing Speculative Loading’s default eagerness from conservative to moderate when caching is detected. @westonruter noted that no negative feedback has been received so far but acknowledged the change could be controversial and planned to ask for additional feedback in the #hosting channel.
  • @mukesh27 asked about the status of the Adminadmin (and super admin) View Transitions work. @westonruter replied that this is tracked in #64470, with an active PR #10699 opened by @flixos90.
    • @westonruter shared that the change looks close to being ready, but an unexpected E2E test failure still needs investigation. @mukesh27 shared that the implementation looks solid overall, and @westonruter mentioned he had merged the latest trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. changes and planned further debugging, including testing behavior with unminified scripts if the failure persists.

Performance Lab PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party (and other performance plugins)

  • @SarthakJaiswal shared that he has been working on PR #2321, plans to review feedback, and will implement required changes soon, while also asking whether there are additional polishing improvements worth considering.

Open Floor

Our next chat will be held on Tuesday, January 27, 2026 at 16:00 UTC in the #core-performance channel in Slack.

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

Performance Year-End Chat Summary: 23 December 2025

The full chat log is available beginning here on Slack.

View Transitions to CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.

  • @westonruter kicked off the discussion by referencing plans to graduate the View Transitions plugin into core for WordPress 7.0, noting it pairs well with the adminadmin (and super admin) refresh and introduces theme support for configuration.
    • @mikewpbullet raised concerns about potential clashes with plugins or custom code and suggested a UIUI User interface checkbox or update splash screen guidance, while @schmitzoide proposed a general “Activate Advanced Features” checkbox.
    • @adamsilverstein noted performance plugins could add controls.
    • @westonruter clarified that sites could opt out via code toggles like filters or theme support, aligning with WordPress philosophy of decisions over options.
  • Update: See #64470 and #64471.

Speculative Loading and Caching Enhancements

  • @westonruter highlighted ticketticket Created for both bug reports and feature development on the bug tracker. #64066 to shift default eagerness from conservative to moderate when caching is detected, aiding View Transitions by reducing link click delays.
    • @mikewpbullet raised concerns about page caching rarely helping admin performance and noted that server-side caching via nginxNGINX NGINX is open source software for web serving, reverse proxying, caching, load balancing, media streaming, and more. It started out as a web server designed for maximum performance and stability. In addition to its HTTP server capabilities, NGINX can also function as a proxy server for email (IMAP, POP3, and SMTP) and a reverse proxy and load balancer for HTTP, TCP, and UDP servers. https://www.nginx.com/. or Varnish often runs without WordPress plugins that Site Health could detect.
    • @westonruter explained that core’s Site Health test already accounts for proxy caches beyond just plugins and remains extensibleExtensible This is the ability to add additional functionality to the code. Plugins extend the WordPress core software. for improvement.
    • @adamsilverstein acknowledged that comprehensive coverage is impossible but emphasized WordPress’s advantage in rendering detection rules dynamically.
    • @schmitzoide asked whether Site Health could diagnose performance issues.
      • @westonruter added that Performance Lab includes additional tests for excessive blocking scripts and styles.
    • @westonruter responded to @mikewpbullet‘s earlier admin concerns with two ideas: enabling bfcache in the admin for smooth back/forward transitions #63636, and considering speculative loading for admin menu items on sites with object caching enabled.
      • @mikewpbullet raised concerns that users may not want cached admin pages when hitting back, and that object caching is unlikely to help with page load times in admin where slowness comes from 3rd party background requests.

Admin and Dashboard Performance

  • @adamsilverstein shared that tackling the Dashboard landing page is a priority for the new year and mentioned an existing performance ticket. @westonruter later identified ticket #55344 and suggested the Dashboard could leverage preload links for commonly-used resources like the edit post screen assets.
    • @westonruter connected this to ticket #57548 about retiring script and style concatenation in wp-admin, explaining the benefit would be effective preloading but noting that concatenation might still offer better performance without a primed cache, which requires benchmarking. This discussion led to exploring Compression Dictionaries, a newer capabilitycapability 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). that @westonruter explained allows browsers to reuse intersecting portions of different concatenated bundles.
    • @mikewpbullet questioned the need given server-side Brotli compression already exists.
    • @westonruter clarified this isn’t about PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher-based gzip but about the new compression dictionary transport standard that enables reusing cached bundle portions across different pages, particularly beneficial for blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. themes enqueue block styles on-demand based on page content, and in WordPress 6.9 this also applies to classic themes, so compression dictionaries would allow concatenating these varying bundles while enabling browsers to cache and reuse individual styles across pages with different bundles, significantly reducing CSSCSS Cascading Style Sheets. downloads for both logged-in and logged-out users.

Roadmap and Future Planning

  • @schmitzoide asked about the team’s roadmap. @westonruter linked to the 2024 roadmap and explained this meeting serves to shape 2026 priorities, noting they’ll likely use milestoned TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets rather than a full roadmap post given fewer active contributors currently.
    • @schmitzoide asked about graduating additional Performance Lab features and shared plans to propose ideas from block theme optimization work via repository tickets. @adamsilverstein encouraged opening issues for any PerfNow conference ideas worth experimenting with 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/ or can be cost-based plugin from a third-party.
  • @sirlouen asked about integrating performance testing activities similar 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/’s approach, including GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/ Actions tagging and handbook expansion. @westonruter welcomed aligning testing strategies with other core teams in the new year.

Our next chat will be held on Tuesday, December 30, 2025 at 16:00 UTC in the #core-performance channel in Slack.

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

Performance Chat Summary: 16 December 2025

The full chat log is available beginning here on Slack.

WordPress Performance TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets

  • @westonruter shared that he is still working through fixes for a CSSCSS Cascading Style Sheets. issue introduced in WordPress 6.9 related to loading separate 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. styles on demand in PR #10601.

Performance Lab PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party (and other performance plugins)

  • @westonruter noted that several PRs needs to be reviewed.
  • @b1ink0 asked for feedback regarding the planned sunsetting of the Web Worker Offloading plugin issue #2284.

Open Floor

  • @westonruter shared that Safari now supports measuring the LCP metric, which he said will meaningfully improve URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org Metric collection for Optimization Detective
    • @spacedmonkey wondered whether the team could begin running the performance coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. e2e tests against Safari now that the browser includes this capabilitycapability 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)..
  • @westonruter added that he is interested in exploring Compression Dictionaries after learning they can be implemented in PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher with relatively little effort referenced article.
  • @b1ink0 shared information regarding the final 2025 meeting to discuss the 2026 roadmap, scheduled for December 23, 2025.

Our next chat will be held on Tuesday, December 30, 2025 at 16:00 UTC in the #core-performance channel in Slack.

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

Performance Chat Summary: 7 October 2025

The full chat log is available beginning here on Slack.

WordPress Performance TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets

  • @westonruter mentioned ticketticket Created for both bug reports and feature development on the bug tracker. #63636 related to BFCache was punted due to an unresolved Chromium 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. around Clear-Site-Data: "cache" headers.
  • @westonruter identified ticket #43258 on output buffering as the current biggest blockerblocker A bug which is so severe that it blocks a release.. He explained that while there’s been significant discussion both on the PR #8412 and in Slack, the debate centers around the trade-offs between enabling full-page buffering (to allow post-render optimization) versus keeping the door open for streaming, which could improve initial load performance. He provided further context on how classic themes already stream via procedural rendering, while 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 generally do not.
    • @westonruter noted that while streaming isn’t widely adopted in WordPress today, it could become valuable in the future, and care should be taken not to block its evolution. He also shared a WPDirectory search of flush() usage across coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., noting they appear mostly in adminadmin (and super admin) and XML-RPC contexts rather than template rendering.
    • @westonruter asked if anyone has insights into this area and can contribute thoughts on how we can bridge these two perspectives, allowing for a default output buffer while also enabling streaming if the application wants it. He’d be most thankful.
  • @b1ink0 brought up PR #9867 related to footer script module support and noted that @jonsurrell had provided thoughts around dependency handling.

Performance Lab PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party (and other performance plugins)

  • @westonruter mentioned new guidance on AI-generated contributions now available in the Performance repo, including a new AGENTS.md file and updated PR template instructions with PR #2193. He explained that this was prompted by a recent increase in AI-assisted PRs, some of which indicated the AI’s output wasn’t being carefully reviewed by the contributor.

Open Floor

  • @westonruter introduced Trac ticket #64066, proposing that WordPress default to moderate eagerness for Speculative Loading, when caching is detected. He noted the idea could provide a performance boost in WordPress 7.0 by improving preload efficiency on cached sites, but also acknowledged the need to weigh sustainability concerns around increased server load.
    • @mukesh27 asked whether a second opinion was needed, and whether any Google team members had provided feedback.
    • @westonruter replied that he had received positive input from Google, though their priorities don’t always align with those of hosts and site owners. He noted that moderate eagerness can increase bandwidth usage due to unnecessary preloads and may lead to added hosting costs.
    • @gilbertococchi shared his thoughts, emphasizing that moderate eagerness could be significantly more impactful than conservative loading, especially with Chrome’s recent introduction of a Viewport Heuristic, but stressed the importance of safeguards like persistent object caching to mitigate server load.
    • @mukesh27 summarized that @gilbertococchi was supportive of the proposal and encouraged moving the ticket into the 6.9 milestone for visibility.
    • @westonruter clarified that while he wasn’t necessarily aiming for inclusion in 6.9, he agreed to milestone the ticket for tracking purposes, with the understanding that it may still be punted.

Our next chat will be held on Tuesday, October 21, 2025 at 15:00 UTC in the #core-performance channel in Slack.

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

Performance Chat Summary: 23 September 2025

The full chat log is available beginning here on Slack.

WordPress Performance TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets

  • @westonruter shared that PR #8412 has tests added and is ready for review, though he still needs to update the description and remove the draft status.
  • @westonruter enquired about PR #9867, which enables printing script modules in the footer.
    • @b1ink0 added that work is currently underway to implement sorting behavior for script modules and their dependencies.
  • @westonruter enquired about coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. milestone #63012 regarding theme CSSCSS Cascading Style Sheets. minification.
    • @b1ink0 mentioned having a POC (minification only for blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. themes) to partially address #63012 and is working with @shyamgadde on a POC addressing the remaining points, with plans to raise PRs in the coming week.
  • @westonruter mentioned PR #9770 to iterate on fetchpriority for script modules, to allow enqueued script modules to influence the priority of dependencies (or vice versa, which is not yet totally clear).

Performance Lab PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party (and other performance plugins)

Open Floor

  • @westonruter shared that there may be a blockerblocker A bug which is so severe that it blocks a release. preventing ticketticket Created for both bug reports and feature development on the bug tracker. #63636 from being a good candidate for WordPress 6.9. The issue relates to 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. in Chrome where sending the Clear-Site-Data 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. such as during logout can slow down page performance. While this approach is preferable to using pageshow to invalidate the bfcache, the Chrome bug may require postponing the feature to 7.0.
  • @khoipro suggested adding a filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. to exclude certain taxonomies from slow term-count queries in large projects.
    • @johnbillion noted that while the suggestion didn’t seem directly related, two recent fixes in WordPress 6.9 have already reduced unnecessary term recounting #42522 and #63562.

Our next chat will be held on Tuesday, October 7, 2025 at 15:00 UTC in the #core-performance channel in Slack.

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

Performance Chat Summary: 9 September 2025

The full chat log is available beginning here on Slack.

WordPress Performance TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets

Performance Lab PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party (and other performance plugins)

  • @westonruter flagged that the Optimization Detective plugin is overdue for a release but likely won’t ship before 6.9-beta1 due to focus on Core enhancements.
    • @westonruter reminded that getting the 1.0.0 stable release out is blocking next milestone, which includes the work @b1ink0 is doing on URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org Metrics priming.

Open Floor

  • @mukesh27 inquired about the date of the next 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 and @westonruter confirmed it is scheduled for next Tuesday (16 September 2025).

Our next chat will be held on Tuesday, September 23, 2025 at 15:00 UTC in the #core-performance channel in Slack.

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

Performance Chat Summary: 12 August 2025

The full chat log is available beginning here on Slack.

WordPress Performance TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets

Performance Lab PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party (and other performance plugins)

  • @westonruter announced that the next Performance Lab release will include an adminadmin (and super admin) pointer for the View Transitions plugin PR #2122.
    • @b1ink0 asked whether to release Performance Lab now or wait until PR #2059 is ready, as it needs a round of review. @westonruter suggested waiting so that the release can go out next week before WCUS.
  • @westonruter also noted that the admin pointer should be omitted if View Transitions is already active (Issue #2136) and mentioned PR #2119, which proposes adding the No-cache BFCache plugin as a new feature to Performance Lab.

Open Floor

Our next chat will be held on Tuesday, August 26, 2025 at 15:00 UTC in the #core-performance channel in Slack.

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

Performance Chat Summary: 29 July 2025

The full chat log is available beginning here on Slack.

WordPress Performance TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets

  • @westonruter highlighted the PR (#8815) for fetchpriority as one of the WordPress 6.9 roadmap items that still requires an approving review preferably from someone familiar with the script loader component, for example especially the work on adding async/defer, as it builds on that effort.

Performance Lab PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party (and other performance plugins)

Our next chat will be held on Tuesday, August 12, 2025 at 15:00 UTC in the #core-performance channel in Slack.

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