Caching can give the impression of being the “holy grail” for all performance problems. It is no wonder that people raise an eyebrow when I say “Stop using caching” in my presentations, meetups or workshops. For some, especially in the WordPress Community I have become the guy that hates caching. Hence, it is time to make clear what I really mean about this topic, when and for what it should be used. And maybe most importantly, when not to use caching – and look for alternative solutions. When should you use Full Page Caching? Let’s start with the biggest of them all. Full Page Caching, or just page caching. A technique where you temporarily store a pre-generated version of a page to deliver the exact same code (HTML) to visitors in a limited time span. This is how full page caching works: Visitor A visits abc.com/page. This page is not in the cache, and hits PHP and gets generated from the database. Before it is served to Visitor A, it is also stored in the full page cache with an expiry of 10 minutes. Visitor B visits abc.com/page 2 minutes after Visitor A, and is therefore served with the same page, but this time directly from the cache. The pages
Share This