Title: Plugin Load Order
Last modified: June 8, 2020

---

# Plugin Load Order

 *  Resolved [Katherine](https://wordpress.org/support/users/kittcatalina/)
 * (@kittcatalina)
 * [6 years ago](https://wordpress.org/support/topic/plugin-load-order-2/)
 * I know Asset Cleanup does not include this feature. It is available in the Plugin
   Organizer plugin.
 * Do you think a plugin load order option (on a per page basis) would improve speed
   considerably?
 * I read that WordPress loads MU plugins first, then alphebetically, and then plugin’s
   use Hooks and Filters to call to and load their assets after that.
 * I am more interested in what you think of this feature, if it would be a considerable
   speed difference? (Taking into account you’re not ordering things in a way that
   could break the page)
 * I thought this could improve critical rendering path?
 * I already plan to test with Plugin Organizer and read a little more about it.
 * But I was just wondering if this is something Asset Cleanup ever plans to add
   or you have thought about?
 * Thanks for your time!

Viewing 1 replies (of 1 total)

 *  Plugin Author [Gabe Livan](https://wordpress.org/support/users/gabelivan/)
 * (@gabelivan)
 * [5 years, 11 months ago](https://wordpress.org/support/topic/plugin-load-order-2/#post-13025198)
 * [@kittcatalina](https://wordpress.org/support/users/kittcatalina/) fist, my apologies
   for this late reply! Loading plugins in a custom order than they currently are
   is something that was barely requested for Asset CleanUp, thus other features
   had more priority when it comes to development. In an ideal scenario, if developers
   would follow WordPress standards, it shouldn’t matter in which order those plugins
   are triggered.
 * For instance, WooCommerce has lots of extensions and those extensions (especially
   the professional ones) are written in such a way that it shouldn’t even matter
   if the extension is loaded before the actual WooCommerce main plugin or if there
   are other 10 extensions installed there (no matter in which order they are triggering).
   For a newbie developer that is not yet fully familiar with the way WordPress 
   works, he might be tempted to write a base plugin and an extension that should
   be loaded in a certain order. For instance, if the extension happens to be loaded
   before the main plugin, a PHP error would be triggered and the website won’t 
   load anymore. The code has to be written in such a way that if an extension is
   triggered before the base plugin, no errors will be shown and the website will
   load as normal. Moreover, if the base plugin has been deactivated, then even 
   if the extension plugin is active, it will be like it’s inactive since it has
   no usage without the base plugin extension.
 * Anyway, back to performance. Since the plugins are loaded in the backend and 
   the HTML code resulting from those plugins is generated, what sometimes happens
   is that certain hardcoded STYLE/SCRIPT tags or enqueued CSS/JS that have the 
   same priority when add_action() is used, are shown before/after another, but 
   in terms of performance, this is actually not making any difference or at least
   it shouldn’t if the plugin is a professional one. There are rare cases (I don’t
   even recall when I had to change the order if the loaded assets, that’s how long
   it was) when you might need to alter the order of the plugins. Asset CleanUp 
   doesn’t deal with that at least at this time, due to the very low demand.
 * If you check out the description of this plugin: [https://wordpress.org/plugins/plugins-load-order/](https://wordpress.org/plugins/plugins-load-order/)–
   you will notice the same thing I just explained above is also mentioned by the
   plugin’s developer:
 * > If you are plugin developer, I encourage you to use actions and hooks so that
   > you will not need this plugin at all, but if you are managing your own blog
   > and you face to the problem a plugin depends on other one, then this is the
   > plugin you need.
 * So, I strongly recommend the usage of actions & filters (the right way) whenever
   a plugin is developed and it depends on a base plugin.

Viewing 1 replies (of 1 total)

The topic ‘Plugin Load Order’ is closed to new replies.

 * ![](https://ps.w.org/wp-asset-clean-up/assets/icon-256x256.png?rev=1981952)
 * [Asset CleanUp: Page Speed Booster](https://wordpress.org/plugins/wp-asset-clean-up/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wp-asset-clean-up/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wp-asset-clean-up/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-asset-clean-up/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-asset-clean-up/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-asset-clean-up/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [Gabe Livan](https://wordpress.org/support/users/gabelivan/)
 * Last activity: [5 years, 11 months ago](https://wordpress.org/support/topic/plugin-load-order-2/#post-13025198)
 * Status: resolved