If your Elementor editor loads to a spinning dashboard and never opens, and the site sits behind Cloudflare, the culprit is almost always Rocket Loader. Elementor and Cloudflare get along fine in general, but Rocket Loader has a long-standing habit of breaking the editor. Here is why, and the fix I have used for years.
Why Rocket Loader breaks the Elementor editor
Rocket Loader speeds up a site by making JavaScript load asynchronously. That is usually good for the front end, but the Elementor editor depends on its scripts loading in order. When Rocket Loader shuffles them, the editor locks up: it works on a staging copy without Cloudflare, then breaks the moment you go live behind the proxy. That mismatch is the giveaway.
The fix: exclude Elementor URLs from Rocket Loader
You do not need to disable Rocket Loader site-wide. You just tell Cloudflare to skip it on Elementor's editor and template URLs. In your Cloudflare dashboard, create rules that turn Rocket Loader off for these URL patterns:
- Elementor pages:
yourdomain.com/*elementor* - Elementor templates:
yourdomain.com/?elementor_library=*
The front end keeps the Rocket Loader speed boost; the editor gets left alone and works normally.
A 2026 note on Cloudflare rules
When I first wrote this, you would use Cloudflare Page Rules for this. Page Rules still work, but Cloudflare now steers you toward Configuration Rules, which do the same job with a cleaner interface: set the field to Rocket Loader, the action to Off, and match on the URI paths above. Either way, the principle is identical: exclude Elementor's URLs and the conflict disappears.
Running Elementor behind Cloudflare and hitting odd glitches? I work this stack daily. Ask me anything.