The Axis development team reported the following:
****************************
The plugin is loading its javascript on all pages, which is leading to the conflicts with Bootstrap library.
Can you notify to the plugin’s developer and see if they can load their javascripts only on the pages required and not on all pages ?
*****************************
I concur.
While loading code on every page may be necessary when a plugin is first activated and before it is known what pages the user will need its features on, AFTER the user has defined the pages where its features are needed, the plugin could provide the user with a means to restrict the plugin’s code loading to only those pages where it is needed.
Several plugins we use employ this approach and in some scenarios it can also speed up page loading on pages where the code is not needed and can result in higher scores on PageSpeed, Yslow, etc.
Since Google is now considering page load speed in rankings, adding the suggested feature to your plugin would also help assure that it was not inadvertently causing sites that use it to suffer lower rankings due to unneeded code loading on many pages.
Please consider such an improvement in your development pipeline.
Thanks
-
This reply was modified 7 years, 9 months ago by SooBahkDo.