Far Futures Expiry & speed

WordPress Mobile Speed

Updated


There are no affiliate links on PagePipe.

Far Futures Expiry plugin should be added.

REFERENCE: https://pagepipe.com/fixing-pingdom-leverage-browser-caching-errors/

Recommended add Far Futures Expiry

Expiry header specifies a time far enough in the future so that browsers won’t try to re-fetch images, CSS, javascript etc files that haven’t changed (this reduces the number of HTTP requests) and hence the performance improvement on subsequent page views. We recommend an expiry of one year.

REFERENCE: https://wordpress.org/plugins/far-future-expiry-header/

Expiry header specifies a time far enough in the future so that browsers won’t try to re-fetch images, CSS, javascript etc files that haven’t changed (this reduces the number of HTTP requests) and hence the performance improvement on subsequent page views. We recommend an expiry of one year.

There is no far-futures expiry date being set for cached assets. With no “max age” set in the .htaccess file, assets are stored for too short of a time. We recommend a 1-year expiration. Presently, there is no benefit from browser caching for return visitors. We recommend installing the PagePipe plugin LongCache. It writes the settings to the server .htaccess file. This is something we do as part of our service when you approve it.

Godspeed-

Steve Teare
performance engineer
May 2021

 

PagePipe Site Tuning Services for Speed

Instead of band-aid approaches, we drill down to the root cause of your slow site. This is origin optimization. Also known as site tuning. To do this, we analyze site components:

  • Hosting
  • Theme
  • Plugins
  • Scripts and third-party services.
  • Images and media library.
  • We minimize globally loading plugin effects.

Find out more details about Site TuningGet Speed!


 

Other Related Resources

Build with Empathy
GIVE SPEED