Magento extension High Performance Cache with Varnish support by jonathan_made
MageCloud partnered with jonathan_made to offer High Performance Cache with Varnish support in your MageCloud panel for our simple 1-click installation option. To install this extension - create your account with MageCloud and launch a new Magento store. It takes only 3 minutes.
jonathan_made always provides support for customers who have installed High Performance Cache with Varnish support Magento module. Feel free to leave a review for the company and the extension so we can offer you better products and services in the future.
You may want to check other jonathan_made Magento extensions available at MageCloud and even get extensions from hundreds of other Magento developers using our marketplace.
Advanced Block Cache module with support for Varnish and ESI tags that enhances performance.
Compatible with Magento 1.x
High Performance Cache with Varnish support
Quick & Versatile Performance BoostFew know that Magento out of the box actually doesn't cache any frontend blocks other than Navigation and Footer, which are basically static as they are. This module enhances performance by giving developers a simple interface for caching any block they want, and comes with good default settings.
Simple Configuration
Choose what you want to cache and where, via simple layout XML changes - per layout handle. There is also support for disabling cache for specific handles such as the checkout, where you don't want to load the main content block from cache.
Varnish + ESI support (Experimental)Varnish support is built into the actual module. Caching is done on a granular level, keeping the session-dependent blocks cached on a user level until something has actually changed. This means loading times can get extremely low and that whole pages can be served directly from Varnish memory. Check layout/madecache.xml for examples.
Block Level ProfilingA separate profiler is included which gives insight into the different block renderings times, making it easier for a developer to determing which block to cache or not.
Unobtrusive & Future ProofEvents are used instead of block rewrites, and no core functionality is modified. This means that there will be no interference with other modules, and that manual block cache settings are preserved. Implementing block cache