Add Expires headers

Hello Steve,

Are you interested in being able to define custom expires headers for your content? Or would you want us to somehow honour what your server may be setting (i.e. 90day) ?

Thanks

Ok I’ll look into either option. The honouring of expires headers may be easier because we wouldnt have to build in the extra custom option into our configuration management system but this is definitely a good idea and would give people more options. I’m sure there are other options to provide as well once we go down this route.

Apologies for the delay. I have increased the default expires setting from 1 day to 7 days for static assets and 5 days to 30 days for anything in the wp-content/uploads folder, pending the implementation of this as a setting that people can control.

Hopefully this alleviates the issue a bit while we transition to a more settings-based system

Steve,

I’d be curious what they recommend. If google recommends a year for expires then I would be inclined to put that in across the board.

Is there any way you can dig deeper to that recommendation to see what the best practice is?

Thanks

Steve,

Would you mind providing your site URL, or send it in an email to [email protected] ?

I wouldnt mind running that test to see those messages.

Thanks!

Steve,

I replied to you directly. We have changed the browser caching from 30 days to 1 year as a result of best practice recommendations by google.

No idea why 1 year is the magic number but at the very least this will help you score a higher score with the pagespeed type scanning services.

Thanks!