• Hi there,

    I’m not sure when the issues first appeared, but running the latest 3.7.0 version I decided to remove the plugin.

    During a monthly website audit, I found the plugin causes significant pagespeed impact on the entire website (even pages not using the plugin) & loads files where it shouldn’t.

    Let me explain:

    • It should only load the plugin files on a page that actively uses the plugin. Or at least the option to do so (without needing an asset cleanup tool)
    • It should not load back-end block editor JS files on the front end. Examples: block-editor.min.js, editor.min.js, etc. loaded on all pages. While they should generally not be loaded at all on the front-end.

    If these issues are not addressed I can no longer recommend this plugin. Which is a shame, because otherwise, I like what it does.

    Thanks

    • This topic was modified 11 months, 3 weeks ago by krikke.
    • This topic was modified 11 months, 3 weeks ago by krikke. Reason: clarifications
Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author Mahesh Waghmare

    (@mahesh901122)

    Hello @krikke

    Currently the script loaded on all the page’s because the user may select the selector to add it on any page.

    We will add a option in the plugin to load the script on those page’s where user selected the script to load.

    Thread Starter krikke

    (@krikke)

    Thank you for the swift response @mahesh901122

    I understand that’s the design decision you took. I would challenge that decision as it would be better from a user POV to keep the options open when/where to use the plugin & not impact page speed unneeded. There are ways to change when scripts should be loaded based on certain use criteria. In most use cases, the plugin is only used on very select pages (like a contact page).

    Furthermore, your reply does not answer my second point.

    • It should not load back-end block editor JS files on the front end. Examples: block-editor.min.js, editor.min.js, etc. loaded on all pages. While they should generally not be loaded at all on the front-end.

    Those files should not be loaded on the front-end even with the stated design decisions. Furthermore, disabling all your js/css files sitewide does not unload these files. Disabling the plugin immediately unloads all of these files. So it is not based on plugin usage, but rather the plugin being activated.

    Anyhow, I hope this feedback is useful to you to improve the plugin. I will no longer be able to use it on mine or my client sites

    Kristof

    • This reply was modified 11 months, 3 weeks ago by krikke.
    Plugin Author Mahesh Waghmare

    (@mahesh901122)

    #1 Right
    #2 Yes. The backend script not required to load on front-end.

    Is it possible to share the page URL where you have used it for reference?

    Meanwhile, Will check it and provide solution for both asap.

    Thread Starter krikke

    (@krikke)

    Unfortunately, I can not share a link. It was on various client websites & I had to remove the plugin.

    I can tell you I use a Gutenberg stack (kadence theme, kadence blocks, …)

    Plugin Author Mahesh Waghmare

    (@mahesh901122)

    No issues.

    We will take care of it and let you know soon.

    Plugin Author Mahesh Waghmare

    (@mahesh901122)

    Hello @krikke

    The issue is now fixed.

    Please update to the latest plugin and check it once.

    Thread Starter krikke

    (@krikke)

    Thank you for the quick response @mahesh901122

    I can now see you implemented an initial conditional logic. could not verify the fixes due to a couple of issues:

    • Cannot select individual pages/posts in conditional logic
    • It appears the gutenberg block has dissapeared, I cannot find a way to add it to a page
    Plugin Author Mahesh Waghmare

    (@mahesh901122)

    Hello @krikke

    In the upcoming version v3.8.3 we are going to fix:

    • It appears the gutenberg block has dissapeared, I cannot find a way to add it to a page

    But, For the suggession:

    • Cannot select individual pages/posts in conditional logic

    We may consider another update.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Website slowdown & loading unneeded files’ is closed to new replies.