Far Future Expiry Header

Beschreibung

This plugin offers a few lightweight features to speed up your WordPress site without much hassle.

Far Future Expiry

When the feature is enabled, this plugin will modify your .htaccess file by inserting code which will add expires headers for common static file types.

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.

Gzip Compression

You can also enable Gzip compression on your site using this plugin. Gzip compression will speed up your WordPress site by compressing the page output and sending it to your visitors browser.

When enabled, the plugin will do gzip compression if the visitor’s browser can handle it.

This feature may conflict with a few other plugins. So disable this feature if you need to use a plugin which doesn’t work with gzip compression.

Verwendung

To use this plugin do the following:

1) Ensure that the „mod_expires“ module is enabled from your host’s main configuration file

2) Check with your hosting provider or if you have access to the httpd.conf file the following line should be uncommented:
LoadModule expires_module modules/mod_expires.so

3) Enable the „Far Future Expiration“ checkbox

4) Set the number of days till expiry

5) Select the file types you wish to enable the „far future expiration“ feature for by using the checkboxes in the „File Types“ section

NOTE: When you use this plugin, the file selected file types are cached in the browser until they expire. Therefore you should not use this on files that change frequently.

More details can be found on the plugin’s documentation page

Installation

  1. Upload the far-future-expiration.zip file from the Plugins -> Add New page in the WordPress administration panel.
  2. Activate the plugin through the „Plugins“ menu in the WordPress administration panel.

FAQ

Can I set a far future expiry header with this plugin?

Ja

Can I eanble gzip compression on my site using this plugin?

ja

Rezensionen

1. Juni 2021 1 Antwort
I combined speed of light, far future, ssl insecure content fixer, strano ajax login, gtranslate, sonaar mp3 music player pro, telemetry disable, easy digital downloads, Disable XML-RPC-API, kama click counter, url shortener by mythemeshop, and even though I put My products on the front page - I lost about 1.5 seconds off My score by using this in tandem with speed of light.
11. Juli 2019 1 Antwort
after installed Internal Server Error. Breaking my WP dont install
9. Mai 2019 1 Antwort
I was really looking forward to installing it. I have two other sites and the plugin works great. Then today I tried to install it and the moment I click to activate it, the main page goes blank (white page). I deactivate and everything comes back. Then I activate again and I get the blank page. Really weird. The only difference with this site is that I am using Slider Revolution, but not sure that has anything to do. Got a ton of other plugins installed but on the other servers also. Scratching my head a little. If anyone has an idea I am all ears :-).....
5. Mai 2019 1 Antwort
Many thanks to the developer for the work!
Alle 29 Rezensionen lesen

Mitwirkende & Entwickler

„Far Future Expiry Header“ ist Open-Source-Software. Folgende Menschen haben an diesem Plugin mitgewirkt:

Mitwirkende

„Far Future Expiry Header“ wurde in 1 Sprache übersetzt. Danke an die Übersetzerinnen und Übersetzer für ihre Mitwirkung.

Übersetze „Far Future Expiry Header“ in deine Sprache.

Interessiert an der Entwicklung?

Durchstöbere den Code, sieh dir das SVN Repository an oder abonniere das Entwicklungsprotokoll per RSS.

Änderungsprotokoll

1.6

  • PHP 8.2 compatibility related update.

1.5

  • Added nonce to the settings menu.

1.4

  • The far future expiry is written using days instead of hours so GT metrix can read it better.

1.3

  • Added a new feature to enable gzip compression on the site

1.2

  • Fixed a minor bug with the htacess rules.

1.1

  • First commit to wp repo