The MGT Varnish Cache Module works with the Varnish Cache which is an open source web application accelerator. We developed a module that enables easy control of the Cache Module for Magento 2.
With the module, the Cache Module is available at your fingertips and easy to handle. It comes with automation and updatable tags to save time and resources.
We offer a fully managed Cache Module for Magento
The highest ecommerce conversion rates occur on pages with load times between 0-2 seconds. Varnish Cache ensures that Magento page loading time is fast and offers a great user experience in online selling environments.
Blazing Fast Page Loads
The speed of the Magento shop is critical for user engagement and conversion rates. Varnish Cache provides a fast-loading site for customers to complete their purchases quickly.
Better Search Ranking
High performance is essential for SEO and increases site visibility. A fast-loading page ranks higher on search engines like Google or Bing.
Over eight years of integration experience have made us experts in the field. Our clients benefit from our know-how and professional support for any technical queries.
Improved User Experience
Fast page loading time reduces cart abandonment and improves sales. Enhance the user experience and allows customers to spend screen time on the Magento store.
How Varnish Cache Module Works
The Varnish Cache Module works in combination with Varnish Cache as web application accelerator and caching HTTP reverse proxy. It handles all inbound requests before it reaches the web server.
This speeds up the Magento Store by storing a copy of the page the first time a user visits.
Varnish Cache handles much more traffic, so the site’s performance and scalability go through the roof. It uses fewer backend server resources and boosts the delivery of content-heavy dynamic pages.
MGT Varnish Cache Module for Magento 2
MGT Varnish Cache Module is designed to optimize performance with features for cache management.
It includes single-store purges, a cache warmer, and logs that record all purges.
Cache Crawler Queue
All product changes enter the Cache Crawler Queue, and its processing is highly prioritized. The Queue is easily consulted on Cache Management
The Cache Warmer checks the CPU workload when it exceeds a defined limit. It ensures stable performance during traffic spikes.
The function allows us to select specific stores to precisely purge what is needed.
In Debug Mode, all purges are recorded in a log file and displayed with other essential development information.
MGT Varnish Cache Module Warmer Queue
MGT Varnish Cache Module Settings
MGT Varnish Cache Module vs. Magento 2 built-in Varnish
|MGT Varnish Cache Module
|Magento 2 built in Varnish
|Auto Purging After Product Save
|Multi Cache Server Compatible
|Cache Warmer Queue
|Varnish Cluster Compatible
|Works with HTTPS
|Urls can be excluded
|Routes can be excluded
|Params can be excluded
|Different Cache Lifetime for Homepage,
Category and Product and CMS Pages
|Single Url Purge
|Single Store Purge
|Purge Rest API
MGT Varnish Cache Module Pricing
The managed MGT Varnish Cache Module solution comes with the managed Magento hosting plan. The Varnish Cache Module is compatible with all Magento 1 and Magento 2 versions.
* It is the customer who must account for any VAT due (reverse-charge-regime). All prices are exclude German VAT (19%) . VAT is not charged to customers living in the EU if a valid EU VAT ID has been entered. German customers are being charged 19% VAT. Place of performance corresponding § 3a Abs. 5 UStG i.d.F. from 01.01.15 place of business in receipt of benefit (destination principle).
MGT Varnish Cache Module as Cluster
Super Fast Page Loads around the globe with Varnish Cache Nodes in different Regions.
The Varnish Cache Module Cluster consists of as many nodes in the AWS Regions as needed. It is used to achieve the highest possible performance worldwide. Our developed MGT Varnish Cache Module module for Magento controls each node.
How does it work?
Using DNS routing, the visitor is redirected to the closest Varnish Cache node to process the request. If the cached content of the page is available, it is delivered directly to the end user.
The request is redirected to the origin server if there is no cached version in the Varnish Cache node. The MGT Varnish Cache module controls all the Varnish Cache nodes easily. For example, the cache lifetime, excluded routes, etc.
Highest Performance around the Globe
To reach a global audience, the Magento shop has to be fit for the job. With the Varnish Cache Module Cluster, the shop is available at high speed in all regions.
Monitoring, Patching, and Backup
Thanks to our monitoring of all Varnish Cache nodes, it is always highly available. The Varnish Cache nodes receive regular updates to reach the highest possible security. We perform backups once every night to secure the systems. It is reachable within minutes in case of an emergency.
We deliver professional support for all Varnish Cache Module-related services. Our support is backed by over eight years of experience.
Pricing per AWS Region
2 Number of Nodes (HA)
€499.90 Setup Fee
€499.90 Monthly Fee
* It is the customer who must account for any VAT due (reverse-charge-regime). All prices are exlude German VAT (19%). VAT is not charged to customers living in the EU if a valid EU VAT ID has been entered. German customers are being charged 19% VAT. Place of performance corresponding § 3a Abs. 5 UStG i.d.F. from 01.01.15 place of business in receipt of benefit (destination principle).
Yes, it’s possible because we use NGINX in front and a reverse proxy to forward all requests to Varnish. The HTTPS is terminated at NGINX.
Yes, our solution is compatible with Multi-server and Auto Scaling architecture.
It is serving hostname or IP. Port-based virtual hosting follows IP-based hosting. The client is at port 80, and the listen port to the backend default is at port 8080.
Varnish works up to 250 times faster for Magento! Get the fastest response time with a well-configured varnish. The full-page cache stores the cache in the file system, which results in less performance.
No, because the Magento Backend has to stay uncached. The values keep updating in the backend, which is not accessible to customers. The backend is only for Admin purposes.
No, we deliver Varnish completely installed and configured.
We don’t need any varnish configuration file. It is offered as a full turnkey solution for our customers.
It is part of the varnish default.vcl. The vcl_recv subroutine is executed when Varnish receives a request from the client. The VCL logic decides whether or not the request is cacheable.
Yes. Besides that, we offer a reload option in our Panel.
The copy of the content or object stored in the cache comes with a time to live (TTL). It defines how long an object is considered fresh, or live, within the cache.
On top of the defined TTL, it allows a “grace” period, which is used to trigger the “stale while revalidate” behavior. A “keep” period is set to implement some conditional requests.
Yes, it is possible to order additional domain licenses. All further information is available on our “Pricing” page.