Skip to content
Rescue 404
Rescue

Elementor Problems

Elementor Editor Loading Forever (WordPress Repair)

Intermediate Risk: medium

Last reviewed

Hosting access may not be needed Database access usually not needed

Direct answer

When Elementor’s loading ring never finishes, identify the first pending or repeating request, then test Safe Mode, memory, Elementor Free/Pro compatibility, REST access, and script optimization before changing page content.

An endless spinner means Elementor has not completed its editor boot sequence, even if the public page still works. This WordPress Repair guide focuses on requests that remain blocked or starved, which is distinct from a canvas that finishes loading and stays blank.

Intermediate

Key facts

Verifiable numbers and definitions — each claim links to its source.

  • Elementor’s troubleshooting guide identifies a gray page or loading spinner and recommends Safe Mode, conflict testing, console checks, and an alternate editor loader when appropriate. (Elementor — Can’t Edit with Elementor)
  • Elementor states that Safe Mode loads the editor without activated plugins or themes for the logged-in user and does not affect visitors. (Elementor — Slow Editor)
  • Elementor’s widget-panel guide names memory limits, plugin conflicts, and server settings as causes of a continuously loading panel. (Elementor — Widget Panel)
  • Elementor documents that Cloudflare Rocket Loader can alter script loading in a way that breaks or stalls the editor. (Elementor — Rocket Loader)

What the error means

Opening Elementor starts a sequence of PHP work, JavaScript bundles, a preview document, authenticated WordPress requests, and document initialization. One slow, blocked, or repeatedly retried dependency can keep the loading state alive indefinitely: the browser may wait on a security challenge, PHP may exhaust memory, an optimizer may alter script order, or a plugin may throw before Elementor signals readiness. The spinner is therefore a timing symptom, not a diagnosis, and the first request that stays pending or fails is more useful than repeatedly refreshing.

Common symptoms

  • The Elementor logo or circular loading indicator continues indefinitely
  • The editor toolbar and usable canvas never become interactive
  • Network requests remain pending, repeat, or return 401, 403, 500, or HTML challenges
  • Safe Mode loads the editor while the normal session keeps spinning
  • The issue improves in an incognito window or after disabling browser extensions
  • Small pages load but complex pages or templates time out
  • The widget panel continuously says Loading even when part of the preview appears

Most likely causes

  1. 01 Insufficient WordPress or PHP memory during editor initialization
  2. 02 A plugin, theme, addon, or custom-code conflict interrupting Elementor JavaScript
  3. 03 Elementor Free and Elementor Pro versions that are not compatible
  4. 04 REST, admin, or preview requests blocked by a WAF, security plugin, login redirect, or proxy
  5. 05 Cloudflare Rocket Loader or another defer, delay, combine, or minify feature changing script order
  6. 06 Slow PHP workers, database queries, external calls, or server execution timeouts
  7. 07 An overloaded browser session, unsupported browser, or extension modifying editor requests

What changed before the problem started

  • Elementor, Elementor Pro, an addon, WordPress, or the theme updated
  • A performance, security, consent, translation, or browser extension was added or reconfigured
  • Cloudflare, CDN, WAF, or host caching settings changed
  • PHP version, memory, workers, or execution limits changed
  • The affected page gained large nested layouts, dynamic content, or resource-heavy widgets

Troubleshooting steps

  1. 01

    Time one load and inspect the request waterfall

    Open DevTools → Network, preserve the log, launch Elementor once, and find the earliest request that remains pending or turns red. Record its URL, status, duration, and response before refreshing; repeated reloads can hide the actual bottleneck.

  2. 02

    Test Safe Mode and a clean browser

    Back up, enable Elementor → Tools → Safe Mode, and test the same page in an incognito window with extensions off. If either test works, isolate WordPress plugins, the theme, custom code, or browser extensions systematically instead of combining unrelated fixes.

  3. 03

    Check Elementor system requirements and memory

    Review Elementor → System Info for WordPress, PHP, database, and memory values. Increase a genuinely low WordPress admin memory limit only to a host-supported value, then retest; if the server limit does not change, ask the host rather than adding duplicate constants.

  4. 04

    Align Elementor and Elementor Pro

    Record both versions and confirm they belong to a compatible release path. If one package updated alone, update or roll back that package from a backup so Free and Pro are aligned; do not bulk-update every addon while causation is still clear.

  5. 05

    Bypass optimization for logged-in editor traffic

    Temporarily exclude Elementor editor, preview, admin, and authenticated REST requests from page cache, JavaScript delay or combine, and Cloudflare Rocket Loader. Purge all layers after the rule change, then restore features one at a time.

  6. 06

    Compare a small page with the affected page

    Create or use a simple test page and open it with Elementor. If only a complex page spins, duplicate it on staging and investigate its widgets, templates, dynamic sources, and size instead of treating the entire installation as broken.

When to stop troubleshooting

Stop if requests remain pending because the host is saturated, logs show a fatal you cannot safely patch, security exceptions cannot be narrowed, the only copy is a live revenue page, or version rollback lacks a verified backup; provide the Network waterfall, versions, logs, and Safe Mode result to the next technician.

Information to collect before requesting help

  • 01 Screen recording or screenshot of the endless loading state
  • 02 URL, status, duration, and response of the first pending or failed request
  • 03 Elementor, Elementor Pro, addon, WordPress, theme, and PHP versions
  • 04 WordPress and server PHP memory limits
  • 05 Whether Safe Mode or incognito changes the result
  • 06 Whether a simple page loads while the affected page does not
  • 07 Active cache, optimization, security, CDN, and browser-extension list
  • 08 Relevant PHP, server, WAF, or application-performance log excerpt

How a professional repairs the problem

A technician captures a clean editor waterfall, follows its first unresolved dependency into PHP, database, WAF, CDN, or browser evidence, and isolates conflicts in a staging clone. They align Elementor packages, right-size resources, scope cache and firewall exclusions, and verify that representative pages open, save, and publish at normal speed.

Frequently asked questions

How long should Elementor normally show the spinner? +
There is no universal time, but a spinner that far exceeds the site’s normal admin response time and never enables controls is stuck. Capture the Network log instead of waiting through repeated identical attempts.
Is this the same as an Elementor blank screen? +
No. Endless loading keeps an active loading state because boot has not completed; a blank-screen case usually leaves an empty canvas after the shell or preview attempt finishes.
Why does Safe Mode fix endless loading? +
Safe Mode loads Elementor without the normal theme and plugins for the administrator session, so success there points to a conflict or resource cost introduced by that surrounding code.
Can Cloudflare Rocket Loader cause the spinner? +
Yes. Elementor documents that Rocket Loader can change editor script loading and leave the gray loading page stuck. Exclude editor traffic rather than disabling the CDN permanently.
Should I keep raising PHP memory? +
No. Meet the documented and workload-appropriate limit, confirm the effective server value, and inspect logs. More memory will not repair a 403, login redirect, bad script order, or slow external call.
Will reinstalling Elementor erase designs? +
Replacing plugin code does not normally remove database-stored layouts, but a complete backup remains mandatory. Do not delete Elementor database records or uploads during the reinstall.

Repair dispatch

Still Need Help Fixing Your Website?

If you are not comfortable editing website files, changing server settings, repairing a database, or troubleshooting a live website, professional help may prevent additional damage or downtime. We will review the problem before accepting the repair.

  • You will receive a clear explanation of the likely cause.
  • We will tell you if the issue falls outside our repair scope.
  • No additional work will be performed without approval.
  • A backup should be created whenever access and website condition allow it.
Emergency repair Request diagnosis

Do not share passwords through an unencrypted contact form — use Password Pusher (self-destructing link). Prefer a dedicated Rescue 404 admin account, not your personal owner login; if you cannot create one yet, we will add ours after repair.

Written by Josh

Last reviewed

Platform note: Full rescue available for WordPress and self-hosted sites. Wix, Squarespace, Webflow, Weebly, and similar closed builders have very limited backend access — fixes may not be possible. I will tell you honestly before we start.