Caching WordPress Blog Using Hyper Cache Plugin - Installation and Configuration. Caching in wordpress - choosing the best caching plugin WordPress cache

Hopefully, no one needs to explain why a caching plugin is needed and how important it is to choose the one that will really help, and not just create an extra load on the database with its presence. When analyzing, we will take into account all indicators, not just load time.

The benefits of caching

A small digression. If, nevertheless, someone still doubts the need for caching, then you should know that since April 21, Google announced that all mobile-friendly sites (and speed is one of the components "friendly") receive a significant advantage in search results. Google's intentions are very clear - SEO specialists and webmasters need to work on performance, both desktop and mobile version site.

There are several ways to improve the performance of your site and reduce its load time, but for most novice (and not only) SEOs, caching plugins are not one, but the only tool used to achieve this goal.

WordPress renders pages dynamically, which leads to a large number of database queries. Caching is dynamic created pages allows users to see regular HTML pages, which significantly reduces page load times and reduces server load.

Caching test details

At the very beginning, it was planned to use 2 themes in the tests - the simplest "twenty-fourteen" and the more complex one (which will simulate a "real" site). But during the tests, it turned out that the impact of caching on the loading speed of the "twenty-fourteen" theme is so minimal that it can be neglected. It turned out to be more important fine tuning server, but today the article is not about that.

As a result, we will only use 1 theme (Novelty theme by Tesla Themes). The test page was designed with graphics and text. There is also a sidebar and several plugins (news, Twitter / Instagram feed). Hosted by WP Dev Shed. As a result, we got a page with a relatively long load time.

Because the site is new, then it did not have traffic (including, during testing, there were not even PS bots). The server worked in the Apache + Ngnix bundle.

The following plugins participated in the test:

AIO Cache
WP Fast Cache
WP-Cache.Com
Alpha cache
Flexicache
Bodi0's Easy Cache
Hyper Cache
Hyper Cache Extended
Cachify
Lite Cache
Next Level Cache
Really Static
Super Static Cache
W3 Total Cache
Gator cache
Wordfence Falcon
WP Fastest Cache
WP Rocket
WP Super Cache
Zen Cache (formerly Quick Cache)

Left behind the test:

Brutal Cache - didn't work;

Batcache is a plugin with a Memcache dependency that was not used in the current test.

Autoptimize and Widget Cache are also left out because they are not standalone plugins, but support for others.

Benchmarking tools

We used services from Google, GTMetrix and Yahoo as tools. Thanks to this, not only the page loading speed was tested, but also:

optimization of images;
minification and optimization of js and css code;
using browser caching;
server time delay;
using gzip compression;
placement of scripts;
the number of HTTP requests.
using CDN, parallelization / domain sharding;

Google PageSpeed Insights

The site is checked both from the point of view of a desktop PC and from a mobile device. The result is given on a 100-point scale. The service is easy to use, but provides a relatively crude result that does not fully understand everything that can be improved.

GTMetrix and YSlow

Based on the Yahoo Resource Performance Guide. Again, a 100-point scale is used. The services work with over 50 different metrics. GTMetrix even renders the data into a waterfall diagram of the loading process. In our opinion, this is one of the best tools for identifying ways to improve site performance.

Timing

The following tools were used to determine the page loading speed and check the server operation under load:

ApacheBench

Serves to determine the load on the site, calculates maximum amount requests per second. During the test, 1000 requests were sent over 10 different streams. The test was run 10 times. The best score was recorded for each plugin.

A very famous service for monitoring and testing sites. 20 tests were carried out with each plugin and with the fixation of the best result.

Simple but useful service, showing the time of full page load in your browser. It is not a server-side tool, but a locally run service. We chose the boot method via Ethernet, Opera browser... Each page was loaded 101 times with average load times recorded.

So let's get down to the tests.

Google, GTMetrix and Yslow

The result of testing site pages using the specified services:

As you can see from the table, some plugins did not show themselves here in any way - the score is the same or very close to the score without caching. Google gave the best score for Super cache (for both desktop and mobile). Fastest Cache and Rocket showed the best results in GTmetrix and Yslow. As we already said, the rating from Google is less informative, because it uses fewer factors in the assessment.

So, the best plugins are WP Super Cache, WP Fastest Cache, and WP Rocket Cache.

Timing

Evaluation scores are mainly indicative of the quality of the site code. This gives an understanding of what can be done to speed up the site. At the same time, high ratings of a site does not mean that it loads faster than others. And this is the main mistake - evaluation tools provide an abundance of ideas for improving the site to reduce loading time, but at the same time the load time itself is practically not taken into account. Below is a good example (screenshot from Pingdom).

The page earned 96 out of 100 points (which is better than 99% of pages on any site). In this case, the page is loaded for about 35 seconds. This is what blind optimization can do.

Timing is a very important test because real measurements of page loading speed are carried out.

ApacheBench

Let's find out the maximum number of requests per second that our server can support. How more figure, all the better.

WP Rocket showed the best result. The second and third places were shared by WP-Cache.com and WP Fastest Cache.

Result without caching is 2.78 seconds. All plugins were able to improve this indicator.

The undisputed leader is WPRocket again. Super Cache is second, W3 Total Cache is third.

Here we decided to display not only the average, but also the median test result.

Average load time

The situation is similar to the previous test. The top three have not changed - WPRocket, WPSuperCache and W3 TotalCache.

Median load time

The leader is still WP Rocket, but the practically unknown WP-Cache.com again shows a very good result.

Not caching alone

Of course, not everything depends on caching alone. The choice of the Apache + Nginx bundle, the correctness of the server configuration and its type (dedicated, VPS, shared), the quantity and quality (optimization) of images, and much more play a role.

Output

All plugins presented have different functionality. Some are obscenely simple, while others can be compared to a Swiss knife. Super Cache, W3 and other similar plugins are often used in their work by pros who are familiar with CDNs and other tricks. Other users (especially beginners) opt for more simple plugins(Lite Cache or WP-Cache.com). By the way, WP-Cache.com, despite its little-knownness, was able to show excellent results.

What's the best WordPress caching plugin?

In first place (by a large margin) - WP-Rocket. It has many advantages, but there is one BUT (for many it will be a disadvantage) - it is paid. Developers want $ 39 for it (and updates are not life-time, but only a year)

In second place (although given the free, it can also be put on the first) -WPSuperCache. The results are almost the same as those of the leader, but he is absolutely free!

The third is WP-cache.com. The only confusing thing is that it was last updated in 2014.

But on the other hand, it is simple, free and shows decent results.

Are you trying to make changes to a WordPress blog but the changes won't take effect? For example, have you just added an image, edited a theme, or fixed a mistake in the text of a blog post, but you can't see the changes on the site?

This is most likely due to the caching of site pages by WordPress plugins.

These plugins reduce website load times by generating server-side cache for your WordPress blog. However, sometimes saving a copy of the site can cause inconvenience, especially if you want the changes to take effect immediately.

This guide covers clearing the WordPress cache for the 3 most popular WordPress caching plugins.

What is needed

Before we start, check for the following:

Option 1 - Clearing the cache in WP Super Cache

WordPress Super Cache is the most popular caching plugin with over 1 million WordPress users. Follow these steps to clear the cache in WP Super Cache:

That's all, you have successfully deleted the cached pages.

Option 2 - Clearing the cache in W3 Total Cache

W3 Total Cache is known for its convenience and variety of settings. Some popular blogs like Mashable use this caching plugin. To clear the cache of a WordPress site in W3 Total Cache, follow these steps:

Great, you've just successfully cleared the cache created by the W3 Total Cache plugin.

Option 3 - Clearing the cache in WP Fastest Cache

WP Fastest Cache is a simple and easy to use caching plugin. Follow the steps below to clear the cache in WP Fastest Cache:

That's all, you have successfully deleted the cached files.

Summary

Caching plugins for WordPress are good way speed up the site. However, an outdated cache can cause some inconvenience to your visitors. Throughout this tutorial, you will be introduced to clearing the cache for three popular WordPress caching plugins. If after clearing your cache you still don't see the changes in your WordPress blog try also

Data caching in WordPress can speed up your website and significantly reduce the load on your server. There are three main types of caching in the kernel - page caching, object caching, and pass-through caching. In this article, we will briefly cover all three types, as well as take a look at some of the popular WordPress caching plugins.

What is cache?

The cache is an intermediate buffer that allows you to store the most frequently used data in memory or on a hard disk, which significantly speeds up the process of issuing them. Good examples where it is beneficial to use caching are:

Each of these queries can be accelerated using caching. For example, if we output our last message from Twitter networks on the home page of the site, we do not have to make a request to Twitter every time we visit home page.

It is enough to make one request on the first visit and save the result for a certain time in the cache, and on the next visit to the main page, we can return the saved result from memory much faster.

WordPress caching

There are three main types of caching in WordPress:

Page caching - allows you to save entire pages in the cache, and give them out of the cache on subsequent requests
Object Caching - allows you to cache data of arbitrary type
Pass-through caching - very similar to object caching, allows you to save data for a certain period of time

All three types of caching overlap or depend on each other under certain circumstances. We will tell you more about each type, starting with the simplest and most common.

Page caching in WordPress

It takes a lot of work to display one page of a WordPress archive. These are several queries to the database in order to get the latest posts, widget settings, theme settings, active plugins, site name and description, background image, title and much, much more.

Caching pages (page cache) allows you to save the result of displaying the entire page as a whole. At a subsequent request, the same page is returned to the same address, but from the cache, respectively, much faster and with less load on the server.

When you change the content of a record or page, the page cache is flushed, and on a subsequent request it is already cached new page with updated data.

At the very core of WordPress, page caching is not implemented, but it has everything required functions to implement this at the plugin level. The two most popular page caching plugins are WP Super Cache and W3 Total Cache, although others exist.

WP Super Cache Plugin

WP Super Cache is the most popular WordPress page caching plugin. It allows you to create and emit static HTML files for your pages, and with a certain configuration, you can configure the delivery of these pages directly by your web server (Apache or nginx), bypassing the processing PHP files generally.

Newer versions of the WP Super Cache plugin have some additional functions, for example, setting up a CDN, supporting a mobile version of the site, etc., but the main essence of this plugin is page caching.

WP Super Cache is suitable for both beginners and more advanced WordPress users, but since it uses file system for caching, it will be extremely difficult to use for a site with two or more web servers.

The W3 Total Cache plugin is younger than WP Super Cache, but not inferior in functionality. It is gaining popularity very quickly, and today has over 2 million downloads from the WordPress.org directory.

W3 Total Cache allows you to store cached pages both on your hard drive and in memory. It does not preserve the cache structure as WP Super Cache does, so configure the issue without using PHP impossible, but unlike WP Super Cache, the use of external storage makes it easy to work in a multi-server architecture.

W3 Total Cache has a huge number of settings and additional functionality, including CDN support, caching database queries, compression of scripts and styles, and much more. We recommend W3 Total Cache for more advanced WordPress users.

At the time of this writing, the Batcache plugin has only been downloaded about ten thousand times from the WordPress.org directory, but this case this is not an indication of its effectiveness. In terms of performance, it is not inferior to either WP Super Cache or W3 Total Cache.

The Batcache plugin has only one function - page caching, but it does it flawlessly. Batcache uses external object caching to store data, making it easy to use in a multi-server architecture. This plugin is used in large network WordPress.com, with over 40 million sites, over 2000 servers and over 10 billion page views every month.

Which page caching plugin you choose depends on the size of your site, your capabilities, and your experience with WordPress. If you are not using page caching plugins at the moment, we always recommend starting with WP Super Cache. If more power and finer caching configuration is important to you, try W3 Total Cache. If you are good at programming and server administration and are willing to donate graphical interface on setup - try Batcache.

Object caching in WordPress

Object caching is implemented in the very core of WordPress. This mechanism allows you to store objects of arbitrary type in memory and is useful mainly for WordPress theme and plugin developers.

For example, when requesting an option from the MySQL database using the get_option function, WordPress will save the result of this function in memory, and upon the next such call, it will return the result from memory without making any queries to the database.

Similar caching in the core is implemented for many objects, including: options, posts (pages, and custom types), post metadata, terms, and taxonomies. This is why WordPress developers should not be afraid to use functions such as get_option and get_post as they are such calls do not cause unnecessary queries to the database.

Object caching in WordPress is done through a number of internal functions, including: wp_cache_add, wp_cache_set, wp_cache_get.

Persistent object caching

It's important to know that WordPress object caching is not persistent by default. This means that the cached values are valid for only one page request, and on subsequent requests, the cache is generated from scratch.

At first glance, this is completely unprofitable, but if you count how many times WordPress calls the get_option function to process a single request (about 500 times), then the benefits of object caching become obvious.

However, persistent object caching (or external caching) in WordPress is easily implemented using third-party plugins like Memcached Object Cache or APC Object Cache. Both plugins allow you to use the server's RAM to store WordPress objects, while the objects do not disappear when the request ends. This approach significantly reduces the load on the MySQL database.

It is also worth noting that when page caching is enabled, most often the time does not reach the work with stored objects, since the entire page is retrieved from the cache. This is not a reason to disable object caching, especially when working with users who are logged in, and some plugins (for example Batcache) generally use object caching to store pages.

Pass-through caching in WordPress

For users this method caching is completely transparent. Transient cache allows developers to save data for a certain period of time. This method is implemented in WordPress using the get_transient, set_transient and delete_transient functions.

Transit caching is most often used to store fragments, especially when it comes to requests for external resources, for example, to display a message from the Twitter network or to display a weather forecast from a third-party service.

Similar caching is also used in the kernel when working with RSS feeds, and requests to update WordPress themes, plugins and core.

Unlike object caching, pass-through caching is persistent by default in WordPress, and stores all data in the database. But it is important to note that when using a plugin for external object caching (such as Memcached or APC), pass-through caching will use this plugin for storing data.

Object caching or pass-through caching?

It's easy for developers to choose between the two methods. If we need to store the result for a certain period of time and for more than one request, it is best to use transit caching. If we need to keep a small object in memory only for the current request, object caching is fine. If you need to save something for an indefinite period of time, the easiest way is to use the options - then there is a guarantee that the value will get into the database.

When using a plugin for persistent object caching, all three methods will use this plugin.

Conclusion

Caching plays an important role in improving the performance and speed of sites, as well as optimizing them for high loads. In most cases, this is not so important for sites with low traffic, although it is always nice when the site opens faster.

For most sites, simple page caching solves all issues with speed and load. This is the first thing to do when problems arise, especially on cheap hosting sites. Page caching plugins are easy to install and configure.

Object caching and trick caching are fairly transparent to WordPress users, but it is important for developers to be familiar with and separate the two. External object caching plugins often require more configuration work than page caching.

Finally, remember that caching is just one way to improve the speed of your site. If speed is important to you, don't forget about image optimization, compression of scripts and styles, query and database optimization, using CDN servers and load balancing.

If you have any questions about caching in WordPress or problems configuring a caching plugin, please leave a comment and we will be happy to help you.

02.07.2013 05.11.2013

Co-founder of WP Magazine and the first WordCamp conference in Russia. Developer at Automattic, actively involved in the development of the WordPress core. Favorite programming language: Python.

WordPress is a great engine for easy website management. This core contains many features that you can constantly add. But this is the insidiousness of this CMS-system - it is so functional that some webmasters, adding new modules, do not notice how the site starts to slow down.

To avoid becoming a victim slow work engine, you need to take some additional measures.

The best way to speed up the display of your resource within the user's browser is to install special plugins.

Use a cache and the slow WordPress problem will disappear on its own.

Why Cache Speeds Up WordPress - How It Happens

It is unclear to many how creating cached copies can improve the performance of an entire resource. But once you figure it out a little, everything becomes very clear. The fact is that the browser only understands html language... And the WordPress engine deals with php files - all its functions are located in this format on the server. You will not be able to get a picture of the site from the browser if the data is not previously converted to a different format.

When the user wants to open the page, a request is made to the server. This request "pulls" the desired part of the site and creates a copy of it in a format suitable for the browser. As a result, the user sees the same page, only it is no longer a php file. And it takes a certain amount of time for the server to change the format. And the more configurations, material and functions there are on the page, the longer it takes to reformat the data. Thus, over time, when the number of plugins and modules on the engine builds up, WordPress starts to run slower.

To prevent the server from rushing from one part of the site to another, creating copies of pages in the desired format, use the cache. It works on the following principle: when someone makes a request for a page, a copy of it is created and placed in the cache. As a result, the hosting does not have to make copies every time someone makes a request - they are already in a specially designated directory. As a result, for the browser this will bring increased page load speed, and for the site - improved server response rates and trust from the search engines. After all, the loading speed of a WordPress site is another important ranking factor.

To make a cache of pages and configurations for accelerated work the user's browser and improve the position of the resource in the search results, use special WordPress plugins.

WP Hyper Cache

WP Hyper Cache is the best plugin of its kind. It will allow not only creating a cache in response to requests, but also doing it automatically without processing php files. The module is constantly updated and there is already a cache for mobile versions of WordPress sites. In addition, this module is distributed free of charge, so today, without spending a penny, you can speed up the work of your site.

Please note that the plugin requires special installation. By default, the caching feature in WordPress is disabled - you need to enable it. To do this, you need to dig a little in the wp-config.php file. Find the following line in it:

define ("WPLANG", "ru_RU");

(this is after installing the plugin on WordPress, but before activating it). After the above line, insert the following tag:

define ("WP_CACHE", true);

After the installation is complete, you need to properly configure the WordPress Hyper Cache plugin to work. Here are the main settings you need to adjust:

The caching timeout is the time that the page cache will be kept for the user's browser. The timeout is needed so that the pages do not lose their relevance. After all, you can make new settings in your blog, but they will not be displayed, because users see the old version of the site.
Cache invalidation mode is a condition under which the cache will be automatically deleted.
Disable commentator cache is an important setting for active blogs. Users do not like to wait for their comment to appear on the page, so in order to avoid objections, it is better to disable caching for this element.
RSS caching - it is not worth creating a cache for feeds, as this is dynamic information that may become out of date due to delays.

If you have a responsive site, then you should enable the function “Define mobile devices”. It will help to correctly display pages, the appearance of which changes when switching to the mobile version (some widgets disappear, and the sizes are also adjusted). If you do not have a mobile version of the WordPress site, then you can leave the checkbox unchecked - the plugin will not create additional copies under a different name.

When a text cache is created, if you have a lot of information on your site, there may be a problem on the server with a lack of workspace. To avoid such problems, it is recommended to enable the text compression function in the plugin.

Why do I need to clear my WordPress cache?

Sometimes the cache can be harmful. For example, when you entered some new function or changed the structure of the page. In such cases, you should clear the cache. Otherwise, users simply won't see any changes on your site. It is recommended to immediately indicate the prohibition on caching the main page, if it is dynamic, or include in the filter URLs by which the latest entries are displayed - that is, category links.

It is very easy to clear the cache in WP Hyper Cache plugin - just one click to delete old copies of pages from the server. In the module statistics, you will see the number of cached pages. If there are too many of them, delete them. Or set a small caching timeout so that the cache is cleaned without your participation and does not bother you.

Other caching plugins

WP Super Cache is the main competitor of the Hyper Cache plugin. It works by modifying the .htaccess file on the hosting. When visiting the site, the user is automatically redirected to a cached copy of the page. Although the plugin functions reliably, it is still inferior to its competitor - it gives an increase in download speed by 15% less than Hyper Cache.
Widget Cache is a module that will allow you not to create caches of the whole page, but only to copy widgets on the hosting. After all, it is the functional blocks in the sidebar that give the greatest load on many sites.
Total Cache is a plugin for professional webmasters. Its feature is in a wide range of settings. If you are an experienced programmer, then you can change this module in your own way, adding many filters and caching conditions.

Hello dear readers of the blog site. In this article, I will continue the topic of WordPress optimization () in order to reduce its load on the hosting server. This question will become more relevant to you, the more visitors come to your blog.

In the previous article, a few were described. But these are, of course, only half measures that must be performed in combination with other methods.

There are a lot of optimization methods, and I will talk about all of them in detail in this series of articles. Today we will look at one of the most powerful of them, namely caching. First you need to decide what it is and why you need to use it. First, let's take a look at how a WordPress blog works without a cache.

WordPress caching and how the blog works

The thing is that browsers only work with web pages in HTML () format and do not understand at all PHP language, on which, in fact, this engine is written. Therefore, WordPress, after the user turns to a particular blog page, must have time to form this page based on the algorithm written in its PHP code.

In a classic static site (there are very few of them now), all web pages actually exist and are located on your hosting server. You can always contact them by entering the appropriate address in the browser, or even physically, via FTP, download some page from the server to your computer and open it by double-clicking on it. As they say, you can touch it.

Based on these templates, the graphic design of the requested web page is created, and then, for example, the text of the article is loaded into the content area from the MySql database. The sidebar area can also be loaded with data from the MySQL database, if you use the output of any information in it regular means WordPress or using plugins.

As you have probably already noticed, this way of generating web pages for the browser hides in itself some problem, which can be especially acute with a large number of visitors to the blog. The code of files written in PHP is interpreted into an HTML page on the fly.

If there are a lot of requests to the database for creating pages (with high traffic to the blog), then this can significantly load the hosting. Even if we assume that all visitors currently on your site have requested the same page, it will still be created in WordPress as many times as the number of visitors clicked on the corresponding link.

The way out of this situation is using the cache... How does caching work in WordPress? Pretty simple. Every time a page in HTML format is generated on the server at the request of a visitor, it is not only transmitted to the browser of the user who clicked on the link, but also saved in the corresponding folder of your site.

And already the next time this page is accessed, it will not be re-generated, taking away the server resource (creating an additional load on its processor and RAM), but will be transferred to the browser of the user who requested this page from the same folder on your site where cached web pages.

This method, when the entire web page is cached, is the most efficient, but not the only one possible. Also, some dynamic elements of your blog might not work.

Some WordPress plugins only cache database queries and therefore allow dynamic elements to work. Still, caching entire web pages is, in my opinion, the most efficient way.

The hero of today's publication (the Hyper Cache plugin) caches entire pages and stores their HTML versions in his cache folder. Interestingly, caching only works for unregistered visitors to your blog. Because most bloggers do not use registration, then the only registered user in this case will be only the administrator, i.e. you.

For you, caching will not work and it is very convenient. For example, when you make design changes, you don't have to flush the cache every time to see the results of the changes. I want to give an example of the effectiveness of using this extension in WordPress.

Hosting is good, but for free it is excellent. But one day they flew HDD where the databases of all users were located. And what is noteworthy, my blog continued to work quietly at the same time, because its pages were opened from the cache and at the same time there were no calls to the database at all, because she was not available.

Which also had caching enabled, but did not work, complaining about the unavailability of the database. The lifetime of HTML copies of web pages in the cache was 1440 minutes (one day), and this turned out to be longer than the time during which the hosting database was inactive (several hours).

Here is such a wonderful plugin for caching in WordPress. Well, I think that the theory is enough and it's time to consider directly its installation and configuration.

Installing the Hyper Cache plugin on WordPress

Download Hyper Cache you can from the official page. Next, we carry out the standard installation steps. Unpack the hyper-cache.zip archive, using ftp-manager (), connect to your site and upload the hyper-cache folder to the wp-content / plugins / plugins folder on the remote host.

Next, you will need to enable caching in the WordPress engine itself. To do this, we need to open the wp-config.php configuration file for editing, which you can find in the root folder on your site server. You only need to add one line of code to it:

Define ("WP_CACHE", true);

You can insert it anywhere before the line:

/ ** The absolute path to the WordPress directory. * / if (! defined ("ABSPATH")) define ("ABSPATH", dirname (__ FILE__). "/");

For example, I inserted into the area where the parameters for the database are being set:

/ ** Database name for WordPress * / define ("WP_CACHE", true); define ("DB_NAME", "wm1604_ox823");

Enter the WordPress admin panel, select the "Plugins" - "Inactive" tab, find the line with this plugin and activate it. Next, select Options -> Hyper Cache from the left menu. If no warning messages appear in the settings window, then everything is ready to go.

If warnings appear, then setting access rights to 777 for the folder will most likely help (read about this in the article about Filesila at the link given just above) wp-content or the wp-content / plugins / hyper-cache folder.

This is so that this plugin can create a folder in WordPress to store cached web pages called cache. After he creates it, you can return the permissions () to the wp-content folder and the wp-content / plugins / hyper-cache folder back to 755, and already the cache folder, which I have in wp-content / plugins / hyper-cache / cache, assign permissions 777 so that Hyper Cache can write to and erase HTML files with the cache.

Hyper Cache settings to reduce server load

In the first field of settings (in the left menu select Options - Header Cache) called "Files in cache", you can see how many web pages of your blog are currently stored in the cache.

In the same field there is a very important button "Clear cache", which allows you to flush the cache, i.e. delete all files from the folder designated for this purpose. You may need this button if, for example, you've made design changes and want your visitors to see them as quickly as possible. Because otherwise, only cached versions of web pages will still be available to them.

In the area of "Configuration" the main settings are concentrated.

In the field "Timeout of cached pages" you can set the lifetime of the cache in WordPress. During this time, HTML copies of your blog's web pages will be stored in the cache folder, and all users who request them will receive exactly these copies.

But as soon as the time specified in this field for a web page expires, the next time a visitor accesses it, it will no longer be opened from the cache, but in a standard way. In this case, it will be re-cached by the plugin and placed in cache folder... If the lifetime is set too short, then Hyper Cache, instead of unloading the server, will give it an increased load associated with constant writing of cached web pages.

The "Cache invalidation mode" field specifies how the cache is cleared when new articles are added to your blog or when existing articles are updated (including when adding comments). If you select "All cached pages" from the drop-down list, then when adding new entry or updating an existing one, the entire cache in WordPress will be updated (cleared). If you select "Nothing", the cache will remain unchanged.

When choosing "Only changed records" only the cache files of the web pages that have changed will be updated (removed from the cache). Checkmark in the field “When canceling a record, also cancel home page, pages of archives and categories ”will add convenience to you when working with your blog.

You can check the box "Disable commentator cache". In this case, users will be able to see the comments they have added without waiting for the cache lifetime for this web page. This makes caching in WordPress less efficient, but the blog itself is more usable. Checking the "RSS Caching" box will allow you to cache the RSS feed.

In the "Compression" area, by ticking the boxes provided, you can pages that are in the cache. This will allow speed up page loading a little your blog.

In the "Expert settings" area, it will be desirable to check the box "URL with parameters"... In my case, after installing it, the blog hosting load has halved.

I don't know all the ins and outs, but despite the urls with all sorts of signs, questions and other nonsense that WordPress can generate, someone turns to such pages (bots or someone else) and they should also be cached.

In the "Home caching" box, you can check the box to disable caching of the home page. This may be necessary if it is being updated intensively and enabling its caching can cause additional overhead due to constant file overwriting.

Do not forget to save the changes made in the settings window of the Hyper Cache plugin by clicking on the "Update" button. To check if caching is working, you will need to go to your blog not as a registered user, but as a regular visitor. To do this, you can simply open it in a browser other than the one in which you work as an administrator.

Open any blog page and see its source code. To do this, you need to click right click mouse over the page in your browser and select the item context menu Source Code (), or Page Source (Firefox), or View Page Code ( Google chrome) or View HTML Code (IE).

If you see at the very bottom of the window with source code something like

then this will mean that Hyper Cache is working and on the next request it will open this page from the cache.

Good luck to you! See you soon on the pages of the blog site