Tech

Elementor Stuck on Loading? Safe Checks Before Changing Your Website

Elementor stuck on its loading screen usually means the editor’s scripts could not finish. Here are the likely causes and safe checks, in the right order.

By Harika Behara 30 Oct 2026 · 8 min read 0 views Rate it 0 comments

Short answer: When Elementor gets stuck on its loading screen, the editor has not completed its loading process. The usual causes are a plugin or theme conflict, too little PHP memory, a caching or CDN feature that delays scripts (Cloudflare Rocket Loader is a common one), or mismatched Elementor and Elementor Pro versions. Work through the checks below in order, starting with the ones that change nothing on your live site.

Step 1

Observe the failure

Step 2

Compare browser and System Info

Step 3

Isolate conflicts on staging

Last reviewed: 30 October 2026. Requirements were checked against Elementor’s System Requirements page (updated August 2026) and WordPress.org’s hosting requirements.

What you see when Elementor is stuck

You click “Edit with Elementor” and the familiar spinner or grey panel appears, but the editor never finishes opening. Sometimes the canvas loads and the left widget panel keeps spinning. Sometimes the whole screen stays blank. The front end of your website may look completely normal to visitors, which can make the problem feel mysterious.

That last detail is a useful clue. Visitors only see pages that have already been built, while the editor has to load a large set of JavaScript files, talk to WordPress through the REST API and display your page inside an embedded frame. Any one of those steps can fail on its own.

What normally happens behind the scenes

When the editor opens, your browser downloads Elementor’s scripts and your site’s PHP builds the editor’s settings. The editor then asks WordPress for data through addresses that begin with /wp-json/elementor/, and loads a live preview of the page in an iframe. If PHP runs out of memory, a plugin throws a JavaScript error, a security header blocks the iframe or a performance tool rearranges scripts, the editor waits forever for something that will never arrive.

Also readHow to Speed Up an Elementor Website Without Breaking the Design: A Practical 2026 Guide

Likely causes at a glance

Symptom	Likely cause	First check
Spinner forever on every page	Low PHP memory or a conflict	Elementor → System Info, then Safe Mode
Worked yesterday, stuck after an update	Elementor and Elementor Pro out of sync, or an add-on update	Compare version numbers
Stuck only for logged-in users behind Cloudflare	Rocket Loader or script optimisation	Pause the optimisation and retest
Stuck on one page only	A specific widget or add-on on that page	Duplicate the page and remove sections
Grey preview area, panel loads	Security headers blocking the iframe	Check the browser console

Before you change anything

Take a full backup of files and database, or confirm your host has a recent restorable copy. If your host offers a staging site, reproduce the problem there first, because some checks involve deactivating plugins. Write down the current versions of WordPress, Elementor, Elementor Pro and any Elementor add-ons, so you can tell support exactly what changed.

Do not test on a live shop or booking site during busy hours. Deactivating plugins can briefly switch off checkout, forms or payment features.

Safe checks, in a sensible order

1. Rule out the browser

Open the editor in a private window with extensions switched off, or try a different up-to-date browser. Ad blockers and privacy extensions sometimes block editor scripts. If it works in a private window, investigate extensions, cookies and cached assets before changing server settings.

2. Read Elementor’s System Info

In WordPress go to Elementor → System Info and look at the PHP version and the WordPress memory limit. Elementor’s documentation currently lists 256 MB as the minimum memory for Elementor and Elementor Pro, 512 MB as recommended and 768 MB for best performance. If your figure is lower, ask your host to raise it, or raise WP_MEMORY_LIMIT in wp-config.php within the limit your hosting plan allows.

3. Check that Elementor and Elementor Pro match

If one was updated and the other was not, the two halves of the editor may not understand each other. Update both to their latest versions from Dashboard → Updates, then clear any site cache.

4. Try Elementor Safe Mode

Elementor’s help centre recommends activating Safe Mode (under Elementor → Tools) to see whether you can edit without other plugins and your theme interfering. Safe Mode only affects the editor session, so visitors are not affected. If the editor opens in Safe Mode, the problem is a conflict with a plugin or theme.

5. Find the conflicting plugin on staging

On a staging copy, deactivate plugins one at a time, starting with recently updated ones and Elementor add-ons, and retest after each change. If the editor opens after a change, repeat the test to confirm the suspected conflict. Reactivate the others and contact that plugin’s developer with your version numbers.

6. Pause script optimisation and CDN features

Elementor’s documentation notes that Cloudflare’s Rocket Loader can delay or block editor scripts. Turn it off, or exclude admin and editor URLs from optimisation, and purge the cache. Do the same for “delay JavaScript” or “combine JavaScript” options in caching plugins.

7. Try the Switch Editor Loader Method setting

Some Elementor versions include Switch Editor Loader Method under Elementor → Settings → Advanced. Enabling it changes how the editor’s files are loaded and can help on some server configurations. Treat it as a workaround rather than a cure, and note the change in case it needs to be reversed later.

8. Look at the browser console

Press F12, open the Console tab and reload the editor. Errors mentioning a plugin folder can provide a lead, but do not prove that plugin is the root cause. A “500” error on a wp-json/elementor request means the server failed, and your host’s error log will say why. Errors about frame-ancestors or X-Frame-Options mean a security header is blocking the preview. Elementor documents that frame-ancestors 'self' is required, so ask your host to adjust it rather than removing the protection completely.

What a successful result looks like

The editor opens within a few seconds, widgets drag and drop normally, and saving shows no errors. Test with two or three pages, including one with your heaviest widgets. If you changed memory or caching settings, confirm the public site still loads quickly and the editor keeps working after clearing your browser cache.

Fix or workaround?

Raising memory to a sensible level, updating mismatched versions and replacing a broken add-on are genuine fixes. Disabling Rocket Loader just for the admin area is a reasonable, permanent configuration. Leaving Safe Mode switched on, permanently deactivating a security plugin, or editing pages only through a workaround are temporary measures, and should not be left in place without understanding the cause.

When to stop and ask for help

Stop if you cannot access the dashboard, if the server log shows fatal PHP errors you do not understand, or if the site handles orders or bookings and the only way forward is deactivating plugins on the live site. Also stop if raising memory “fixes” the problem but the site keeps getting slower, which can point to a deeper performance issue.

How to stop it happening again

Update Elementor, Elementor Pro and add-ons together, ideally on staging first.
Remove Elementor add-ons you no longer use, since each one loads its own scripts in the editor.
Keep PHP on a supported version. WordPress.org currently recommends PHP 8.3 or greater.
Exclude /wp-admin/ and editor URLs from aggressive script optimisation.

Also readPHP2Shell Explained: The Critical PHP Flaw Every Website Owner Must Patch Now

Her View

Most people who contact a developer about this have already reinstalled Elementor twice and lost an afternoon. The calmer route is to collect evidence first: version numbers, a screenshot of System Info and one console screenshot. Those three things turn a vague “Elementor is broken” into a problem someone can actually solve.

His Insight

Think of the editor as a much heavier app than your website. A server that serves pages comfortably can still struggle when one admin opens the editor with ten add-ons loaded. Memory, script order and security headers matter far more in the editor than on the front end, which is why the public site often looks fine while editing fails.

HView Digital Solutions

Elementor still not opening?

Tell us what you see and what changed. We can help check editor loading, plugin conflicts and server settings, then explain the next step before work begins.

Simple WordPress fixes start at ₹499. Complex plugin or server issues are scoped and quoted before work begins.

Get Elementor help

Frequently asked questions

Will deactivating plugins delete my content?

Normally, no. Deactivating a plugin stops it running but keeps its settings. Deleting a plugin can remove data, so deactivate on staging and avoid deleting until you are sure.

How much memory does Elementor need?

Elementor lists 256 MB minimum, 512 MB recommended and 768 MB for best performance. Sites with WooCommerce and many add-ons usually need the higher end.