FAQ: Full Page Cache

The cause of the issue is "Collect Page Visit Statistics" option which is set to "No". Read the full answer to get a complete instruction on how to solve the current issue.

A large number of pages may receive "Cache miss" status because 'curl' is used as the User Agent.
Read the full answer to see the settings.

Yes, the Full Page Cache extension offers to apply the hole punch to blocks. See the complete answer to learn the full list. 

Yes, sure you can keep all the checkout pages uncached for correct operation of the process. Use special settings listed in the full answer to conduct caching of the needed areas.

Yes, the Full Page Cache extension supports Redis. To see the full list of supported Magento caches continue reading.

It depends on your current TTFB and server. According to the tests we conducted, our FPC extension can save seconds of loading time which may be critical for your visitors and ROI as a result. Read on to see the tests results.

For the Full Page Cache module, there are four available cache storages that will influence the overall cache performance. These are Redis, Database, Server, Memcache and each one of them has its pros and cons. Read the full answer to get more details on them.

The extension supports responsive mobile interface. All you need for this is to enable mobile design in the general settings section. Go on reading to follow detailed instructions.

The order of links in the file is the order of their crawling. Read the full answer to get more information.

Unfortunately, the current behavior is common for websites with a high quantity of pages and visits. Please read the long answer to learn a few workarounds for the problem.