Elementor not loading means one of several things depending on what you actually see. A spinning loader that never stops is a JavaScript crash, usually a plugin conflict. “The preview could not be loaded” is an SSL or URL mismatch. A blank white editor is a CSS/JS conflict. Post-update breakage needs a data migration. Check which symptom matches yours before trying anything.
Quick First Steps
Before going through full diagnosis, try these in order:
- Hard refresh the Elementor editor (Ctrl+Shift+R on Windows, Cmd+Shift+R on Mac) to clear the browser cache
- Try a different browser – Chrome for Elementor is the most tested combination
- Disable browser extensions – ad blockers, privacy extensions, and script blockers frequently interfere with Elementor’s JavaScript
- Check if a recent plugin update coincided with the loading failure
If none of these resolve it, proceed with diagnosis below.
Fix 1: “The Preview Could Not Be Loaded” Error
This specific error means Elementor’s preview iframe cannot communicate with WordPress. Most common causes:
SSL/HTTPS mixed content: If your WordPress URL uses HTTPS but assets are loading over HTTP (or vice versa), the preview iframe is blocked. Go to WordPress -> Settings -> General and ensure both WordPress Address and Site Address use the same protocol (both https://). Also check that WP_HOME and WP_SITEURL in wp-config.php match.
Cookie domain mismatch: WordPress uses cookies for the editor authentication. If your site is accessible via multiple domains or subdomains, cookie settings may block the preview. Ensure you are accessing the editor through the same domain as WordPress is configured for.
Go to Elementor -> Tools -> General -> Regenerate Files and flush URLs. This rebuilds Elementor’s CSS cache and sometimes resolves preview loading issues caused by stale cached data.
Problem not solved? Describe the issue and get a free estimate.
Fix 2: Elementor Loading Spinner Never Stops
An infinite loading animation means Elementor’s JavaScript initialisation is failing. Open browser DevTools (F12) -> Console tab while the editor loads. JavaScript errors there identify the specific conflict. Common sources:
Plugin conflict: Another plugin’s JavaScript is preventing Elementor from initialising. Deactivate all plugins except Elementor (and Elementor Pro if applicable) and try loading the editor. If it loads, reactivate plugins one at a time until the conflict reappears. The last reactivated plugin is the conflict.
PHP memory limit too low: Elementor needs at least 256MB of PHP memory. Add to wp-config.php:
define( 'WP_MEMORY_LIMIT', '512M' );Fix 3: Elementor Editor Loads Blank (White Screen)
A white screen in the Elementor editor is usually a JavaScript error that crashes the page. Check browser DevTools console. Also check:
- Go to Elementor -> Tools -> Regenerate CSS & Data. This rebuilds all Elementor-generated CSS files.
- Clear your caching plugin‘s cache completely. Cached JS files can conflict with updated Elementor JavaScript.
- Disable any JavaScript minification or combination in your caching plugin – these frequently break Elementor by merging its JavaScript incorrectly.
Fix 4: Elementor Not Loading After WordPress Update
WordPress updates can break Elementor if the new WordPress version changes an API that Elementor depends on, or if Elementor’s files were not fully updated. Go to Plugins -> Elementor and check that the latest Elementor version is installed. Click “Update Now” if an update is available.
If already on the latest version, go to Elementor -> Tools -> Replace URLs and run the URL replacement to ensure Elementor’s internal URLs are correctly set. Also try deactivating and reactivating the Elementor plugin (not uninstalling – just deactivate and activate again) to clear its activation cache.
Fix 5: Increase Server Timeout for Elementor
On slow shared hosting, Elementor’s editor can time out during loading because the PHP response takes too long. Add to .htaccess:
php_value max_execution_time 180
php_value memory_limit 512M