Turbine makes your site faster by serving visitors ready-made copies of your pages, so WordPress and your database do far less work on every visit. This guide switches it on and checks that it works.
On Phluit Managed WordPress, Turbine comes set up for you. New sites start with the page cache on (copies renewed every 10 hours), browser caching is on, and the server already compresses every page, so you can skip to Step 2. You can also switch the page cache on or off from the portal. See Turning on the page cache.
Step 1: Switch on the page cache
- In WP Admin, go to Turbine → Page cache.
- Switch on Page cache and click Save settings.
Turbine adds a small drop-in file to wp-content and turns on WP_CACHE in wp-config.php. The Status card shows each step as done. Both are removed again when you turn the page cache off or deactivate Turbine, and wp-config.php is restored exactly as it was.
If the status says "wp-content/advanced-cache.php belongs to another plugin (left untouched)", another caching plugin is still installed. Deactivate it first: use one page cache at a time.
Step 2: Check that it works
Open your site in a private browser window, where you aren't signed in, and load a page twice. The Page cache screen then counts the cached pages and their size.
Signed-in users, password-protected posts, previews, searches, feeds and form submissions are never cached, so you always see your latest changes while you're signed in.
Step 3: Clear the cache when you need to
Copies clear themselves when you publish or update content, approve comments, or change menus, widgets or the theme. To clear everything by hand, use Clear page cache in the WP Admin toolbar, on the Page cache screen, or in the post editor.
Step 4: Browser caching and compression
- Go to Turbine → Browser caching.
- Choose how long browsers may keep each type of file (CSS, scripts, images, fonts and so on), and switch on compression.
- Click Run checks to see what your server actually sends.
On Apache and LiteSpeed, Turbine writes its rules to .htaccess in its own marked blocks and never touches other blocks. On Nginx or IIS, copy the snippet shown on the screen into your server configuration, or ask your host to.
On Phluit hosting, browser caching is already on and compression shows Handled by Phluit hosting: the web server compresses every text file itself, so you can leave Turbine's compression off.
More settings
The Page cache screen also lets you:
- use a separate cache for phones,
- choose how long copies are kept, and whether to cache 404 pages or keep compressed copies,
- leave out pages, cookies or browsers that should never be cached,
- clear Cloudflare, Varnish or an Nginx cache together with the page cache,
- preload your home page and latest posts after the cache is cleared.
Good to know
- Turbine was called Phluit Brisk until November 2026. It works the same way.
- On a multisite network, the page cache is set up once for the whole network under Network Admin → Turbine, with a switch per site.
- On a site outside Phluit hosting, activate your license key first. See How do I activate my license key in WordPress?
