Answers.Body: <p>If it helps, we're running with <a href="https://wordpress.org/plugins/wp-super-cache/" rel="nofollow">WP Super Cache</a> and it works fine. Civi pages are excluded. It's extremely fast, and the associated lack of PHP processing takes some strain off the server, so there's a corresponding speed bump in Civi too.</p>
  
  <p>(Super Cache used to need <a href="http://wiki.civicrm.org/confluence/display/CRMDOC/WordPress+plugins+incompatible+with+CiviCRM" rel="nofollow">a hack</a> to work, but latest versions seem to be ok)</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-29T12:58:23.520Z
Answers.LastActivityDate: 2015-04-29T12:58:23.520Z
Answers.UserDisplayName: Andrew West
Answers.Body: <p>No experience with any of these tools, my recommendation would be to try with a sandbox site first and see what happens.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-28T08:38:10.437Z
Answers.LastActivityDate: 2015-04-28T08:38:10.437Z
Answers.UserDisplayName: ErikH - CiviCooP
Answers.Body: <p>Most of the pages displayed by civicrm can potentially be customised per user (eg. pre-fill the contribution form if the visitor is known or display "looks like you are already registered" on an event page for instance).</p>
  
  <p>So if you start generating a page for one specific visitor, cache it  and distribute the result to all visitors, there is a big risk you will show information about one visitor to all the others, and finetuning which specific page is cache safe is going to be tricky</p>
  
  <p>However, it seems that the falcon cache allow you to explicitly exclude some pages, so you could exclude every civicrm page and still benefit from the cache for all your other pages (eg. your articles).</p>
  
  <p>That's what I'd suggest you to do. The potential speed gain isn't worthwhile the risk of showing private information to the wrong visitor.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-28T11:53:08.203Z
Answers.Text: Great, thanks @Xavier. This is what I suspected, but I thought I'd check.
Answers.UserDisplayName: Vshura
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-28T09:31:28.060Z
Answers.LastActivityDate: 2015-04-29T10:13:18.077Z
Answers.LastEditDate: 2015-04-29T10:13:18.077Z
Answers.UserDisplayName: Xavier
Body: <p>I'm using CiviCRM on Wordpress, and recently installed <a href="http://www.wordfence.com/" rel="nofollow">Wordfence</a>, an excellent security plugin to make my installation more secure. It also offers the <a href="http://docs.wordfence.com/en/Falcon_Cache" rel="nofollow">Faclon Engine</a>, a server-side caching system which promises to speed up the website by 30-50 times. </p>
  
  <p>While my installation of CiviCRM isn't too slow, some more speed would be welcome.  However, due to the sometimes complex php searches and apis that CiviCRM runs, I was wondering if it'll lead to mistakes / crashes when running.</p>
  
  <p>Does anyone have a sense if these kinds of engines are ok with CiviCRM or if they're better avoided?</p>
  
  <p>Thanks.</p>
  
Tags: <wordpress>
Title: Does CiviCRM work with Site Performance Engines in Wordpress such as Falcon?
ThreadText: # Does CiviCRM work with Site Performance Engines in Wordpress such as Falcon?
  
  (Asked by: username_0 on 2015-04-28)
  
  I'm using CiviCRM on Wordpress, and recently installed [Wordfence](http://www.wordfence.com/), an excellent security plugin to make my installation more secure. It also offers the [Faclon Engine](http://docs.wordfence.com/en/Falcon_Cache), a server-side caching system which promises to speed up the website by 30-50 times.
  
  While my installation of CiviCRM isn't too slow, some more speed would be welcome. However, due to the sometimes complex php searches and apis that CiviCRM runs, I was wondering if it'll lead to mistakes / crashes when running.
  
  Does anyone have a sense if these kinds of engines are ok with CiviCRM or if they're better avoided?
  
  Thanks.
  
  **Tags:** wordpress
  
  
  ---
  
  ## 3 answers
  
  ### Answer by username_3 on 2015-04-28. Score: 5 | Accepted answer
  
  Most of the pages displayed by civicrm can potentially be customised per user (eg. pre-fill the contribution form if the visitor is known or display "looks like you are already registered" on an event page for instance).
  
  So if you start generating a page for one specific visitor, cache it and distribute the result to all visitors, there is a big risk you will show information about one visitor to all the others, and finetuning which specific page is cache safe is going to be tricky
  
  However, it seems that the falcon cache allow you to explicitly exclude some pages, so you could exclude every civicrm page and still benefit from the cache for all your other pages (eg. your articles).
  
  That's what I'd suggest you to do. The potential speed gain isn't worthwhile the risk of showing private information to the wrong visitor.
  
  > **Comments:**
  > **username_0**: Great, thanks @username_3. This is what I suspected, but I thought I'd check.  
  
  ---
  
  ### Answer by username_1 on 2015-04-29. Score: 3
  
  If it helps, we're running with [WP Super Cache](https://wordpress.org/plugins/wp-super-cache/) and it works fine. Civi pages are excluded. It's extremely fast, and the associated lack of PHP processing takes some strain off the server, so there's a corresponding speed bump in Civi too.
  
  (Super Cache used to need [a hack](http://wiki.civicrm.org/confluence/display/CRMDOC/WordPress+plugins+incompatible+with+CiviCRM) to work, but latest versions seem to be ok)
  
  
  ---
  
  ### Answer by username_2 on 2015-04-28. Score: 0
  
  No experience with any of these tools, my recommendation would be to try with a sandbox site first and see what happens.
  
  
  ---
  
  