Performance: Caching

Purge the cache, refresh reserved cache and Critical CSS, and set browser, static, JavaScript and cookieless cache.

What it is

Caching lets you configure how your site's files are stored and served by Tuurbo and by the visitor's browser. A good cache makes pages load faster and reduces the load on your server.

To open it: Performance, then Caching.

Maintenance actions

Each action asks for confirmation before running.

Action	What it does	Limit
Purge cache (button Purge all)	Clears cached files so Tuurbo fetches a new version from your server. Performance may drop temporarily and your server receives more requests.	None
Refresh reserved cache (button Refresh)	Fixes outdated or inconsistent content shown to different visitors.	3 times per day
Refresh Critical CSS (button Regenerate)	Regenerates the Critical CSS, useful after graphic changes to the site.	3 times per day

The counter next to each action (for example 1/3) shows how many refreshes you have used.

Step by step: refresh the Critical CSS

Critical CSS is the essential styling the browser loads first so pages appear faster. Tuurbo generates it for every page and refreshes it on its own when it detects significant design changes. After smaller changes (new graphic elements, layout tweaks, theme or plugin updates) refresh it yourself:

Open your site and go to Performance, then Caching.
In the maintenance actions, find Refresh Critical CSS.
Click Regenerate. Tuurbo deletes the old Critical CSS and generates a new version from your updated CSS files.
Wait 5 to 20 minutes for the new version to reach the CDN. The site keeps working normally in the meantime.

You can do this up to 3 times per day per site. Technical teams can also automate it with the API.

Browser Cache TTL

How long the visitor's browser keeps files. Options: Respect existing headers, 2 hours, 8 hours, 1 day, 1 week, 1 month, 1 year. Click Save to apply.

Static File Cache

Switch plus Cache duration (1 day, 1 week, 1 month, 3 months, 6 months, 12 months) for images, fonts and other static files. Default: active, 1 month.

JavaScript File Cache

Same settings, for JavaScript files. Default: active, 1 year.

Cookieless Cache

Distinguishes anonymous visitors from logged-in customers, so anonymous visitors get cached pages while carts and personal areas stay correct. Available only for PrestaShop, WooCommerce, WordPress, Magento and Magento 2.

Turn on the switch.
Choose the CMS (Universal, PrestaShop, WooCommerce, WordPress, Magento, Magento 2).
Choose the Cache duration.
Click Save settings.

Tips

Purge the cache after important changes to the site (new prices, new layout) if you do not see them online.
Use long durations for files that rarely change and shorter ones if you update the site often.

Common problems

Problem	What to check
I do not see my latest changes	Use Purge all, then reload the page.
The Refresh button is disabled	You have reached the 3 refreshes per day: try again tomorrow.
Logged-in customers see wrong content	Check that Cookieless Cache has the correct CMS selected.