Cached css and js files without a far-future expiration date

  • Resolved harman79

    (@harman79)


    4 years, 4 months ago

    Hi,

    I am using the pro version of asset cleanup together with WP Fastest cache. The results in both gtmetrix and webpagetest are showing that the cached js files do not have a far future expire date, giving me a low score in caching. What also buffles me a bit is that the main .htaccess file is indeed empty (i.e. no caching rules there). Is there a way to fix this?

    Thanks for the great plugin btw…

    • This topic was modified 4 years, 4 months ago by harman79.

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

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Gabe Livan

    (@gabelivan)

    @harman79 the combination of plugins is a good one: a page caching plugin + a cleaning one that takes away the useless assets.

    As for gzipping, browser caching, and other things, they should be enabled in WP Fastest Cache like in the following print screen: https://ibb.co/CJY82G7 – if after enabling them and updating the page, it will still not work, then you should contact WP Fastest Cache support as Asset CleanUp never writes anything in .htaccess and WP Fastest Cache should do this for the features you need.

    If the .htaccess rules are correct, any file from your WordPress installation should have a far-future expiration date, no matter if they are loading from /wp-content/cache/, /wp-content/themees/ or any other location ??

    Thread Starter harman79

    (@harman79)

    OK, thanks for the fast reply!

    I have all settings in WP fastest cache as you suggested, so I will try their support or I will try another plugin.

    Plugin Author Gabe Livan

    (@gabelivan)

    @harman79 sure, make sure .htaccess is writable, perhaps something is funny there and it has some buggy code that prevents it from working fine (e.g. from a different optimization plugin, you never know).

    Also, in the GTmetrix report, core files such as /wp-includes/js/jquery/jquery.js?ver=1.12.4-wp are reported without a far-future expiration date suggesting, there’s nothing special about Asset CleanUp caching files. All the files should be treated the same way by WP Fastest Cache. The plugin is great and many people using it in combination with Asset CleanUp so it might be an isolated case here. For some reason, it doesn’t work well on your end, perhaps the .htaccess file is having issues.

    Thread Starter harman79

    (@harman79)

    I was totally reckless and did not do my homework properly… First off, my htaccess file was not empty. It was actually bloated with nonsense and duplicate rules from other caching plugins which I had installed in my quest to find the most suitable match for my needs… I deleted all duplicate rules and now it all works as it should!

    Apologies for messing around in the support section of your plugin and thanks a lot for the time you took to even run gtmetrix for my site…

    Appreciated, keep up the great work!

    Plugin Author Gabe Livan

    (@gabelivan)

    @harman79 as I suspected, it’s been bloated with rules from other plugins. It happens often! Anyway, I’m glad it’s been sorted now ??

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Cached css and js files without a far-future expiration date’ is closed to new replies.

Tags