Caching age on local asset too small

Rule from network under performance category

What is a trooper!

we have submitted your edit to the community for review! We'll review and make it live on the site in the next few hours, the internet thanks you :).

Browse another section of the knowledge base



Suggest an edit

Cancel

This rule has no content... yet.

Add content to this rule

Or just browse to view rules that have content



 

Having an extremely short caching age on local resources (in production) is generally a bad idea, as this nullifies the point of allowing the browser to cache resources.

How do I fix this ?

Consider setting the Expires header at least two days in the future. If this is unacceptable, alternatives include filename based cache busting.

Resources

Browse another section of the knowledge base



Signup icon
Ready to see how well your site scores?

Passmarked works best when you have an account. It allows you to keep a dashboard with saved data of the sites you have run through the system, we’ll alert you about important updates and you get access to the Passmarked Slack forum.

Sign up to get started