Varnish is a web app accelerator platform, which caches content for the sake of quicker access. It is occasionally referred to as an HTTP reverse proxy too and it interacts between a web server and a browser. When a site visitor accesses a given web page, its content is requested by the web browser, and then the web server handles this browser request and returns the required data. If Varnish is activated for a particular site, it will cache the pages at the very first request and in case the visitor opens a cached page again, the content will be delivered by the caching platform instead of the web server. The increased speed is an end result of the much faster response time that Varnish offers as compared with any web server software. At the same time, this does not mean that the website visitors will continue being served the very same content again and again, as any change on any of the pages is reflected in the content that the Varnish platform caches in its system memory.

Varnish in Shared Hosting

You can use Varnish’s full potential and optimize your websites’ loading speed irrespective of the shared hosting package that you have picked and you can activate and set up the content caching platform with several mouse clicks through the simple-to-work-with interface offered by our innovative Hepsia Control Panel. During the process, you’ll be able to select two different things – how many sites will employ the Varnish platform, i.e. the number of instances, and how much information will be cached, in other words – the amount of memory. The latter is offered in increments of 32 megabytes and is not bound to the number of instances, so you can use more instances with less memory and the other way around. In case you’ve got plenty of content on a specific Internet site and you get numerous visitors, more memory will guarantee you a better result. You may also consider employing a dedicated IP for the sites that will use the Varnish platform. Hepsia will provide you with simple 1-click controls for turning off or restarting any instance, for deleting the cache for each website and for checking elaborate system logs.