Configure full page cache for your site to increase performance and ease the load on your WordPress pods.
The Backend field allows you to choose between Memcached and Redis for your cache. With Memcached there is no additional configuration required from your side, as it uses the same instance used for the WordPress Object Cache.
If you want to use Redis instead, you will have to deploy Redis and specify its Host and Port.
For more page cache settings, select Show Advanced Settings.
Cacheable Response Status Codes specify which pages will be cached based on their HTTP response status codes.
Default TTL specifies the default duration in seconds after which the cached pages will expire. The value is
ignored if a duration is specified in one of the
Expires response headers.
Honor bypass from response headers allows bypassing caching pages when specified so by the
Cache-Control or the
Expires response headers, in the following cases:
Cache-Control: privateis present, the page is not cached;
Cache-Control: no-storeis present, the page is not cached;
Cache-Control: no-cacheis present, the page is not cached;
Cache-Control: max-age=0is present, the page is not cached;
Expires: <date-from-the-past>is present, the page is not cached.
Bypassing the page cache
Currently the page cache is automatically bypassed in the following situations:
- if the user is logged in or if there are other cookies that might indicate dynamic content is expected;
- if the request URI contains any query parameters (e.g.
/?page=2); in the future, we plan on adding support for stripping certain parameters or allowing them to be cached.
- for some sensible locations, such as: sitemaps, feed, admin-ajax, wp-login etc.
For more details, you may consult our nginx config for page caching .
In this section you can create custom environment variables, that you can later use in your code.
This Events section contains logs about the events that take place within your site.
Here you'll find concise steps and pre-filled commands to perform common operations.
When you click on the **Logs** section, you'll be redirected to your Google account, to the Google [...]