Faster loading via Cloudflare
Qubix serves your domains through Cloudflare — a global network of servers — and sets everything up itself. Caching is on by default, so pages load several times faster for visitors while load on your server is tens of times lower. All of it is free: Cloudflare charges nothing for its network or caching, and Qubix handles the setup.
What Qubix configures automatically
When a domain is served through Cloudflare, on connection Qubix itself:
- creates the zone, DNS records and SSL (Full mode, forced HTTPS, TLS 1.2);
- routes the domain's traffic through the Cloudflare network to your server.
You don't have to do anything for this — the domain works behind Cloudflare right away.
Why Cloudflare beats a direct connection
A domain can be connected to Qubix directly, but serving it through Cloudflare wins on every count:
- Faster for the visitor — site files are served from the Cloudflare server nearest to them (see caching below).
- Less load on your server — the Cloudflare network takes the bulk of requests.
- Your server's address is hidden — the visitor connects to Cloudflare, not to your server directly. Your real server IP isn't exposed, making it harder to find and attack.
- Cloudflare takes the hit — traffic spikes and attacks are absorbed on its network and simply never reach your server.
A direct connection leaves the load on your server and exposes its address. That's why serving through Cloudflare is the preferred mode for production domains.
Faster loading — on by default
Faster loading works by default for all your domains behind Cloudflare — Qubix turns it on itself. You can manage it under Settings → Cloudflare, the Faster site loading block, switch Speed up loading via Cloudflare — for example, to turn it off temporarily.
What it gives you:
- Much faster for the visitor — page files are served from the Cloudflare server nearest the person, not from your server on the other side of the world. Landings and sites open almost instantly worldwide.
- Tens of times less load on your server — each page pulls dozens of static files (scripts, styles, icons, screenshots), and Cloudflare serves them from its servers. The server handles only the dynamic part — on the same hardware you serve tens of times more visitors.
- Free — both caching and fast delivery across the Cloudflare network cost nothing.
What is cached, and what isn't
Only files that don't change are cached: scripts, styles, images, icons and site screenshots. They're safe to keep on Cloudflare's servers for any length of time.
The dynamic part always stays fresh and runs on your server: the cloaking decision and the landing itself are served per visitor and aren't cached. So the speed-up never interferes with cloaking or tracking.
What you need
Faster loading applies automatically once Cloudflare is set up. The only requirement is a Cloudflare API token with cache-management permissions (Qubix uses this token to apply the rule to your zones):
- Under Settings → Cloudflare, save your Cloudflare API token (create it in Cloudflare Dashboard → My Profile → API Tokens) with the permissions Zone.Cache Rules:Edit, Account.Account Rulesets:Edit, Account.Account Filter Lists:Edit.
- Done — Qubix applies caching to all your domains, and your sites' files start being served from Cloudflare servers near your visitors. You can turn it off anytime with the Speed up loading via Cloudflare switch.