Elementor stuck loading? How to fix the loading screen problem in 9 steps

You click “Edit with Elementor” – and then nothing happens. The Elementor logo spins, the widget panel stays empty, and after a few minutes you give up in frustration. The problem is very common and almost always fixable. In this guide, you’ll work through the causes one by one: from the two-minute check to server settings.

Important up front: this is about the editor not loading. If instead your finished website is slow for visitors, our article Elementor slow? 7 causes and fixes will help.

Typical symptoms: how to recognize the problem

• The loading screen spins endlessly – Elementor takes forever to load.
• The widget panel on the left stays gray or empty.
• The message “The preview could not be loaded” appears.
• After clicking “Edit”, you get a white screen or a “500 Internal Server Error”.

Quick check: 2 minutes before you dig deeper

1. Open the editor in a private browser window.
2. Check whether Elementor, WordPress and PHP are up to date (Elementor → System Info).
3. Test whether all pages are affected or just a single one.
4. Think about whether you recently installed or updated a plugin.

These four answers alone narrow down the cause a lot. Then work through the following steps – they’re ordered so that the most common and simplest fixes come first.

Step 1: Rule out browser extensions and cache

Ad blockers, password managers, translation or privacy extensions interfere with pages – and the Elementor editor is a complex JavaScript application that’s sensitive to that. In a private window, extensions are usually disabled. If the editor loads there, turn off your extensions one by one until you find the culprit. Also clear your browser cache.

Step 2: The browser console reveals the cause

Press F12 (Mac: Cmd + Option + I), open the “Console” and “Network” tabs and reload the editor. Look out for red entries:

• 500 Internal Server Error (often on admin-ajax.php): a PHP error occurred on the server – usually a lack of memory (→ step 5).
• 403 Forbidden: a firewall or security plugin is blocking the request (→ step 7).
• JavaScript error with a plugin path, e.g. /wp-content/plugins/xyz/: this plugin is your prime suspect (→ step 4).
• Mixed content or blocked content: there’s an http/https problem (→ step 8).

Pro tip: PHP errors don’t show up in the console. To see them, add the following to wp-config.php and then check wp-content/debug.log:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

Remove these lines again once you’ve found the error.

Step 3: Start Elementor in Safe Mode

Under Elementor → Tools → General, enable Safe Mode. Elementor often offers it directly on the stuck loading screen after a few seconds, too. In Safe Mode, the editor loads without other plugins and with a default theme – only for you in the editor, visitors won’t notice anything.

• Editor loads in Safe Mode: a plugin or your theme is to blame → continue with step 4.
• Editor doesn’t load in Safe Mode either: the cause lies with the server, the configuration or the hosting → continue with steps 5 to 8.

Disable Safe Mode again after testing.

Step 4: Find plugin conflicts with the half-split method

Ideally, do this on a staging copy of your website. Deactivate all plugins except Elementor (and Elementor Pro). If the editor loads, reactivate half of the plugins. If it no longer loads now, the culprit is in that half – which you then split in half again. With 20 plugins, you’ll find the troublemaker in no more than five rounds.

Common suspects are:

• Optimization plugins that combine, delay or minify JavaScript
• Security plugins with strict rules
• Outdated Elementor add-ons and widget packs
• Plugins that load their own jQuery version

Test the theme too: temporarily switch to “Hello Elementor”. If your website has piled up lots of plugins over the years, a thorough review is worth it – our checklist: which plugins do you really need? will help.

Step 5: Increase the PHP memory limit

The Elementor editor needs a lot of memory, especially for long pages, with Elementor Pro and several add-ons. Elementor recommends at least 256 MB; in practice, 512 MB is a good value for the editor. You’ll find your current limit under Elementor → System Info in the “Memory Limit” entry.

In wp-config.php, you increase it with:

define( 'WP_MEMORY_LIMIT', '512M' );

This only works if the server allows it – the hosting’s PHP limit is the upper bound. Our guide How to increase the Elementor memory limit shows how to check and adjust both. While you’re at it, also check the maximum execution time (max_execution_time): below 60 seconds, the server tends to cut off large editor requests.

Step 6: Check caching, minify and CDN

Performance plugins are worth their weight in gold for visitors, but they interfere with the editor if they also apply to logged-in users. Check in your caching plugin that:

• Caching for logged-in users is turned off.
• JavaScript options like “Combine”, “Delay” or “Defer” are turned off for testing.
• On Cloudflare, Rocket Loader is disabled – it’s one of the most common reasons for a stuck editor.

Then clear all caches (plugin, server, CDN) and click “Regenerate Files & Data” under Elementor → Tools.

Step 7: Firewall or security plugin is blocking Elementor

When loading and saving, Elementor sends large data packets to admin-ajax.php and the REST API. To a strict firewall (e.g. ModSecurity rules or a security plugin), this sometimes looks like an attack – the request is blocked with a 403. Check your security plugin’s logs and whitelist the blocking rule. If the firewall is on the hosting side, your provider has to take care of it. At Servflix, our support team will check the server logs for you.

Step 8: Check the site address and HTTPS

Under Settings → General, “WordPress Address (URL)” and “Site Address (URL)” must match exactly – both with https:// and either both with or both without www. If they don’t match, the browser blocks the editor’s preview window. After switching to SSL, the Elementor → Tools → Replace URL tool helps you fix old http addresses in your content.

Step 9: Let Elementor rebuild itself

If nothing so far has helped, reset Elementor itself:

1. Run Elementor → Tools → “Regenerate Files & Data”.
2. If available in your version: under Elementor → Settings → Advanced, enable the “Switch Editor Loader Method” option.
3. Update Elementor (and Pro) to the latest version or reinstall it – your content will be preserved.

Overview: symptom, cause, solution

Symptom	Likely cause	Solution
Endless loading screen, console shows 500	Not enough memory or PHP error	Increase memory limit, check debug.log
Endless loading screen, console shows 403	Firewall or security plugin	Whitelist the rule, contact your web host
Widget panel stays gray	JavaScript conflict with a plugin or add-on	Safe Mode, half-split method
“The preview could not be loaded”	Addresses or HTTPS don’t match	Align the site addresses
Only one page affected	Very long page or broken widget	Load an older revision, split the page
Problem since an update	Incompatible plugin version	Roll back the update or wait for a fix

How to keep the editor from hanging again

• Test updates on a staging copy first.
• Use as few Elementor add-ons as possible.
• 512 MB of PHP memory and a current PHP version (8.2 or newer).
• Exclude logged-in users from caching and JavaScript optimization.
• Daily backups so you can roll back at any time.

Frequently asked questions

Why does Elementor fail to load on just one specific page?

Usually the page is very long, contains a broken widget or content from another page builder. Load an older version via the WordPress revisions or split the page up. The debug.log often shows you which widget is causing the error.

What is Elementor Safe Mode?

In Safe Mode, Elementor loads the editor without other plugins and with a default theme. This lets you quickly see whether a plugin or the theme is causing the error. Visitors to your website won’t notice a thing.

Can my hosting be to blame if Elementor takes forever to load?

Yes. Too little PHP memory, too short an execution time, overly strict firewall rules or overloaded servers are common causes. If the editor doesn’t load in Safe Mode either, the error is very likely on the server side.

Will I lose content if I deactivate plugins?

No. Your pages and plugin settings stay stored in the database as long as you only deactivate plugins and don’t delete them. Once you reactivate them, everything is back. Still, a backup before testing never hurts.

Conclusion: systematic instead of trial and error

A stuck Elementor editor almost always comes down to one of four causes: the browser, a plugin conflict, too few server resources or a blocking firewall. With the console and Safe Mode, you can narrow it down in just a few minutes. If you no longer want to deal with memory limits and server configuration: our Elementor hosting is tailored specifically to the page builder – with 1 GB of RAM, daily backups and support that knows Elementor inside out.