Add to that:
6. Theme Caching via Avada (our theme)
For now, we clearing our cache in the following sequence: (from lowest to highest order)
1. Theme Caching
2. Page Caching
3. Dynamic Caching
4. Object Caching (Memcached)
5. Edge Caching
6. Browser Caching
Thoughts?
Thank you!
Using more than one cache system concurrently is not a correct idea. you can use only wp fastest cache and cloudflare.
In theory that sounds great, but our site is hosted by SiteGround and they offer Dynamic Caching (hard-coded, cannot disable it) and Memcached (optional, but helps boost our website speed).
The other cache layers are expected (Theme cache, Page Caching via WPFC, and Browser Cache).
So, based on the above, are you saying we don’t need to use Memcached when using your plugin?
Thank you.
yes, you do not need to use Memcached.
what is Dynamic Cache? What it is used for?
OK, we’ll test our site with and without Memcached.
Concerning Dynamic Caching. Here goes ….
Details: Dynamic Cache (SiteGround).
We’ve noticed that when we make a change to our site or publish a new blog, our changes are not shown on the frontend until we purge our dynamic cache. Dynamic cache is currently standing between your plugin and the frontend.
We’ll consult SiteGround to find out if there’s a programmatic way to disable it and the consequences.
Cheers!
Update:
This great article explains SiteGround’s server caching system. We’re still waiting for them to tell us how to programatically disable Dynamic Caching. So far, no solid answers. Stay tuned.
Cheers!
Update:
So, for those using SiteGround as their host, there are two ways to disable their Dynamic Caching system (when not using their plugin, Speed Optimizer):
- Contact SiteGround Support. They will disable it at their end.
OR
- Add the rule provided below to your .htaccess file.
Note: When disabling SiteGround’s Dynamic Caching, HTTP header checks for your website will always display the following:
x-proxy-cache: MISS
We plan to test our site with SG’s Dynamic Caching enabled and also disabled, then report back here the results and recommendations as they impact the use of WPFC.
Thank you!
—————————-
HTACCESS Rule to Disable SiteGround’s Dynamic Caching:
<IfModule mod_headers.c>
Header set Cache-Control "private"
</IfModule>
then you can use dynamic cache instead of proxy cache.
Sorry. Your statement is confusing. If Dynamic Cache is disabled with SiteGround (as explained above), then Proxy Cache is disabled as well. They are both the same as suggested by this article. What did we miss?
ow I got it wrong. you can disable the dynamic cache.
Update:
We disabled SiteGround’s Dynamic (i.e., Proxy) caching via the htaccess rule provided above and conducted several tests.
Result: No issues and no impact to our website performance since we’re already covered by this plugin and Cloudflare APO.
Benefit: Files purged faster and one less cache layer to worry about.
All good. Closing this topic as “Resolved.”
Update:
So, we completed additional tests and confirmed the only caching layers needed when using this plugin are:
1. Theme Caching (built into many themes, like Avada)
2. Page Caching (this plugin)
3. Edge Caching (CDN, like Cloudflare APO)
Notes:
1. Memcached (object caching) is not recommended for shared hosting environments like ours.
2. If you’re connected to a CDN via this plugin, and making changes to your website, all you have to do is clear or purge your page caching (this plugin) and the changes will automatically appear on the frontend. If not, simply clear your browser cache to see them.
