CDN and advanced tab
Background mode, test mode, debug log, Divi Visual Builder guard and conflict fix, CDN URL rewriting and the environment report in TurboCache.
TurboCache → Settings → CDN and advanced.
Advanced
- Background mode (default Loopback requests) — Loopback requests (recommended): the plugin calls itself so work starts within a second, independent of visitors or WP-Cron. WP-Cron: for hosts that block loopback connections; slower, needs traffic or a real cron job.
- Test mode (default off) — optimise only for administrators; visitors get untouched pages and caching is off for them. Use it to preview changes safely.
- Debug log (default off) — write cache decisions and worker activity to the log shown on the Manage screen.
Divi
- Visual Builder guard (default on) — never optimise or cache builder sessions.
- Purge hooks (default on) — refresh the cache when layouts, the Theme Builder, presets, global colours or Divi options change. Theme Builder and library saves refresh the whole site.
- Conflicting Divi options — lists Divi → Theme Options → Performance settings that duplicate the plugin’s work (Minify And Combine JavaScript/CSS, Critical CSS, Defer jQuery And jQuery Migrate, Enqueue jQuery Compatibility Script, Defer Additional Third Party Scripts, Load jQuery In Body, and the inline Google Fonts option). Turn them off switches them off and clears Divi’s static files.
CDN
- CDN (default off) — rewrite same-origin asset URLs, including generated CSS/JS and image variants, to a pull-zone CDN such as BunnyCDN, KeyCDN or CloudFront.
- CDN address — for example
https://cdn.example.com. - File types —
css,js,img,fonts(default), plusmediaorall. - Exclude URIs — files that stay on your own domain.
- Attributes — attribute names rewritten:
src, href, srcset, data-src, data-wpca-src, data-wpca-srcset, data-wpca-bg, poster.
Cloudflare as a proxy is not a pull-zone CDN — leave this off and use the Cloudflare fields on Cache and revalidation instead.
Environment
A read-only report: cache directory and whether it is writable, drop-in status, whether WP_CACHE is true, the web server and the state of its rules, PHP version and extensions (GD, Imagick, Brotli, zlib, cURL), and the Nginx snippet path.
Did this answer the question? No — open a support request