WP Super Cache Plugin
Installing a WP-Super-Cache, which can be accomplished under plugins, is one way to optimize WordPress.
To use the recommended settings, please finish all four (4) steps.
Step 1 : Set General Settings
On the “Advanced” tab:
- Check box next to “Cache hits to this website…”
- The select button next to “Use mod_rewrite to serve cache files”
- “Cache rebuild” & “Extra homepage checks” should already be checked, leave them that way.
- Select the “Update Status” button.
Step 2: Set Mod_Rewrite Rules
Then, scroll down and select “Update Mod_Rewrite Rules” in the yellow box.
Step 3: Set Garbage Collection
Scroll down to “Expiry Time & Garbage Collection” and enter “3600” in the box, then select “Change Expiration”
Step 4: Set Rejected User Agents
It is suggested that you do not remove default user agents from the list to avoid bots from caching contents and websites usually not seen by your tourists.
Explanation of the Options Selected Cache hits to this website…
Use mod_rewrite to serve cache files
The fastest caching method uses mod_rewrite rules in the client’s .htaccess file
Documents of the WP Super Cache Plugin are compressed and stored so that heavy compression is obtained only once. These files are generally smaller and much more quickly sent to a visitor’s browser than uncompressed html. This means that the server spends less time discussing the network, saving CPU time and bandwidth, and also providing much quicker service on the next request.
304 Not Modified browser caching
Indicates to the client’s browser whether a requested file has been modified or not.
Don’t cache pages for known users
This prevents logged-in users from being served cached pages and is the default for almost every caching plugin out there.
Expiry Time & Garbage Collection
By default, cache documents can be cached at age 1 hour (3600 seconds) before ideally deleted. In the case of sites with not many posts (1,000 or less), if you do not frequently update your content, this setting can be increased. If you have a very big number of messages, it can be more feasible to make a reduced environment around 1800 to avoid stat / CPU problems owing to the number of documents generated.
Rejected User Agents
It is recommended not to delete the default user agents from the list so that bots cannot cache contents and pages not normally viewed by your visitors. (For instance, if you’ve got a calendar, an actual visitor may only browse months in the vicinity of it, but a bot will index it for every month as if it was a distinct website.