This feature is available in the Pro version starting from v1.2.3.4.

This option is useful if you want to unload or load as an exception (from any unload rule already set) whole plugins on taxonomy pages. These include the built-in categories (“category”), tags (“post_tag”) and custom taxonomies which includes the popular WooCommerce product categories & tags (“product_cat”, “product_tag”).

These pages are showing the list of the posts that are associated to the taxonomy. For instance, if you to your WordPress Dashboard and then visit “Posts” — “Categories” and then click on “View” for one of the categories that has at least one post/article, you will view the taxonomy page with the list of all the posts/articles belonging to that category. The same with the list of categories (taxonomies) from WooCommerce (or a similar plugin). If you are using WooCommerce, you can go to “Products” — “Categories” and then click on “View” from any of the product categories that has at least one product associated with it. You will view the taxonomy page with the list of all products belonging to that category.

Often, in these type of pages, you will likely not need specific plugins to load.

Case Scenario #1

You have a plugin installed called Product Gallery Slider and Additional Variation Images Gallery for WooCommerce (check the live demo for this particular plugin) that works together with WooCommerce plugin. This plugin is ONLY needed to trigger on a single product page (e.g. a modal box that triggers when you click on an image which will show the gallery of images for that product). But you know for sure that the plugin which is meant to be used just for that gallery is never used in the product category (taxonomy) pages.

In the print below, there’s the product category (taxonomy) page (list of WooCommerce products). You will notice that, there’s no gallery there, nor any option to magnify the image to view the gallery.

When the visitor would click on a specific product, the gallery will be visible along with the magnifying icon to view the product images that would load in a Lightbox.

Here are two print screens that show both the single product page with the gallery and the Lightbox after it was clicked on the magnifying icon.

Case Scenario #2

Another example is the well known “Contact Form 7” plugin. If you do not have any contact form loaded on the page when someone visits the list of products from a specific category, then you will likely not need the plugin to load there and you could unload it (e.g. this was just an example as “Contact Form 7” sometimes loads in all pages in the footer of websites or loaded inside a modal box when you click on the “Contact” link, as some website owners prefer it to have it this way, so you to double-check that before unloading it).

Based on my experience, I usually unload lots of plugins on such taxonomy pages and save resources. You should always unload a plugin one by one on a taxonomy page and then test the page. If everything looks good as it used to, then you can continue with the unloading and so on. Note that some plugins are meant to load site-wide (unless you have specific reasons not to) such as “Analytify – Google Analytics Dashboard For WordPress” which is meant to provide you analytics for the category pages as well so you know which pages were visited by your potential clients.

How to reach the area where you could apply the rule to unload the desired plugin on a taxonomy page?

  1. Within the “Asset CleanUp Pro” menu go to: “Plugins Manager” — “IN FRONTEND VIEW (your visitors)” (default tab)
  2. Scroll until you locate the plugin that you want to unload on the taxonomy page
  3. Within the “Unload this plugin in the front-end:” area, click on “On these taxonomy pages:” and it will show you the list of all the taxonomies that are loaded on your website. Choose the one(s) that you want.

Here’s a print screen below (based on the example I mentioned above) so you can understand better:

In general, plugins that aren’t meant to load site-wide on a page and do not have to be loaded on the taxonomy pages, could be unloaded in order to save resources (fewer PHP code to trigger) and also prevent their CSS/JS assets to uselessly load on the taxonomy pages.

Was this post helpful?