Server-level page caching with a web server like Nginx .

[mouakter13]

The blog post you are reading is the perfect example of a page that does not need to be generated dynamically. Like many of our other posts , the content of this post is designed to be static, so there is no need to spend CPU resources to continuously generate identical pages.

Instead, it's better to have PHP generate the page once and then cache it. Page caching has many obvious advantages over dynamic page generation with PHP.

For example, imagine a blog post on your site goes viral and receives 100,000 page views within a few hours of being published. Without page caching, your PHP threads would likely be overwhelmed and your server would crash.

With page caching, only the first page view would be generated denmark phone number data dynamically. The other 99,999 requests would be served from your page cache, which uses relatively little CPU resources.

There are two ways to configure page caching for your WordPress site.

Page caching based on a WordPress plugin like WP-Rocket .
For maximum performance, we recommend using server-level page caching whenever possible. At Kinsta, all of our pages use Nginx’s FastCGI caching module for super-fast performance.

If your host does not offer the option of server-level page caching, the next best option is to use a WordPress caching plugin to implement application-level page caching.

Object Cache
For WooCommerce stores , community forums, and other WordPress sites that can't make efficient use of page caching, adding a persistent object cache like Redis in front of your MySQL database can increase performance and reduce the load on PHP threads.

Without a persistent object cache, MySQL database queries will be executed for every request, even if the result is identical to a previous query.

For example, a community forum site that avoids page caching will make separate identical queries to the database to obtain post data in order to build a page.