Ever wonder how to make your website load faster and perform better?

There are a plenty of methods to improve your website load time. Optimizing the images or removing the unnecessary fonts and elements could bring some improvements, but hey, website caching will do the job! When a request comes to your website, your backend requires time to process the request and return an HTML. But if your website is cached server-side, backend is not getting involved in serving the request anymore.

Good news is that SpringBuilder has brought up its caching mechanism, which means you don’t need to worry about all these caching related technical stuff anymore, yet grip such advantages like better pagespeed and web performance, exceeding network traffic, etc.

Our caching mechanism is temporary storing your pages’ HTML server-side and serves directly to your visitors in almost no time.

If the caching mechanism is enabled on your website, the system will cache your public pages until the next change has been applied.

How to turn caching on?

It takes one step to turn on caching on your SpringBuilder website: head over to your Dashboard > Site Settings, and switch on the Site Caching option.

In order to avoid outdated content, we also brought the ‘Clear Cache’ button to your Edit modes. Head over to your Left Panel > Publish app and you will notice the list of all the domains currently attached to your SpringBuilder website with a small ‘Clear Cache’ spinning icon. Once clicked, the system will clear your website cache on our servers (both Desktop and Mobile views) and will wait until the next public request to your website in order to re-cache the pages again.

Important! Do not clear cache before publishing! Make sure to hit Publish, then Clear cache of your website.

Please note, that all content types that require separate publishing, like Articles are not being cached on our servers to ensure we are serving the right content.

Please also note, that caching does NOT apply to your websites with BetConstruct subdomains and only works with your Custom Domain.

Did this answer your question?