WordPress 6.7, released in May 2026, is one of the most performance-focused releases in recent memory. While most WordPress releases include minor optimisations, 6.7 targets specific performance bottlenecks that previously required third-party plugins. Here is what changed and what still needs external optimisation.

Database query improvements

Term queries

The term query system (used for categories, tags, and custom taxonomies) received a significant rewrite. Previously, querying posts by taxonomy involved multiple joins that scaled poorly with large term counts. The new implementation uses a more efficient join strategy:

// Before 6.7: this query touched multiple join tables
$query = new WP_Query([
    'category_name' => 'hosting',
    'tag' => 'vps',
]);

// After 6.7: same query, fewer joins, ~40% faster on sites with 10,000+ posts

Sites with many categories and tags (ecommerce, news, directories) will see the largest improvement. Benchmarks show ~30-40% faster term queries on sites with 50,000+ posts.

Autoloaded options

WordPress stores configuration values in the wp_options table. Options marked “autoload” are loaded on every request. Before 6.7, large autoloaded option sets could add 50-200ms to every uncached page load.

WordPress 6.7 introduces intelligent autoload splitting. Options are now batched into multiple queries when the total autoloaded data exceeds a threshold (1 MB by default). This prevents the “all or nothing” autoload problem where one large option (like a cached page builder config) bloated the autoload payload.

Site Health now warns when autoloaded options exceed 900 KB and lists the largest offenders.

Script loading improvements

Deferred and async by default

WordPress 6.7 adds native support for defer and async script loading strategies through a new wp_register_script parameter:

wp_register_script('my-plugin', 'script.js', [], '1.0', [
    'strategy' => 'defer', // or 'async'
]);

The Block Editor (Gutenberg) now registers its scripts with defer by default. This is a meaningful improvement — Gutenberg loads significant JavaScript, and deferring it prevents render-blocking.

Script module support

WordPress 6.7 officially supports ES modules for registered scripts. This enables modern JavaScript loading patterns without bundling:

wp_register_script('my-module', 'module.js', [], '1.0', [
    'type' => 'module',
]);

This is a developer-facing feature rather than a performance win on its own, but it enables smaller, more efficient JavaScript delivery once themes and plugins adopt it.

Native lazy loading for iframes

WordPress has lazy-loaded images since 5.5. Version 6.7 extends this to iframes (YouTube embeds, maps, third-party widgets). WordPress automatically adds loading="lazy" to iframes in post content.

This is a meaningful improvement for content-heavy sites. A blog post with three YouTube embeds previously loaded all three video players on page load. Now, only the first visible embed loads; the rest wait until the user scrolls.

What still needs plugins

WordPress 6.7 does not replace:

  • Page caching: Still requires a caching plugin or server-level caching (FastCGI cache, Varnish)
  • Object caching: Redis/Memcached integration still requires a plugin and server configuration
  • Image optimisation: WordPress does not convert images to WebP/AVIF or compress them beyond the default JPEG quality
  • Database cleanup: Post revisions, expired transients, and orphaned metadata still accumulate
  • Script concatenation: Combining multiple CSS/JS files still requires a plugin or build step

The core team’s philosophy is to improve WordPress’s own code rather than adding features that overlap with the plugin ecosystem. Page caching isn’t coming to core — it is better handled at the server level or by dedicated caching plugins.

Should you upgrade immediately?

Yes. WordPress 6.7 is a performance release with no breaking changes. The database query improvements, autoloaded option handling, and lazy-loaded iframes are all improvements you get for free by upgrading.

Before upgrading:

  1. Back up your site (database + files)
  2. Update all plugins and themes to their latest versions
  3. Run the update
  4. Check Site Health for any new warnings (especially the autoloaded options warning)

The update takes under a minute for most sites. The performance improvements are immediate.

The trend

WordPress core performance has improved steadily since 5.9 in 2022. Each release chips away at the need for third-party optimisation plugins. In 2026, a WordPress site with a decent caching strategy (page cache + object cache) and WordPress 6.7 is significantly faster than the same site was two years ago — with fewer plugins doing the heavy lifting.

The long-term direction is clear: core handles the fundamentals (efficient queries, lazy loading, modern script loading), and specialised plugins handle the advanced cases (full-page caching, CDN integration, image optimisation). This is a healthy division of responsibility.