ZenWeb - Blog - Elementor Not Loading? How to Fix the Stuck Editor Spinner

Elementor Not Loading? How to Fix the Stuck Editor Spinner

November 5, 2026

Share this post:

Elementor Not Loading? How to Fix the Stuck Editor Spinner
TL;DR: When Elementor is not loading and the editor sits on a grey screen or endless spinner, the cause is usually a plugin conflict, a low PHP memory limit, or a cache or Cloudflare setting that blocks Elementor’s scripts. Test in an incognito window, turn on Safe Mode, raise memory to at least 256 MB, then clear Elementor’s files and data. Most cases are fixed in under an hour.

You click Edit with Elementor to change a price or a promo banner, and the page never opens. The logo spins, the screen stays grey, and your campaign goes live tomorrow. For a Malaysian SME that updates its own website, this is one of the most common WordPress headaches we see.

The good news: a stuck editor almost never means your website is broken. Visitors usually still see the live site normally. The problem sits between the editor’s scripts, your server and your browser, and it can be traced step by step.

This guide ranks the causes by how often we see them on client sites. It gives the fixes from Elementor’s own help centre (checked in October 2026), sets honest time expectations and shows how to stop it coming back. If you are still choosing a page builder rather than fixing one, read our Elementor review instead.

In this official video, the Elementor team explains Safe Mode, the built-in tool you will use in Section 3 to find what is blocking the editor.

What Is Safe Mode — Elementor

Source video: Watch on YouTube (Elementor)

1. Why Is Elementor Not Loading?

Quick Answer: Elementor not loading usually means something stopped the editor’s JavaScript before it finished starting. On business websites, the most likely cause is a conflict with another plugin or the theme. Low PHP memory, caching or Cloudflare script optimisation, browser extensions and mismatched Elementor and Elementor Pro versions come next.

Elementor’s help article Elementor stuck on loading screen lists the same suspects. Here is how they rank when Malaysian businesses bring a stuck editor to us:

What Causes a Stuck Elementor Editor — Share of ZenWeb Cases
Root causes of Elementor editors stuck on the loading screen, ZenWeb client tracking 2024 to 2026.
Root causeShare of cases
Plugin or theme conflict (often after an update)

34%

PHP memory limit too low

21%

Cache, minify or Cloudflare Rocket Loader blocking scripts

17%

Browser extension or stale browser cache

11%

Elementor and Elementor Pro on mismatched versions

8%

Server security headers, old PHP or a corrupted widget

9%

Source: From ZenWeb client tracking of Malaysian SME WordPress sites, 2024–2026. Illustrative of typical patterns, not Elementor data.

The pattern behind the top cause is simple. Someone clicks “Update all” on a Monday morning, a slider or form plugin loads its own scripts into the editor, and Elementor stops halfway. Notice the timing too: if the editor broke right after an update, that update is your first suspect.

A stuck editor is different from a slow website. If visitors also wait ages for pages to load, read our guide to fixing a slow website, because the same server limits can cause both.

Key takeaway: Start with what changed last. Over half the stuck editors we fix trace back to a recent plugin update or a server limit, not to Elementor itself.

Tired of a website you can’t edit?

We build and maintain Elementor websites for Malaysian businesses, with hosting limits and plugins set up correctly from day one. See our web design services →


2. What Should You Check in the First Five Minutes?

Quick Answer: Rule out your browser first. Open the editor in an incognito window, then try a second browser. If it loads there, clear your cache and switch off ad blockers and other extensions. If it still hangs everywhere, open the browser console and note the red error, because it points to the real cause.

These checks need no WordPress changes, so they are safe for anyone in the office to try:

  1. Open an incognito window. In Chrome press Ctrl + Shift + N, log in to WP Admin and open the page in Elementor again.
  2. Try another browser. Elementor suggests Chrome, Firefox, Safari or Opera. An outdated browser can also fail; Elementor no longer supports Internet Explorer at all.
  3. Disable extensions one by one. Ad blockers, password managers and translation add-ons can block editor scripts.
  4. Read the console. Right-click the grey page, choose Inspect, open the Console tab and screenshot any red errors.
  5. Edit on a desktop. Elementor does not support editing on phones or tablets, per its system requirements page.

Elementor’s common troubleshooting steps page walks through clearing Chrome’s cache with the same menu. If only some staff can open the editor, compare their browsers. A site that misbehaves in one browser but not another is covered in our guide to a website that won’t load on some browsers.

Key takeaway: If incognito works, the problem is on your computer, not your website. Fix the browser and stop there.

3. How to Use Elementor Safe Mode to Find a Plugin Conflict

Quick Answer: Turn on Safe Mode under Elementor > Editor > Tools. It loads the editor without your theme and other plugins. If the editor opens in Safe Mode, a plugin or theme is the cause. Turn Safe Mode off, deactivate plugins except Elementor and Elementor Pro, then reactivate them one at a time.

These steps follow Elementor’s troubleshooting guide and its debugging with Safe Mode page, checked in October 2026. Only users with the Administrator role can turn Safe Mode on.

  1. Back up the site. Take a full backup from your hosting panel before changing plugins.
  2. Enable Safe Mode. In WP Admin go to Elementor > Editor > Tools, set Safe Mode to Enable and click Save Changes.
  3. Open the stuck page. If the editor now loads, a plugin or the theme is to blame.
  4. Deactivate other plugins. Go to Plugins > Installed Plugins, tick everything except Elementor and Elementor Pro, and choose Deactivate from Bulk actions.
  5. Reactivate one by one. Test the editor after each plugin until it breaks again. That last plugin is the culprit.
  6. Test the theme. If plugins are clean, activate the Hello Elementor theme under Appearance > Themes. Theme preloaders are a known trigger.
  7. Turn Safe Mode off and update, replace or report the conflicting plugin to its developer.

On a live online store, do this on a staging copy or outside business hours. Deactivating plugins can briefly hide add-to-cart buttons or stop order emails, which our guides on a missing WooCommerce add to cart button and WooCommerce emails not sending cover. If an interrupted update leaves the site showing a maintenance notice, see WordPress stuck in maintenance mode.

Key takeaway: Safe Mode answers one question fast: is it Elementor, or something around it? Answer that before you touch the server.

4. Is Your Hosting Too Weak for Elementor?

Quick Answer: Often, yes. Elementor needs a WordPress memory limit of at least 256 MB, PHP 7.4 or later, and security headers that allow the editor’s preview frame. Cheap shared hosting plans in Malaysia often ship with lower memory and stricter headers. Check WooCommerce sites especially, as they need more memory.

Compare your server with Elementor’s official system requirements, last updated August 2026. You can see your current values in WP Admin under Tools > Site Health > Info > Server.

Elementor Server Requirements vs Typical Entry-Level Shared Hosting
Elementor minimum and recommended server settings compared with typical entry-level shared hosting defaults seen on Malaysian SME sites.
SettingElementor minimumElementor recommendedCommon on entry plans
WordPress memory limit256 MB512–768 MB64–128 MB
PHP version7.48.x7.4–8.1
WordPress version6.5LatestOften one or two versions behind
X-Frame-Options headerSAMEORIGINSAMEORIGINSometimes DENY after “hardening”
CSP frame-ancestors‘self’‘self’Sometimes ‘none’ from security plugins

Source: Elementor Help — Elementor System Requirements (August 2026); entry-plan column from ZenWeb site audits of Malaysian SME hosting, 2024–2026.

How to fix each gap:

  • Memory. Add define( 'WP_MEMORY_LIMIT', '256M' ); to wp-config.php, as described in WordPress’s wp-config.php documentation. If your host caps PHP memory lower, ask them to raise it. Our guide to the WordPress memory limit exhausted error has the full method.
  • PHP version. Most cPanel plans let you change it under Select PHP Version. Test on staging first.
  • Headers. Ask your host to set X-Frame-Options to SAMEORIGIN and CSP frame-ancestors to ‘self’. A “DENY” value blocks the editor’s preview frame.
Key takeaway: A RM10-a-month hosting plan with 128 MB of memory was never built for a page builder plus WooCommerce. Fix the limit once and several “random” errors disappear together.

5. How to Fix Cache, Cloudflare and Corrupted Widget Problems

Quick Answer: Clear Elementor’s own files and data, purge your caching plugin, and stop Cloudflare Rocket Loader or JavaScript delay features from touching editor pages. If only one page is stuck, a corrupted widget or broken custom code on that page is the likely cause. Match the console error to the fix below.

Use the console message you saved in Section 2 to jump straight to the right fix:

Stuck Elementor Editor: Symptom, Likely Cause and Fix
Common stuck Elementor editor symptoms mapped to their likely cause and the official fix.
What you seeLikely causeFix
Console mentions “frame” or “refused to display”X-Frame-Options or CSP headerHost sets SAMEORIGIN / ‘self’
Broke right after enabling Cloudflare or a speed pluginScripts loaded async or delayedBypass Rocket Loader and JS delay for Elementor URLs
Every page stuck after an Elementor updateVersion mismatch or stale CSSUpdate both plugins, then Clear Files & Data
Only one page or template stuckCorrupted widget or custom codeDraft the custom code or rebuild the widget
“Allowed memory size exhausted” or 500 errorLow PHP memoryRaise memory to 256 MB or more

Source: Elementor Help — Elementor stuck on loading screen, Elementor and Cloudflare Rocket Loader and System Requirements pages; compiled by ZenWeb, October 2026.

The menu paths, per Elementor’s help centre:

  • Clear Files & Data: go to Elementor > Editor > Home, click Tools, then Clear Files & Data, as shown on the Clear Files & Data help page. Back up first.
  • Rocket Loader: create Cloudflare rules that skip URLs containing *elementor* and ?elementor_library=*, per Elementor and Cloudflare Rocket Loader. If Cloudflare also shows timeout errors, see our Cloudflare error 522 fix.
  • Custom code: go to Elementor > Editor > Custom Elements, click Code, use Quick Edit and set the snippet to Draft.
  • Corrupted Loop widget: disable the feature in Elementor > Element Manager, save the page without it, re-enable it and rebuild the widget.
Key takeaway: One page stuck points to that page’s content. Every page stuck points to the server, cache or plugin versions. That one question halves your search.

Still staring at a grey screen?

Our team fixes Elementor and WordPress issues for Malaysian businesses without risking your live site. Get Elementor website support from ZenWeb →


6. How Long Does It Take to Fix Elementor Not Loading?

Quick Answer: Browser and cache issues take minutes. A plugin conflict found with Safe Mode usually takes under an hour. Server changes depend on your host’s support queue and can take from a few hours to two working days. Corrupted content or custom theme code takes longest because pages may need rebuilding.

Use these ranges to plan your campaign dates, not as a promise:

Typical Time to Fix a Stuck Elementor Editor, by Cause
Typical time to fix a stuck Elementor editor for each root cause.
CauseTypical time to fix
Browser cache or extension

5–15 minutes

Plugin or theme conflict

30–60 minutes

Cache or Cloudflare settings

1–2 hours

Memory, PHP or headers via your host

Few hours–2 working days

Corrupted widget or custom theme code

1–3 working days

Source: ZenWeb operational observations across Malaysian client WordPress sites, 2024–2026. Host response times vary by plan.

While the editor is down, your live pages keep selling, but you cannot change them. Plan around that. If a product page needs urgent edits for a sale, check the pages your ads point to. This matters most if you also see Google Shopping ads not showing or Meta catalog products getting no impressions at the same time. Some higher Elementor plans include access to its support team, while free users rely on the help centre and community.

Key takeaway: The slow part is rarely the fix itself. It is waiting on a host or rebuilding broken content, so start those requests first.

7. How to Stop the Elementor Editor Breaking Again

Quick Answer: Update on a staging copy first, keep Elementor and Elementor Pro on matching versions, give the site at least 256 MB of memory, and exclude editor pages from caching and script delay. Take a backup before every update. These habits remove most of the causes ranked in Section 1.

We run this routine on every Elementor site we maintain:

  • Staging before live. Test plugin updates on a copy of the site, never on Monday morning before a launch.
  • Update in pairs. Update Elementor and Elementor Pro together so versions always match.
  • Fewer add-on packs. Each extra widget pack adds scripts that can clash. Remove the ones you no longer use.
  • Editor-safe caching. Exclude logged-in users and Elementor URLs from JavaScript delay and minify rules.
  • Right-sized hosting. Move to a plan with 512 MB memory if you run WooCommerce, as Elementor itself advises.
  • Backups you have tested. Keep daily backups and confirm you can restore them.

Shops need extra care, because an editor fix can ripple into checkout. After any plugin change, place a test order to confirm shipping still shows at checkout and orders are not left on WooCommerce pending payment. Also check your analytics: rebuilt forms and buttons often break tracking, which shows up as (not set) in GA4 reports or GA4 custom events not showing.

Key takeaway: Prevention costs an hour a month. A stuck editor the night before a campaign costs far more in delays and lost sales.

8. When Should You Call in an Expert?

Quick Answer: Get help when Safe Mode does not fix the editor, when the console shows PHP or server errors you cannot read, when you have no staging site or tested backup, or when the editor problem comes with other site errors. These cases carry a real risk of breaking the live site.

Escalate when you see any of these:

  • Safe Mode changes nothing. The cause is then deeper in the server, the database or Elementor’s data.
  • The front end breaks too. A blank page for visitors needs our guide to the WordPress white screen of death, not just an editor fix.
  • Unknown code or redirects appear. Strange scripts in the console can mean malware; see cleaning a hacked website.
  • Google cannot reach the site. If Search Console reports a DNS resolution error as well, the hosting itself needs attention.

ZenWeb is a Google Partner agency that has worked with 500+ Malaysian businesses. Our web design services include building and maintaining Elementor websites, so we can find the conflict, right-size your hosting and protect your live pages while we work.

Key takeaway: Browser checks and Safe Mode are safe DIY steps. Server, database and security problems are where expert help saves time and risk.

9. Conclusion

Elementor not loading feels like your website has broken, but it is usually one blocked script with a clear cause. Work in order: test incognito, read the console, turn on Safe Mode, check memory and headers, then clear Elementor’s files and data and fix your cache rules. Then stop it coming back with staging, matched versions and right-sized hosting. For more ways to keep your site and marketing running smoothly, start at the ZenWeb home page.


10. Frequently Asked Questions

1. Will my live website go down if Elementor is not loading?

Usually not. A stuck editor affects the editing screen, and visitors normally still see the published pages. If visitors also see errors or a blank page, treat it as a site-wide problem and check your server and recent updates.

2. Is it safe to enable Elementor Safe Mode on a live site?

Yes. Safe Mode only changes how the editor loads for you while you test. Visitors keep seeing the normal site. Remember to turn it off under Elementor > Editor > Tools when you finish.

3. How much memory does Elementor need?

Elementor lists a WordPress memory limit of 256 MB as the minimum, 512 MB as recommended and 768 MB for best performance. WooCommerce sites should aim for at least 512 MB.

4. Why does Elementor load in incognito but not in my normal browser?

A browser extension or old cached files are blocking the editor’s scripts. Clear your browser cache, then switch off ad blockers and other extensions one at a time until the editor loads.

Need your website editable again before the next campaign?

Tell us what you see and what changed last. We will trace the cause, fix the editor safely and set your site up so it stays fixed.

Get help with my website →

Table of Contents
Table of Contents

Get A Free Proposal

Complete the form and our team will contact you to discuss your goals. Let’s grow your business.