Caching

We’ve spent a lot of time making Blokks as fast as possible and keeping load times to a minimum. We’re optimizing and lazy loading images, using non-blocking minified scripts, swapping web-fonts, gzipping text files and serving assets using a CDN.

Next to this, Blokks also depends heavily on browser- and server caching to improve performance.

Browser caching

The browser cache is a temporary storage on your computer for files the browser has downloaded. The browser is smart enough to only download updated files, or files that have not been stored in the cache yet.

Blokks uses browser caching to loading static files like CSS, JavaScript, fonts and images. These assets are cached forever, only invalidating the cache when a file actually changes. This basically means that assets are only loaded once.

Note: you can bypass browser caching by force reloading the page. Depending on your browser, you can do this by pressing CMD + R / CTRL + R or CMD + F5 / CTRL + F5.

Server caching

Blokks uses server caching to reduce bandwidth, server load, database connections and most importantly, latency. All of this makes sure that our servers respond faster to HTTP requests and stay online even during peak usage, like during the days of your event.

Blokks flushes its server cache every 15 minutes. Because of this, it may take some minutes for your saved changes to become visible.

This can be annoying when you are testing your schedule. To avoid this, you can bypass server caching by appending ?preview=true to your website url.