![[Pagely® SupportOps] Help Center home page](http://theme.zdassets.com/theme_assets/32062/2ad21ef41cc48fa0c78ae52fe62dc22906fcb7f3.png)
PressCACHE™ is our caching mechanism used at Pagely and is backed by NGINX‘s powerful and robust caching technology. This is a key component of our architecture that produces extremely fast performance for your WordPress sites. Settings are accessed directly via your WordPress admin screens where you may turn it on/off, or enable developer mode. There is really nothing else to do other than turn it on, and enjoy the speed.
How PressCACHE™ Works
A visitor arrives at a page on your site. Pagely caching technology decides if it’s safe to serve them a cached page.
Cache will not be served if:
Cache will not be served if:
- The site is in preview mode.
- They are logged into Wordpress, due to the possibility of user-specific content on the page.
- They have a cookie marking them as a commenter, since all comment forms will populate with the user’s name and email.
- They have a PHP session started, as serving cache may expose private data from pulling a value unique to the user and their session.
- It is not a GET request, such as a POST request.
If it is safe to serve a cached page, a key is built which represents the page. With that, a check is done to ensure a copy of the page already exists in the cache. If it exists, it is served from the cache. Otherwise, the page is processed normally and as long as the page does not return an error or set cookies, a new copy of the page will be added to cache before serving the results.