Your Divhunt site can now be served from Cloudflare's global network. Connect Cloudflare with one token, and a ready copy of every page is kept in 300+ locations around the world. Every visitor gets your site from the location closest to them, wherever they are.
The result is an even faster site for everyone, with better Core Web Vitals and PageSpeed scores, which helps both SEO and conversions.
It costs nothing
The free Cloudflare plan is all you need. It includes the CDN, caching, SSL, DDoS protection and the Cache Rules this integration uses.
How to set it up
- Add your domain to a free Cloudflare account and change the nameservers at your registrar to the ones Cloudflare gives you.
- In DNS, point A @ and A www to the Divhunt server IP with Proxied turned on (the orange cloud), and set SSL/TLS mode to Full (strict). Divhunt keeps issuing your SSL certificate when the domain is behind Cloudflare.
- In Cloudflare, go to My Profile > API Tokens and create a Custom token for your domain with three permissions: Zone Read, Cache Rules Edit and Cache Purge.
- In the Divhunt builder, open Performance > Cloudflare in the sidebar, paste the token and click Connect.
That's it. Divhunt finds the right zone in your account, creates a cache rule for every custom domain of the site (with and without www), clears the cache right away, and from then on clears it automatically after every Publish. You also get a Clear cache button for manual clearing and a Disconnect button that removes the rule and the token.
Everything keeps working
- Forms: submissions are never cached
- CMS lists, filters and search: they load live, so they are always fresh
- New posts and changes: visible right after Publish, because the cache is cleared
- Animations and interactions: they run in the browser
- Memberships: logged-in members always get the live page and never see someone else's
- Builder and preview: you always see your latest draft
Your other Cloudflare rules stay untouched. Divhunt only manages its own rule, and the token is stored securely, is never shown again and is not part of site backups or exports.
When it is not the right fit
If your site shows different content to each visitor without a login, or content changes without a Publish and has to show up immediately, the cache is not for you. Cached pages refresh after Publish, after Clear cache or after 7 days. For presentation sites, portfolios, landing pages, blogs and sites with forms, it is ideal.
More in the Performance tab
- Faster scripts: your site's JavaScript is built once per version instead of for every visitor.
- Disable GSAP: skips loading the GSAP library if your site does not use GSAP animations.
- Delay tracking scripts: Google Analytics and GTM, Facebook Pixel, Hotjar, Clarity, LinkedIn, TikTok, X and Pinterest start on the first scroll, click or tap, or after 5 seconds, so the page shows without waiting for them.
Want to check that it works? Open DevTools > Network, click the page and look for cf-cache-status: HIT in the response headers. The first visit shows MISS, every visit after that shows HIT.

