Title: Page cache
Last modified: May 24, 2018

---

# Page cache

 *  Resolved [incognito0](https://wordpress.org/support/users/incognito0/)
 * (@incognito0)
 * [8 years ago](https://wordpress.org/support/topic/page-cache-2/)
 * Hi,
 * this might be a silly question but do i have to pay attention for something when
   using NinjaFirewall together with a page caching plugin like W3TC? When i activate
   the firewall (full WAF, user.ini) the respond time of my server decreases massively.
   When i deactivate the page cache i get the same decrease. Has this anything to
   do with how php sessions work?
 * Thanks for your help!

Viewing 4 replies - 1 through 4 (of 4 total)

 *  Plugin Author [nintechnet](https://wordpress.org/support/users/nintechnet/)
 * (@nintechnet)
 * [8 years ago](https://wordpress.org/support/topic/page-cache-2/#post-10319572)
 * Hi,
 * Maybe it’s an issue with PHP session. I remember someone who mentioned they were
   having problem with a shopping card plugin using PHP sessions and the W3TC CDN
   option. Can you check this?
    Alternatively, as you mentioned that the issue is
   still present after disabling W3TC, maybe there is a conflict with some rules
   and directives it added to you .htaccess? Did you try to flush the cache too?
 *  Thread Starter [incognito0](https://wordpress.org/support/users/incognito0/)
 * (@incognito0)
 * [8 years ago](https://wordpress.org/support/topic/page-cache-2/#post-10319780)
 * Hi,
 * i don’t have any shopping cards or active CDN.
 * I thought that ninjafirewall might somehow prevent the usage of the page cache.
   I read elsewhere that phpsessid might have to do with this as it might force 
   the regeneration of the cache for every single user. But i didn’t find anyone
   mentioning it here.
 * I tested the loading time with pingdom:
    – W3TC + Ninja: 2,9s – Ninja: 4,78s –
   Nothing: 4,77 – W3TC: 0,99s
 * There might be some scattering and i am not sure if there is really a differenc
   between Ninja and W3TC+Ninja. But it obviously has something to do with the page
   cache.
 *  Thread Starter [incognito0](https://wordpress.org/support/users/incognito0/)
 * (@incognito0)
 * [8 years ago](https://wordpress.org/support/topic/page-cache-2/#post-10320853)
 * Hi again,
 * i don’t know why but my problem seems to be solved. In addition to other attempts,
   I changed the cache mode to basic, which has improved the performance considerably.
   Afterwards i changed it back to disk enhanced and now everything seems to work
   fine again. Maybe you were right about the htacces. But deactivation and reactivation
   of the plugin didn’t solve the problem at first.
 * I am going to observe this the next few days and if the problem doesn’t reappear
   i will mark this as resolved.
    Thanks for your help!
 *  Plugin Author [nintechnet](https://wordpress.org/support/users/nintechnet/)
 * (@nintechnet)
 * [8 years ago](https://wordpress.org/support/topic/page-cache-2/#post-10321285)
 * Maybe the changes you made completely flushed the cache and helped to solve the
   problem.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Page cache’ is closed to new replies.

 * ![](https://ps.w.org/ninjafirewall/assets/icon-256x256.png?rev=976137)
 * [NinjaFirewall (WP Edition) - Advanced Security Plugin and Firewall](https://wordpress.org/plugins/ninjafirewall/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/ninjafirewall/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/ninjafirewall/)
 * [Active Topics](https://wordpress.org/support/plugin/ninjafirewall/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/ninjafirewall/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/ninjafirewall/reviews/)

## Tags

 * [page-cache](https://wordpress.org/support/topic-tag/page-cache/)
 * [W3TC](https://wordpress.org/support/topic-tag/w3tc/)

 * 4 replies
 * 2 participants
 * Last reply from: [nintechnet](https://wordpress.org/support/users/nintechnet/)
 * Last activity: [8 years ago](https://wordpress.org/support/topic/page-cache-2/#post-10321285)
 * Status: resolved