js being delayed despite settings

  • Resolved mikebuckley42

    (@mikebuckley42)


    2 years ago

    Quick background, inherited this site and performance is shocking so I’m looking at litespeed plugin to help matters. I’ve set UCSS to on and I can see the individual combined css pages being created for each page – though, the optimised css still displays circa 95% unused in the inspector but that’s a different battle.

    I’ve set the javascript to both ‘off’ and ‘deferred’ and never ‘delayed’, but nothing changes, the javascript files don’t load until I interact with the page in mobile view but they do in desktop view. The console also logs ‘[LiteSpeed] Start Load JS Delayed’ when I interact, then everything loads up. BTW the page will look a bit wonky as I’ve tried to remove unused css manually.

    Thanks in advance

    The page I need help with: [log in to see the link]

Viewing 8 replies - 1 through 8 (of 8 total)
  • serpentdriver

    (@serpentdriver)

    You are using a 3rd party cache layer which inevitably does not support all features of the LiteSpeed LScache plugin. This also includes the UCSS function and much more. It is therefore only logical that there are malfunctions and misrepresentations. In order to be able to use all functions of the LiteSpeed Cache plugin and all functions of this plugin, you need either the LiteSpeed web server or quic.cloud. In any case, the use of a 3rd party cache layer is excluded.

    Thread Starter mikebuckley42

    (@mikebuckley42)

    Thanks for your quick response CacheCrawler, I’ve just gone out and got a sandwich, come back and the delay issue has disappeared, everything is working fine (apart from it’s appearance) – I did nothing. I have got a quic.cloud account and I’m going to approach our hosting company about installing a litespeed server.

    Just a confirmation if you don’t mind, the 3rd layer cache you’re referring to is securi? As I said, I’ve inherited this so I’ll need to check with a higher authority if it’s ok to switch it off.

    Thanks again

    serpentdriver

    (@serpentdriver)

    Just a confirmation if you don’t mind, the 3rd layer cache you’re referring to is securi?

    I don’t know the name of the cache provider, but you have another HTTP cache layer in use, which, due to its very dubious methodology, causes many problems and is independent of the LScache plugin. Don’t use it any longer!

    Thread Starter mikebuckley42

    (@mikebuckley42)

    Appreciate your answers – as you can tell I’m probably out of my depth but guess that’s how we learn… where are you identifying the cache layer? the best I can see is to inspect a loaded asset and look at the headers? the application inspectors shows no caching at all.

    Any steer would be grateful!

    serpentdriver

    (@serpentdriver)

    the best I can see is to inspect a loaded asset and look at the headers?

    Yes, you can tell by the response headers.

    Plugin Support qtwrk

    (@qtwrk)

    a quick guide for check http response header

    Thread Starter mikebuckley42

    (@mikebuckley42)

    Thank you for your message qtwrk – sorry for tardy response, been away for a few days.. to be honest, I think I might abandon this – our hosting company don’t install or have anything to do with litespeed, I’ve gone a bit further with the quic.cloud integration and it’s now asking me to change the named servers with our registrar – given this staging site is in a subfolder for the main site I’m getting a bit twitchy, I’m normally quite cavalier about these things but on this occasion I’m chickening out…

    Thanks again!

    Plugin Support qtwrk

    (@qtwrk)

    yeah , in order to use CDN, you have to update the DNS like you did with sucuri , the issue you stated is more like mis-configuration somewhere, if you wish to continue , I would suggest to reset to default setting first , see if it works or not on default , then narrowing down which option that caused trouble and see what to do next.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘js being delayed despite settings’ is closed to new replies.