@kcaluwae can you share with us the URL to the CSS/JS file (not just the page where you prevented it from loading). The code within it could “tell” what’s needed for.
If it’s for the WP top black admin bar and you don’t need the functionality related to it (suggests from its name that it’s for some notes), nor your visitors (which by default are not viewing the admin bar, unless they’re logged in, then it should be safe to unload it. Consider checking the browser’s console too (right-click, “Inspect”, “Console”) to make sure no JS errors have been generated from unloading it.
-
This reply was modified 7 years ago by
Gabe Livan.
Hi @gabelivan ,
Thanks for your answer.
The browser’s console is showing no errors.
This is the link to the files:
https://s0.wp.com/wp-content/mu-plugins/notes/admin-bar-v2.js?ver=7.3.1-201921
https://s0.wp.com/wp-content/mu-plugins/notes/admin-bar-v2.css?ver=7.3.1-201921
According to what I found Mu-plugins refers to must-use plugins. I had a look in my WP dashboard and I have one such pluging ‘ManageWP Worker’ but I don’t see how these files would have anything to do with Manage WP worker’?
You could have several plugins in “mu-plugins” and it looks like “ManageWP Worker” plugin is not related to the CSS/JS you mentioned.
I wouldn’t recommend dequeuing files that are loading only for logged-in users (unless you have many that you’re sure you don’t need) as it won’t usually make much difference in page speed load and you will avoid breaking pages (e.g. if you unload CSS that is linked to an admin bar, then you could break the layout of that bar).
-
This reply was modified 7 years ago by
Gabe Livan.