Load Combined Core Block Assets
This is a workaround for sites experiencing any issues with the ability introduced in WordPress 6.9 to load block styles on demand in classic themes. The known issues have been fixed during the 7.0 release cycle with the following commits: r61076: Script Loader: Fall back to hoisting late-printed styles to end of HEAD if wp-block-library is not enqueued. r61122: Script Loader: Load block styles on demand in classic themes even when wp-block-styles support is absent. r61174: Script Loader: Improve hoisted stylesheet ordering (in classic themes) to preserve CSS cascade. r61554: Script Loader: Preserve original CSS cascade for classic themes when hoisting late-printed styles. r61945: Script Loader: Refine hoisted stylesheet ordering to preserve original CSS cascade in classic themes. If running a classic theme (i.e. not a block theme), this plugin filters should_load_separate_core_block_assets to be false. 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 7.0. At any time, you can test whether any issues remain by adding ?should_load_separate_core_block_assets=true to any frontend URL; this restores the default behavior in WP 6.9. This workaround should be 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 wp-block-library stylesheet. Loading separate block styles on demand reduces the amount of CSS which should improve page load time. Nevertheless, as explained in the dev note, some sites may be built in a way that fundamentally does not work with loading separate block styles on demand. For these sites, this plugin is available to retain the old behavior.
Site Speed Test – SpeedGuard
Track Core Web Vitals for the entire website and for individual URLs. Mobile and Desktop. Every day. Automatically. For free. No need to guess whether your website performance needs your attention or not – you will get the definite answer in your WordPress Dashboard in a few minutes. With SpeedGuard you get: Core Web Vitals (LCP, CLS, INP) testing for individual URLs of your website PageSpeed Insights (LCP, CLS) for the cases if your website doesn’t have Core Web Vitals yet automatic everyday monitoring both desktop and mobile testing links to the Google PageSpeed Insights reports (that include CWV on top as well) which you can pass to the performance engineer to improve your site speed tests are completely automated — you don’t need to do anything easy to use — just pick pages of your website that you would like to monitor It’s free 🙂 Test performance of any content in WordPress : Posts Pages Events WooCommerce Products any other Custom Post Type Archives Categories Tags any other Custom Taxonomy Idea Behind There is no need to say that performance IS very important. What’s also important — is to understand whether you have to worry about your website performance or it’s doing fine. Google Core Web Vitals are the metrics that Google uses to measure the user experience on the web (real user experience!). If your website passes CWV assessment for Origin — it means that your website is fast enough for the majority of users. If it doesn’t pass — it means that you have to fix this. If it does pass but quite a few specific URLs are not passing — it’s a good time to look into those URLs and improve them to prevent the entrire webstie to be marked as failing CWV. I wanted a simple easy-to-use tool to warn me in case my clients’ websites performance has a bad tendency and needs my attention. I wanted a native WordPress solution, with all information available from the dashboard, simple but still informative, a guard who will do the monitoring every day and ping me, in case something goes wrong. I have not found one and that’s why I’ve built this plugin. I’ll be happy to know that you find it useful as well — please, leave a review. P.S. Note about PageSpeed Insights: you SHOULD always use CWV data in case it is available for your website. In case it is not available (when the website is new and/or doesn’t have enough traffic yet) — use PageSpeed Insights. But you have to remember, that PSI — are lab tests, it’s just an emulation of real users experience. It’s better than nothing, of course. Watch my talk here if you want to understand Core Web Vitals Mystery better.
