
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.
Source video: Watch on YouTube (Elementor)
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:
| Root cause | Share 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.
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 →
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:
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.
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.
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.
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.
| Setting | Elementor minimum | Elementor recommended | Common on entry plans |
|---|---|---|---|
| WordPress memory limit | 256 MB | 512–768 MB | 64–128 MB |
| PHP version | 7.4 | 8.x | 7.4–8.1 |
| WordPress version | 6.5 | Latest | Often one or two versions behind |
| X-Frame-Options header | SAMEORIGIN | SAMEORIGIN | Sometimes 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:
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.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:
| What you see | Likely cause | Fix |
|---|---|---|
| Console mentions “frame” or “refused to display” | X-Frame-Options or CSP header | Host sets SAMEORIGIN / ‘self’ |
| Broke right after enabling Cloudflare or a speed plugin | Scripts loaded async or delayed | Bypass Rocket Loader and JS delay for Elementor URLs |
| Every page stuck after an Elementor update | Version mismatch or stale CSS | Update both plugins, then Clear Files & Data |
| Only one page or template stuck | Corrupted widget or custom code | Draft the custom code or rebuild the widget |
| “Allowed memory size exhausted” or 500 error | Low PHP memory | Raise 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:
*elementor* and ?elementor_library=*, per Elementor and Cloudflare Rocket Loader. If Cloudflare also shows timeout errors, see our Cloudflare error 522 fix.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 →
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:
| Cause | Typical 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.
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:
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.
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:
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.
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.
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.
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.
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.
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 A Free Proposal
Complete the form and our team will contact you to discuss your goals. Let’s grow your business.
Chat with us on WhatsApp
Tell us a little about what you need. We'll open WhatsApp with your message ready to send.