Note: This option is available in the Pro version starting from v1.2.2.0. By default, Asset CleanUp Pro is disabled whenever a REST API call is made. As there is no front-end to optimize in this situation (e.g. nothing to alter on the HTML source code), it’s better to avoid triggering the code from the plugin […]
Category: Unload Rules
Is Asset CleanUp loading when Bricks Visual Site Builder is used? How to make the editor faster?
Note: This option is available in the Pro version 1.2.1.7. By default, Asset CleanUp Lite/Pro does not trigger when Bricks Visual Site Builder is used, more precisely when the following query string is in use: bricks=run. For instance, you might have an “About Us” page and it’s built using the “Bricks Visual Site Builder” theme. […]
How to unload or only load CSS/JS assets on all pages that have certain taxonomies (category, tag, etc.) set?
This feature is available in the Pro version starting from v1.2.0.5. This option is useful if you want to unload CSS/JS on specific post pages of any kind including, but not limited to: posts (their default well-known taxonomies are “Categories” and “Tags”), pages, custom post types such as WooCommerce’s “product” (it has “Product categories” and […]
Is Asset CleanUp loading when Divi Builder is used? How to make the editor faster?
Note: This option is available in the Pro version 1.1.9.2. By default, Asset CleanUp Lite/Pro does not trigger its unload rule when Divi’s builder is in use. Moreover, no extra Asset CleanUp Lite/Pro optimization rule takes place including minifying/combining CSS/JS. The reason behind it is to make sure that the editor will load perfectly fine, […]
Is Asset CleanUp loading when Oxygen’s Visual Site Builder is used? How to make the editor faster?
By default, Asset CleanUp Lite/Pro does not trigger when Oxygen’s Visual Builder is on, more precisely when the following query string is in use: ct_builder=true. For instance, you might have an “About Us” page and it’s built using Oxygen. The page builder can be accessed in the front-end via /about-us/?ct_builder=true. While you use the visual […]
Unloading plugins within the Dashboard /wp-admin/
This feature is available in the Pro version starting from v1.1.8.6. For better performance and a higher PageSpeed Insights score, unloading plugins (not just the CSS/JS files that are loading from those plugins) in the frontend view is one of the features that can be used in Asset CleanUp Pro. This post is about the […]
How to unload Swiper from Elementor
One of the largest assets loaded from the Elementor plugin is Swiper located in /wp-content/plugins/elementor/assets/lib/swiper/swiper.min.js (this is the minified version that should load in a live environment) which uncompressed (if the server where the website is located doesn’t serve files GZIP compressed) has a size of ~135 KB which is quite a lot for just […]
How to check if Gutenberg Blocks CSS file is needed or not
One of the most common files that are loaded by default in WordPress (at least at the time of writing this, June 2, 2020) is /wp-includes/css/dist/block-library/style.min.css which has a size of ~54 KB (if it’s not GZIP compressed). In many cases, it is not needed site-wide or on certain pages depending on the situation, if […]
What are plugins unload rules?
This is a feature available in the Pro version of Asset CleanUp. Remember: When you unload a plugin, you would not only unload all the CSS/JS that is loading from that plugin but everything else: its backend PHP code, HTML output printed via wp_head() or wp_footer() action hooks, cookies that are set), etc. It would […]
What are CSS/JS unload rules?
An unload rule is the action that prevents a specific asset (CSS/JavaScript file) from loading on a certain page, a group of pages or site-wide (everywhere, on all pages of the website). These include: Unload on this page (applies only on the post/page that you’re editing) Unload everywhere (site-wide unload of an asset) Unload on […]