You click "Edit with Elementor" and get the spinning logo forever, a grey panel on the left with nothing on the right, or the message "The preview could not be loaded". The public site still works; only the editor won't open. Elementor loads the whole editor in your browser through a few background requests to your own site, so when one of them is cut short (not enough memory, another plugin, a speed setting, the host's firewall) the editor just waits. Two checks tell you which one it is. Below is a rebuilt example (not a real client), the two checks, and the fix for each cause.
In the dashboard go to Elementor > Tools, set Safe Mode to Enable and save, then open the page in Elementor again. Safe Mode loads the editor with only Elementor and a plain theme, without touching what visitors see.
Turn Safe Mode off again when you are done.
On a computer, open the stuck editor, press F12 (or right-click and choose Inspect), open the Network tab and reload. Type admin-ajax in the filter box and look at the Status column of the rows that appear. Then do the same with the Console tab and read the first red line.
| What you see | Cause | Fix |
|---|---|---|
admin-ajax.php status 500, or "Allowed memory size exhausted" in the error log | The editor ran out of PHP memory | Elementor needs at least 256 MB (Elementor > System Info shows your current limit). Add define('WP_MEMORY_LIMIT', '256M'); to wp-config.php above the line that says "That's all, stop editing". If System Info still shows less, the host's own cap is lower: ask them to raise it, it is a setting on their side. More in "Allowed memory size exhausted" |
Status 403 on admin-ajax.php, or a page from your host or Cloudflare saying the request was blocked | A firewall rule (often ModSecurity, Wordfence or Cloudflare's WAF) took the editor's save-and-load request for an attack | Ask the host to check the firewall log for your IP at that minute and allow that rule for /wp-admin/admin-ajax.php; in Wordfence, use "Allowlist" on the blocked request under Firewall. Do not switch the whole firewall off |
| Editor opens in Safe Mode, hangs without it | A plugin or the theme loads a script that breaks the editor | Deactivate plugins in halves (keep Elementor and Elementor Pro on) until the editor opens; the last half you switched off holds the culprit. Speed and optimisation plugins are the usual suspects, then add-on packs for Elementor that are older than your Elementor version. Update or replace the one you find. Step by step: a plugin update broke something |
Console shows errors in files with names like rocket-loader, autoptimize or wp-rocket | A speed setting combines or delays scripts, including the editor's own | Turn off Cloudflare's Rocket Loader (Speed > Optimization), and exclude the editor from JavaScript delay and combine in your speed plugin; most have an option to skip logged-in users or the elementor scripts |
| "The preview could not be loaded", and the Network tab shows the preview page as 404 or redirected | The address WordPress uses for itself does not match the one you are on (http vs https, www vs not), or the permalink rules are stale | Under Settings > General, make both addresses identical to the one in your browser bar, including https and www. Then open Settings > Permalinks and press Save without changing anything; that rewrites the rules. See also too many redirects |
| Nothing red anywhere, but it only fails in your usual browser | A browser extension (ad blockers and script blockers most often) stops the editor's files | Open the editor in a private window. If it works there, turn your extensions off one by one |
| Editor opens but the page looks unstyled or old | Elementor's generated style files are stale | Elementor > Tools > Regenerate Files & Data, then clear any cache plugin and your host's cache. More in changes not showing on the live site |
Open two or three different pages in Elementor, change a word, press Update and reload the public page to see it. Then check Elementor > System Info once more: the memory line and the PHP version (8.1 or newer is the safe range today) should no longer be flagged. If you changed a firewall or speed setting, open the public site on your phone too, to be sure visitors still get the fast version.
Most of these take ten minutes once you know which one it is. If you would rather someone else finds and fixes it, that is what the box below is for. Related: a plugin update broke something, "Allowed memory size exhausted" and changes not showing on the live site.