How does the Caching work?

At Seravo the server caching layer has been built with great diligence to ensure that our clients websites run as fast as possible. This kind of caching orientation is not something many generic hosting-providers provide to their clients and at Seravo we strive to be above average. For example we offer an easy to enable advanced caching solution for our clients.

More information about caching in our blog.


The idea of caching is simple, information is saved into a caching layer so that the next time the same information is requested it can be served from cache instead of loading it all again from the server. There are many different kind of caches but with websites the cache in question is usually the HTTP-cache

The changes made to the website don't always update instantly to the browser because of the browsers own caching layer. Often developers need to see their changes instantly, however, so the page must be refreshed without using the browsers cache. This can be done using the command ctrl+F5 (or when using Apple products shift-cmd-R/cmd-option-R)


Different cache layers renew themselves automatically so that the site visitors don't have to empty their own browser cache every time a change has been made to the site. At Seravo the server side cache is renewed in a 15 minute cycle, but the cache can also be emptied manually by running the command wp-purge-cache via SSH on the server. Cache can also be purged using the "Purge cache" button on the WordPress admin panel.


How the website handles cache depends on the choices made by the site developer. For example it is possible to build the site so that when loading specific content the site tells the browser to not use cache and as result the requested content is loaded completely from the server instead of cache.


Further information about caching:

- https://en.wikipedia.org/wiki/Web_cache

- https://cachingexplained.com

- https://www.refreshyourcache.com

- General info about caching: https://en.wikipedia.org/wiki/Cache_(computing)

Did this solve your problem?