Streaming live at 10am (PST)

Serve static assets with an efficient cache policy

Hi there,

I am currently trying to improve my website performance and after doing some audits with GTmetrix, I have found that I would need to implement an efficient cache policy. Have you already work on something similar? How to do it?

You will find here the link for GTmetrix:

  1. https://gtmetrix.com/reports/www.droverclub.com/uOmJaVtC/
  2. https://gtmetrix.com/reports/www.droverclub.com/Br0XC85H/
  3. https://gtmetrix.com/reports/www.droverclub.com/aVKshiTt/

Here is my site preview link: Webflow - Drover Club

Many thanks for your time given,
Aurélien

Since you have no control over the CDN or site hosting you can’t address these issues. Only Webflow can unless you export your site and handle it on your own.

Hi Webdev,

Thank you for your reply. Does it mean I have to deal with this request directly with Webflow support?

The choices made by Webflow in regards to hosting are settings affecting all sites, not just yours. Webflow can’t and won’t make changes just for you. They roll them out for everyone. It is safe to say that they are aware of hosting limitations. If this is a requirement for you then you would need to host the site yourself to have complete control.

Important - On tests like Google pagespeed Insights -or- GTmetrix - The cache policy warnings not related to webflow resources (Jquery, webflow [1] one JS file & [1] one CSS file and fonts).

If you find issues - most of the times, it will be related to tools like hubspot, hotjar, paypal, google analytics, or in short "3rd party resources". First, not all of this 3rd resources scripts will work properly with long cache. Second, anyway it isn’t hosted on webslow server, so you can’t optimize it (Beside lazy loading, defer, async, and ideas like this).

Avoid 3rd party resources ATTACK => Load 3rd resources responsibly

The best approach is to load 3rd resources “Responsibly” (Although the shortest/laziest way is just to load all the 3rd scripts under global site setting).

For example no need to load Paypal API for the entire site - if you need Paypal only on X pages). And of course “clean up” unused 3rd resources .
**Google tag manager tags and triggers - are very very useful tool for this idea.