Weston Ruter

This is a temporary workaround for sites experiencing any issues with WordPress 6.9’s new ability to <a href="https://make.wordpress.org/core/2025/11/18/wordpress-6-9-frontend-performance-field-guide/#load-block-styles-on-demand-in-classic-themes" rel="nofollow ugc">load block styles on demand in classic themes</a>, for example <a href="https://core.trac.wordpress.org/ticket/64354" rel="nofollow ugc">#64354</a>.
If running a classic theme (i.e. not a block theme), it filters <code>should_load_separate_core_block_assets</code> to be <code>false</code>. This has the effect of reverting a change introduced in 6.9 where classic themes now load separate core block assets on demand by default.
Note that this plugin should be considered temporary until any issues are resolved in 6.9.1. At any time, you can test whether any issues remain by adding <code>?should_load_separate_core_block_assets=true</code> to any frontend URL; this restores the default behavior in WP 6.9.
This workaround is temporary because there are performance benefits to loading separate core block assets. They can be loaded on demand just when they are used, as opposed to loading the large single combined <code>wp-block-library</code> stylesheet. Loading separate block styles on demand reduces the amount of CSS which should improve page load time.

Load Combined Core Block Assets

Temporary workaround for sites experiencing issues with WordPress 6.9's new ability to load block styles on demand in classic themes.

Load Combined Core Block Assets vs Autoptimize