All Collections
Design Mode
Enable Publishing and Caching for Your Website
Enable Publishing and Caching for Your Website

Publish versions of your website and explore caching

Karen Sahakyan avatar
Written by Karen Sahakyan
Updated over a week ago

Your site's success really depends on the speed and efficiency of your website load time. Therefore, it's really important that your site loads very quickly, and that's where caching comes in!

There are 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, the backend is not getting involved in serving the request anymore.

Good news 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 temporarily 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.


Site Caching

Website caching is the best way to improve your website load time. SpringBuilder has developed its caching mechanism, so you can trust us to handle the technicalities. Our caching mechanism temporarily stores your SpringBuilder pages' HTML server-side and directly serves your visitors in almost no time.

SpringBuilder automatically enables the caching mechanism on your website once you create it. Thus, the system will cache your public pages on our servers (both desktop and mobile) until the following change has been applied.

A Clear Cache Button is located in the Publishing section as well to avoid an outdated content issue. Click on the Publish Tool on your Left Panel, and you'll notice the list of all the domains currently attached to your SpringBuilder Website with a Clear Cache button next to each domain name. The system will clear your website cache on our servers (both desktop and mobile) and wait until the next public request to your website to re-cache the pages again.

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

!Note: All content types that require separate publishing, such as Articles are not being cached on our servers to ensure we are serving the right content.

You can clear the caches of all connected domains with one click.

Caching does NOT apply to your websites with BetConstruct subdomains and only works with your Custom Domain.

Site Versioning

The Site Versioning functionality is handy for those who like experimenting with different website versions and have a custom domain connected to their websites.

To enable the Versioning for your website, move to the Site Settings App, located on your Dashboard and turn on the Site Versioning in the Basic section. Once you've saved these changes, the Publish Tool will appear on the Left Panel.

At that time, the latest version of your website will be automatically published to your custom domain, and the version number will appear next to the domain name. The number will change accordingly with every published version, and the badge will become active with every change.

The changes made in the Design Mode automatically go live on your SpringBuilder subdomain, so yoursite.springbuilder.site always shows the latest version of your website. This is helpful when testing before pushing the version live. If you want to reflect the changes you have made on your Custom Domain, click the Publish Button. This action will also clear the cache from our servers and update the content and design of your site.

Related Articles


For any further questions or concerns you may have, please visit the SpringBuilder Help Center for more information. 

Did this answer your question?