Varnish is a web application accelerator platform, which caches info for faster response times. It is sometimes called a caching HTTP reverse proxy as well and it works between a web server and its users. When a visitor opens a particular web page, its content is requested by the web browser, and then the server processes this request and delivers the needed info. If Varnish is enabled for a particular site, it will cache its pages on the very first request and if the user accesses a cached page again, the content will be delivered by the caching platform and not by the web server. The improved load speed is an end result of the considerably faster response time that Varnish offers as compared to any web server software. Of course, this doesn’t mean that the website visitors will keep seeing the exact same content over and over again, as any modification on any of the pages is reflected in the content that Varnish caches in its system memory.

Varnish in Shared Hosting

You can unlock Varnish’s full potential and accelerate the loading speed of your sites irrespective of the shared hosting package that you have picked and you can add and set up the data caching platform with a couple of clicks using the easy-to-use interface offered by our next-gen Hepsia Control Panel. In the meantime, you will be able to choose two separate things – how many Internet sites will use the Varnish caching platform, i.e. the number of instances, and how much information will be cached, in other words – the amount of system memory. The latter is available in increments of 32 megabytes and is not bound to the number of instances, so you can order more instances with less memory and the other way around. In case you’ve got lots of content on a specific site and you attract numerous visitors, more memory will give you better results. You may also consider employing a dedicated IP address for the Internet sites that will use the Varnish caching platform. The Hepsia Control Panel will provide you with simple 1-click buttons for removing or restarting any instance, for clearing the cache for each site and for checking in-depth logs.