• Resolved chromasia

    (@chromasia)


    Congratulations on the new minification options – they work really well.

    That said, since implementing this feature GTMetrix is telling me that the combined CSS and JS files don’t have a far-future expiration date. I’m sure this is irrelevant, as the files are being served from the Litespeed cache, so I guess the expiration dates aren’t needed, but it’s having a negative impact on the reported page speed. I did try looking for the ‘min’ folder on my server but guess this is generated on the fly rather than as an actual folder that contains the css and js files. As such there’s no way I can change the expiration dates. Is this an issue that can be addressed, or should I just ignore it?

    Best wishes,

    Dave

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

Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Support Hai Zheng?

    (@hailite)

    Hi @chromasia,

    We are glad you like it.

    That file is cached on server side, so those css/js file can be faster served than file-based files. Currently you don’t have to add any expiration date. In later release we will add browser cache, which will add it automatically for all static files and these cached css/js files.

    Thread Starter chromasia

    (@chromasia)

    Thanks. And yes, I appreciate that the expiration dates don’t make any significant difference, it’s just the issue with page speed metrics. Adding a expiration date to the browser cache will fix that so I’ll look forward to the update.

    Thread Starter chromasia

    (@chromasia)

    Does that also mean that the generated/minified files will also be able to be cached by a CDN? The reason I ask is that it seems as though the generated css and js files, at the moment at least, can only be served from the origin server – they’re not able to be cached by a CDN. I appreciate that this works well if you’re geographically near to the server, but if you’re further away it means that the more you minify and combine the original js and css files the less you can cache elsewhere. It would be great if the generated files could also be cached elsewhere.

    Plugin Support Hai Zheng?

    (@hailite)

    Yes you are right. When we add CDN feature which should prolly be the release after next release, css/js will be there too as you mentioned.

    Thread Starter chromasia

    (@chromasia)

    That’s great news! ??

    Plugin Support Hai Zheng?

    (@hailite)

    Also @chromasia, can you give any advanced suggestion about CDN feature? Do you need we push attachments to remote server related to CDN? e.g. for Cloudfront, you may want S3 to host your files. Who is the best one to push those files to S3 you think? Should it be done by us?

    Thread Starter chromasia

    (@chromasia)

    To be honest, I’m not sure I’m the best person to ask as my knowledge is limited. My own server is based in London, and currently I use a free Cloudflare account as a lot of my clients are based in the US. Having Cloudflare running reduces the load time for most of my pages to around 50% when aspects of the page are served via their cache. If all my clients were in the UK, I wouldn’t use them, and would be happy with the speed of the Litespeed cache, but I need the CDN as the roundtrip times are just too high to anywhere other than Europe.

    That said, if the compressed/minified files could be pushed to a CDN that would be great, but I don’t know if that’s possible with Cloudflare, and I don’t know if it’s strictly necessary – it only needs one person to view a page and then the files are cached, so I’m not sure there would be much of a performance gain.

    Plugin Support Hai Zheng?

    (@hailite)

    Understand. We will support Cloudflare and AWS in CDN version.

    Thread Starter chromasia

    (@chromasia)

    Thanks.

    It should be CDN provider independent in my opinion.
    There are lots of CDN providers around the world and giving path option is the best way.

    Plugin Support Hai Zheng?

    (@hailite)

    OK we will consider of it. Thanks.

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘CSS/JS Minification Expires Headers’ is closed to new replies.