Full Page Cache + Cache Crawler(v.1.6.1)
A reliable solution to significantly speed up your Magento store. Reduce your server load, decrease page load time and thus enhance website google ranking and sales conversion.
- Significantly speeds up your website. 150ms time to first byte are real! See our demo for the proof
- Cache crawler to keep cache always warmed
- Decreasing server load and reduces hardware requirements
- Easily add a block/page to exceptions list
- Per page statistics
- Clean code
Lifetime free support, bugfixes and updates.
Reliable and robust solution to significantly speed up your Magento store.
Each visitor of a web-store is a potential buyer. It is very important to load a webpage as fast as possible because a potential buyer can leave your website because of slow website performance. The main purpose of Full Page Cache (FPC) extension is to prepare cached version of Magento storefront pages. In other words, the extension is aimed to provide the minimum response time (Time to First Byte, TTFB).
The TTFB of a basic (“clean”) installation of Magento is about 2 seconds. If you install any popular custom frontend theme, then TTFB will be about 10 seconds. FPC extension remarkably decreases TTFB. Sales conversion depends directly on load time because a delay in page load may result in losing customers. That’s why installation of Full Page Cache extension is a must today.
Why should you choose Full Page Cache by PotatoCommerce
The main difference of our extension from its analogs is that we always improve our Full Page Cache Magento extension. FPC is one of our strategic products, and we invest a lot in it. We receive valuable customer feedback and we do our best to consider it in development.
From the technical point of view, the difference is the following:
- We have chosen a realization that is focused on reaching minimum TTFB (time to first byte, response time in other words);
- Easy-to-use and well-documented FPC API User Guide, which allows easily make a compatibility with 3rd-party extensions;
- We have paid a lot of attention to cache control (flush by tag, events; cache size);
- Our FPC extension has built-in cache warmer, while some other vendors ask you to purchase a separate extension, which is obviously must be a part of FPC extension. Our crawler is better than any other because our crawler warms most popular pages first. Thus, your top pages will be cached first if cache flushed or expired;
- We offer free lifetime support. It includes free installation and extension configuration. We are always ready to give an advice or fix some technical issue, even if it does not relate to our extension;
We also recommend switching to our FPC if you use Magento Enterprise because our extension works faster and have more useful features than the FPC module included in Magento Enterprise.
By the way, we offer 30% discount to all merchants who are currently using another paid FPC solution on their website.
Review from our customer: "The fastest Full Page Cache extension for Magento I've ever used. In the past, I used Varnish Cache in Magento, but there is no need for it now. The speed is very similar comparing to Varnish and Potato FPC. I have the A grade in speedtestpage.org for First Byte. Google Insights don't show any speed warnings either so I'm happy with it. My tests show Potato FPC is 75% faster than LestiFPC and 20% faster than Mirasvit FPC. The extension code looks very clean and module settings are limited. Perhaps this is the key to the success. I strongly recommend using the Potato compressor as well."
Features of Full Page Cache extension for Magento
Speed up your website
Reduce TTFB (time to first byte) and therefore significantly decrease a time needed to prepare a requested web page.
Full Page Cache Crawler
Cache can be cleared or expired. To keep cache always warmed you need to have an automatic crawler which emulates visiting each cacheable page of your website and, therefore, generates cached content for real customers. Full Page Cache extension has a built-in Cache Crawler, so that you don’t need to purchase Cache Crawler separately. Our crawler is definitely off the charts because our cache warmer extension has CPU overload prevention and crawling priority features. Thus, your top pages will be cached first if cache flushed or expired.
Decrease server load
Returning cached version of a webpage is an easier operation for web-server than generating an entire web-page. Full Page Cache reduces server load when it's live. In its turn, it generates more revenue due to bounce rate decreasing.
Easily exclude any block/page from caching
Sometimes you need to exclude some none-native block from caching. The extension API allows making compatibility with any 3rd-party extension easily.
Statistics: Per page, cache hit&miss
Cache status and hit/miss statistics will let you know if FPC is working properly. Moreover, the extension have indicators which display the current CPU and cache warm-up conditions.
Do you want more historical statistics for CPU and RAM load? Check this - Performance Monitoring extension.
Usually, some content is common but may differ a little. With our FPC extension you can split cache by for customer group, currency, http/https, desktop/mobile, store views and even specified user-agents.
Free and lifetime technical support
Unlike other developers of Magento extensions, we offer you a guarantee that you will not stay with compatibility issues on your own. We will help you for free at any time.
We've been developing Magento extensions since 2010. And we are fans of clean and effective code. Our huge experience and positive customer feedback allows us to claim that our extensions are of very good quality.
Performance Bundle Promotion
Add 2+ products for Magento / Magento 2 performance optimization and get 15% OFF. Learn more.
Best with Compressor
- How quick my website will be after installation of your Full Page Cache extension?
- How does the FPC Crawler work? How can I make pages cached?
- Do you offer a trial period?
- Do you offer support and installation?
- Is it compatible with Redis and your JS/CSS Compressor extension?
- How to exclude certain block from caching (hole-punching feature)?
- Do I need to flush cache every time I save a product?
- 21 Reviews
Awesome productWe looked at many FPC plugins and finally found Potato FPC, which is work very correctly, fast and reliable.
Crawler works perfect. Many options to balance server load and prioritize the warmer work.
Very quick support from the team.
Finally strongly recommend this plugin.
Excellent serviceI've tested quite a few FPC extensions, this one is the one that best fitted our needs.
Customer service and post sale assistance /support is absolutely at top.
Thank you guys, I'll definitely buy from you again
The best robust solutionI am using it on a large catalog site and performs excellently.
5 stars support. Good comprehent responses. Helped me to set it up and tune it.
Very powerful and simple to use it. Well done potatocommerce. Thank you
Great Extension! Great Support!I got this extension almost 4 months ago. I installed it myself and it worked fine with no need to contact their support.
Recently I noticed a little problem on the backend cache hit/miss statistics graphic. The suppor quickly fixed the problem and even took the time to explain what the problem was and what they did to fix it.
I am very impressed with the quality, attention and speed of their support to solve my problem!
I highly recommend the company and their product!
Excellent Extenstion which Makes My Website Much Faster!I bought this extension alongside with PotatoCommerce JS & CSS Compressor.
...and it was one of the best moves I did for my webshop. It loads much faster now! Here's why:
Firstly, awesome support, I highly recommend them! They have short response time and professional staff.
Secondly, they installed the extension and did some tests, so that everything works like a charm.
Thirdly, their technical staff helped me solve some other issues I had on my server (unrelated to their extension!).
All in all I gave them only 5 stars because there's no option to give them 10.
Magento CE 1.5.*, 1.6.*, 1.7.*, 1.8.*, 220.127.116.11 - 18.104.22.168, 1.9.3* Magento EE 1.11.*, 1.12.*, 1.13.*, 22.214.171.124 - 126.96.36.199, 1.14.3.* Compatible Browsers Chrome, Safari, Firefox, Opera, IE8+
- We recommend you to backup your store before installation
- Go to magento admin and disable compilation (Systems > Tools > Compilation > 'Disable' button) and flush store cache (System > Cache Management > 'Flush Magento Cache' button)
- Download the extension package from your account and extract the downloaded archive.
- Copy the content of extracted folder to your store's root directory
- Flush store cache again
- Log out from the backend and log in again.
- If you want to use Cron for cache warming, then you need to make sure that cron is set up.
- install new cron job:
*/5 * * * * /website path/shell/potato/warmer.sh
- Set permission 755 on files:
/website path/shell/potato/warmer.sh /website path/shell/potato/warmer.php /website path/shell/potato/queue.php
- If you want to enable compilation, then you should run compilation process (Systems > Tools > Compilation > 'Run Compilation Process' button).
- Go to System > Cache Management and enable 'Potatocommerce Page Cache'.
- Flush store cache again
Update Full Page Cache to the latest version
- Go to "My account" > "My Downloadable Links" and download the latest release of Full Page Cache extension
- Disable Compilation (System > Tools > Compilation > Disable);
- Unzip the package and copy extension files (overwrite old files);
- Flush cache;
- How can I make all pages cached?
- After installing "Full Page Cache" extension my store gives error or a blank page.
- There is a block at my website that does not update correctly. How can I fix it? How to exclude block from caching?
- How to calculate the time required to warm cache for all pages?
- How to speed up cache warming (crawling)?
- Where can I check log of Cache Crawler?
- How to uninstall the Full Page Cache extension?
Path to FPC settings: System > Configuration > Full Page Cache
Max. Cache Size (Mb) – This option specifies the maximum cache size. 500Mb is usually enough for an average website (up to 20k products). The more the value, the more pages can be cached.
Use Mobile Detect – If enabled, then cache will be separated for mobile and desktop devices. Our extension uses MobileDetect library to detect mobile devices. Enabling this option is needed if you use a different theme for mobile devices. If your theme is responsive, then enabling this feature is not required. Please note, that enabling this option will double cache size.
Separate Phone/Tablet Devices – If enabled, then mobile cache will be separated on mobile & tablet cache. Please note, that enabling this option will increase cache size.
Flush Cache Automatically When – defines the conditions when cache is deleted automatically because of irrelevance.
Cronjob for clear cache by catalog rule – flushes cache for those pages and categories for which catalog rules have been expired.
Enable Page Cache Debug – This option enables a block on storefront that displays TTFB each time you refresh a page:
Ip Address(es) (comma separated) – Specify IP Address(es) here to display this block only for particular visitors.
Block name hints – Display name of blocks on the storefront.
The path to full page cache management is System > Cache Management. This page contains a detailed information about cache state and its size. Cache is grouped by store-view, customer group and currency, http/https and desktop/mobile.
You can also flush cache by some tag at this page.
You can also track Cache Crawler performance using "cache hit/miss" statistics. Red blocks show number of views with Cache Miss. Blue blocks show number of views with Cache Hit.
Cache Crawler Settings
Path to Cache Crawler settings: System > Configuration > Crawler
Enabled – Enable/disable Cache Crawler.
Acceptable CPU Load, % – To prevent high CPU load, the crawling process will be paused if CPU load is greater than this value..
Store Priority – This option is used to specify priorities of crawling for Magento stores.
Run Crawler For Page Type(s) – This option is used to specify priorities of crawling for group of pages.
Run Crawler For Currency(ies) – This option is used to specify priorities of crawling for currencies.
Run Crawler For Customer Group(s) – You can unselect some customer groups at this option if there is no need to cache pages for some customer groups (unused, system, etc.). It will decrease total cache size and the crawling time.
Run Crawler For Protocol(s) – Select all if you want to cache HTTPS pages (not recommended).
User Agents Used for Crawling Pages – The user agent which warm your cache. You can play with this option to warm mobile cache only, for example.
Source of Page URLs – Use database or sitemap as a source to retrieve URLs for the Crawler..
Use Only Short Product URLs – "No" means that both short and long product URLs will be used by the crawler.
Enable Crawler Logging – Enabling this option will create “var/log/po_crawler.log” file with detailed information about the process. This file contains visited URLs and request parameters.
Add To Queue – Once the button clicked, all pages will be added to the queue for Cache Crawler. It also flushes FPC and media cache.
Full Page Cache extension workflow
- A customer requests a page.
- Magento loads basic configuration and checks if there is a cache for the requested page.
- If the requested page has already been cached, then Magento return cached version of the page.
- If the requested page has not been cached yet, then:
* Magento loads configuration of installed modules and prepares content of the requested page.
* The prepared page is being cached
* The page is being returned to the customer.
1.6.1 Released on 10 January 2018
Full Page Cache - bug fixes
Cache Crawler v 1.0.1 - bug fixes
1.6.0 Released on 24 October 2017
* Bug fixes
Crawler is now a standalone module (included in FPC)
1.5.6 Released on 09 August 2017
* Bug fixes
1.5.5 Released on 02 August 2017
* Bug fix
1.5.4 Released on 31 July 2017
+ Link to FPC API guide added
+ Cron expression configuration added to the extension settings
+ Menu structure improved
1.5.3 Released on 31 July 2017
* Bug fix
1.5.2 Released on 27 June 2017
* Bug fix
1.5.1 Released on 26 June 2017
* Bug fix
1.5.0 Released on 02 May 2017
+ Possibility to use not just the database retrieve URLs for Crawler, but also sitemap.xml.
* Bug fixes
1.4.3 Released on 17 April 2017
* Bug fixes - HIT / MISS incorrect calculation from version 1.4.2
1.4.2 Released on 11 April 2017
* Bug Fixes
1.4.1 Released on 4 April 2017
* Bug Fixes
1.4.0 Released on 1 March 2017
+ Crawler logic improvement
* Bug Fix
1.3.4 Released on 14 December 2016
* Bug Fix
1.3.3 Released on 3 December 2016
* Bug Fix
1.3.2 Released on 02 November 2016
* Bug Fix
1.3.2 Released on 17 October 2016
* Bug Fix
1.3.0 Released on 15 October 2016
+ New option "Block Name Hints"
+ New option "Cache Auto-Refresh By Events"
* Bug Fixes
1.2.0 Released on 06 October 2016
+ Now crawler start warm cache from most popular pages
+ You can view page views statistics and its cache status
+ You can view cache hit/miss statistics
+ New options for managing crawler
+ Update cached block content without ajax
+ Stability and performance improvements
* Removed crawler daemon
* Bug fixes
1.1.0 Released on 22 April 2016
* Fixed an issue with caching AJAX requests
* Fixed an issue with caching HTTPs pages
* Fixed an issue with AJAX headers
+ Module performance improved
+ Cache management improved (search, flush)
+ Added an interface to flush cache by tag
+ Added “currency” tag to page cache
+ Added desktop/mobile device detection
+ Crawler logic improved. Added an ability to run crawler in daemon mode.
+ Crawler can cache pages for each customer group
+ Fixed an issue with Redis compatibility
+ Added an ability to see cache state and size for each store
+ Added support of widgets as a part of dynamic content
+ Added an ability to use API at app/code/community/Potato/FullPageCache/etc/custom.xml file
1.0.4 Released on 26 November 2015
1.0.3 Released on 03 June 2015
1.0.2 Released on 02 June 2015
1.0.1 Released on 29 March 2015
1.0.1 Released on 25 March 2015
- We Recommend