How to serve static assets cache policy efficiently on Static Site App Platform Deploy

After uploading a static website in App Platform using GitHub source I deploy the website and ran a Lighthouse diagnostic on it.

The diagnostic result report is tagging my static site with a note saying “Serve static assets with an efficient cache policy”


I’ve run into the same issue. When generating static sites all the images have unique names, allowing you to take advantage of both cdn and browser caching.

In my opinion, being able to control browser caching is essential. Without it, the load speed of our static sites will be negatively impacted.

Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Accepted Answer


Serve static assets with an efficient cache policy 33 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

This is from the lighthouse report. It’s basically that it’s seeing that 33 image/js/css resources that I have in my static site source code have no efficient caching policy.

👋🏼 @angelicas

Can you share more details about the Lighthouse report or your app URL if that’s ok? I just ran a Lighthouse test on a Static Site of my own ( and it didn’t complain about this, so we’ll have to look more into your app specifically.