• Hi, congrats again to your idea – happy to be your first reviewer today!
    Really love your plugin.

    But, please, do not split your JS into a file and some inline part. Since there’s no settings page anyway, I see no reason to put an inline part with variables (there are none) into HTML, do you?

    Problem was, that I wanted to have your script running after first interaction (no need to load it on init) by means of the Flying Scripts plugin – which raised an error, since the inline part was faster loaded than the file.

    So appending the inline part to your JS file solved the issue for me.

    May be that I don’t see why you’re splitting the JS at all?

    Thanks again for your plugin, intend to use it on all my projects!

    The best, Frank

    • This topic was modified 2 years, 4 months ago by Frank.
Viewing 2 replies - 1 through 2 (of 2 total)
  • drazon

    (@drazon)

    By appending the inline script to the external js file does it work with flying scripts and a caching plugin like super cache or just with flying scripts?

    Thread Starter Frank

    (@t-mug)

    Caching would work anyway – it’s more about delaying the loading of JavaScript files. I don’t understand why developers are not aware of this. Some are, like the people behind the Kadence suite, but speed awareness is really rare among net programmers.

    The lack of awareness in this particular case (this plugin is about speed optimisation, of all things!) is really remarkable.

    Appending the inline part to the file works fine with all JS-delaying solutions like WP Rocket and the like.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Let the thing play together with Flying Scripts’ is closed to new replies.