WordPress problem fix
Eight different problems all show the same spinner. We test them in the order most likely to fix it fastest so you are not flying blind.
If the Elementor editor opens to a spinning loader and never actually loads the canvas, the cause is almost always one of eight things: a JavaScript conflict from another plugin, a memory limit too low for Elementor to render, a permissions issue on wp-content/uploads/elementor/, a mismatch between Elementor and Elementor Pro versions, a server-level mod_security rule blocking the editor's admin-ajax request, a corrupted Elementor cache, a theme that hard-loads jQuery in noConflict mode, or a CDN/security plugin (Cloudflare, Wordfence) that is rate-limiting admin-ajax. The fix is to test them in order of frequency, not in order of where the WordPress docs put them. Most stuck-editor cases resolve at step 2 or 3 once you stop guessing.
If any of these match, you are on the right page.
Clicking 'Edit with Elementor' opens a page with a centered spinning loader
The loader never resolves — you can wait 10 minutes and nothing changes
Browser console shows admin-ajax.php returning 500, 403, or 504
The front-end of the page renders fine; only the editor is broken
It worked yesterday and broke after a plugin or Elementor update
Elementor's editor is a single-page React app that talks to WordPress over admin-ajax with about a dozen rapid requests. Any plugin, theme, server rule, or CDN that interferes with admin-ajax, jQuery, or React's expected response shape can stall the loader. The architecture is fragile by design — high power, high surface area for conflicts.
The front-end uses cached HTML and a small amount of JS. The editor needs admin-ajax, the REST API, full jQuery, the Elementor data layer, and write access to uploads/elementor/. Almost everything that can break for editor-only reasons does not touch the front-end.
Elementor and Elementor Pro share a private data contract. If Pro updates and Free does not, or vice versa, the editor's first admin-ajax call asks for fields the other side does not know about and returns malformed JSON. The React app hangs because it cannot parse the response.
The real method, in the order it works.
Open the browser DevTools console BEFORE clicking 'Edit with Elementor'. Reproduce the load. Read the network tab. The failing admin-ajax response code (500, 403, 504) tells you which category of cause you are in.
Bump PHP memory limit to 512M in wp-config.php (define('WP_MEMORY_LIMIT','512M'); define('WP_MAX_MEMORY_LIMIT','512M');). Roughly 30% of stuck-editor cases are memory-only.
Confirm Elementor and Elementor Pro are on matching compatible versions. The plugin admin page shows a version-mismatch warning when they drift. Update both to the latest stable in the same maintenance window.
Regenerate Elementor's CSS cache: Elementor → Tools → Regenerate Files & Data. If the editor will not load far enough to reach Tools, run wp elementor flush-css over WP-CLI.
Disable every non-Elementor plugin (Plugins → bulk select → Deactivate). Try the editor. If it loads, reactivate plugins one at a time, retesting after each, until the editor breaks. That plugin is the conflict.
Switch to a default theme (Twenty Twenty-Four). Retest. If the editor now loads, the theme is loading jQuery in a conflicting mode or registering scripts on admin pages that should not run there.
Check server / hosting layer: pause Cloudflare on the admin path (Page Rule: bypass cache + bypass security on /wp-admin/*), temporarily disable Wordfence's brute-force protection on admin-ajax, ask the host to whitelist your IP against any mod_security rules triggered by /wp-admin/admin-ajax.php.
Confirm permissions: wp-content/uploads/elementor/ should be 0755 with the web user as owner. A 403 on admin-ajax for the editor often traces back to this.
Real fix, from our work
An e-commerce client on UK shared hosting reported the Elementor editor had been broken for three weeks. Their previous freelancer had bumped PHP memory to 1G, rolled Elementor back two versions, and tried four different themes — none of it worked. The browser console showed admin-ajax.php returning 403 Forbidden. That ruled out memory, version, and theme. It was the host's mod_security rule blocking POST requests larger than 64KB to admin paths — Elementor's first editor request was 71KB. We asked the host to whitelist mod_security on /wp-admin/admin-ajax.php for the client's admin IP. The editor opened in 9 seconds, first try. Total fix time: 22 minutes once we looked at the network tab instead of guessing.
Written by Ali Yasin Jatoi
Founder of WebCare Studios. Ali has worked with WordPress for more than 10 years, including managing a fleet of 150+ sites with WP-CLI automation for updates, security cleanup, and malware removal. He has hands on experience across major hosts including Cloudways, A2 Hosting, Hostinger, and Bluehost.
Site down, hacked, or broken checkout gets a senior engineer within 4 hours. No ticket queues, no bots.
Flat quote up front. If we cannot get you back online, you do not pay. Risk sits with us, not you.
We work on a snapshot first and never touch your live database until the fix is verified safe.
We run a fleet of WordPress sites every day. The errors you are seeing are ones we have closed hundreds of times.
Almost never. A reinstall does not clear the actual cause (memory, plugin conflict, server rule, CDN rule). It also nukes your Elementor templates folder if done wrong. Diagnose first, reinstall as a last resort.
Either PHP max_execution_time is too low (raise to 300), or the upstream PHP-FPM worker is overloaded, or a server-level proxy timeout (NGINX proxy_read_timeout) is shorter than Elementor's longest request. All three are host-side fixes.
Elementor Cloud usually fixes memory and mod_security issues automatically, so the remaining causes there are version mismatch (rare on Cloud), plugin conflict, and theme conflict. Steps 3, 5, and 6 above are the relevant ones.
Yes. Cloudflare's Bot Fight Mode and Super Bot Fight Mode regularly flag editor admin-ajax traffic as automated. The fix is a Page Rule that bypasses bot management on /wp-admin/*. We see this on at least one client site per month.
Yes. Plugin → Roll back to previous stable. But roll back Pro to the same version as Free in the same step, or you create the very version mismatch that is one of the eight causes.
Two fields. Email and your URL. A senior WordPress engineer reads it within minutes and replies on email and WhatsApp with what is wrong and what we will do next.
Real proof and field guides tied to "Elementor editor stuck on spinning loader".