Troubleshooting · Troubleshooting
How to Fix a Page Builder That Won't Load in WordPress
Short answer
A page builder that will not load is usually caused by low PHP memory, a plugin or theme conflict, or a script tool such as Cloudflare Rocket Loader. Run the builder's safe mode first, raise the WordPress memory limit to 256 MB, and purge all caches. If the editor opens in safe mode, turn plugins back on one at a time to find the conflict.
Key takeaways
- Safe mode loads the editor without third-party plugins, themes, or custom code, and only for you.
- Elementor lists a 256 MB WordPress memory limit as its minimum, with 512 MB recommended, as of November 2026.
- Cloudflare Rocket Loader can delay or break builder JavaScript, so turn it off and retest the editor.
- If the editor works in safe mode, reactivate plugins one at a time until it fails again.
- Contact your host when safe mode does not help or Site Health still shows a low memory limit.
- WordPress.org recommends PHP 8.3 or greater, as of November 2026.
What does “a page builder won't load” mean?
A page builder that will not load shows a grey or blank editor, a spinning loader, or a “failed to load” message instead of your page.
A page builder is a WordPress tool that lets you edit a page with a visual canvas, panels, and drag-and-drop blocks. Elementor, Beaver Builder, and Divi all load extra scripts and data to open that canvas.
When one of those parts fails, the rest of WordPress can still work, so your live site may look fine while the editor stays stuck. Elementor's help page on editing problems lists a blank page, a grey page with endless loading, and a greyed-out widget panel as the main signs.
The exact sign points to the cause. A grey screen often means a script conflict or a blocked frame. A blank white screen often means a fatal PHP error or a memory limit was hit.
Elegant Themes explains in its Divi failed-to-load guide that a “failed to load” message often means a plugin conflict, a custom code problem, or a server limit.
Why does a page builder fail to load?
A page builder fails to load most often because of low PHP memory, a plugin or theme conflict, old software, or a script tool that changes JavaScript.
The editor needs more memory than a normal page view because it loads the builder, your theme, and every active plugin at once. Elementor's requirements page, updated in October 2026, lists a WordPress memory limit of 256 MB, with 512 MB recommended and 768 MB for best performance, as of November 2026.
Elementor's system requirements also list WordPress 6.8 or greater, PHP 7.4 or greater, and MySQL 5.6 or greater or MariaDB 10.5 or greater.
A cache plugin or Cloudflare Rocket Loader can change or delay the JavaScript the editor needs. A security rule can block the editor frame.
A single broken widget or a bad line of custom code can stop the editor from starting. Change only one thing at a time.
| Cause | Main sign | First check |
|---|---|---|
| Low PHP memory | Grey screen, blank screen, or crash | Elementor > System Info or Tools > Site Health > Info |
| Plugin or theme conflict | Editor works in safe mode only | Safe mode test in your builder |
| Old WordPress, PHP, or builder | Editor fails after an update | Dashboard > Updates |
| Cache or Rocket Loader | Editor loads slowly or never finishes | Turn off Rocket Loader and purge cache |
| Blocked frame or bad URL | Grey page with a console error | Browser console and Settings > General |
How do you run the safe-mode test first?
Run the safe-mode test first because it tells you in one step whether a plugin, theme, or custom code is the cause.
Safe mode is a test mode in Elementor and Divi that loads the editor without third-party plugins, themes, or custom code, and only for you. Your visitors still see the normal site.
If the editor opens in safe mode, the problem is a conflict. If it still fails, the problem is more likely memory, a server limit, or a blocked script.
- Back up your site, or ask your host to make a restore point, before you change plugins or settings.
- In Elementor, go to Elementor > Tools, open the Safe Mode tab, and turn Safe Mode on.
- In Divi, go to Divi > Support Center and turn Safe Mode on.
- In Beaver Builder, add
&safemodeto the end of the editor URL, as described in Beaver Builder's plugin-conflict guide. - Try to open the same page in the builder again.
- Turn safe mode off after the test, so you can find the exact plugin or setting that caused the failure.
How do you fix low memory and old PHP?
Raise the WordPress memory limit to 256 MB, and update WordPress and PHP, because a page builder editor needs more memory than a plain page view.
WordPress tries to set WP_MEMORY_LIMIT to 40 MB for a single site and 64 MB for a multisite install by default. That is far below the 256 MB minimum Elementor lists.
If your host caps PHP below 256 MB, a line in wp-config.php cannot raise it above that cap, so ask your host to raise the PHP memory_limit itself. Our guide to the allowed memory size exhausted error explains the same limit in more detail.
- Go to Tools > Site Health > Info, open the Server section, and note the PHP version and PHP memory limit.
- Go to Dashboard > Updates and update WordPress, your builder, and your theme.
- Open
wp-config.phpand adddefine( 'WP_MEMORY_LIMIT', '256M' );above the line that reads “That’s all, stop editing! Happy publishing.” - Reload the editor and check Site Health again to confirm the new value.
- If the value did not change, ask your host to raise the PHP
memory_limitto 256 MB or 512 MB.
WordPress.org recommends PHP 8.3 or greater and MariaDB 10.11 or greater or MySQL 8.4 or greater, as of November 2026, in WordPress.org's requirements.
Elementor still lists PHP 7.4 as its floor, but a newer PHP version is the safer choice when your host supports it. If you need to change PHP, follow our guide on how to update the PHP version in WordPress.
How do you find the plugin or theme causing the conflict?
Deactivate all other plugins, test the editor, then turn plugins back on one at a time until the editor fails again.
This test is slow, but it names the exact plugin. Do it only after a backup, and do it when few visitors are on the site if you can. If safe mode already worked, this step confirms which plugin safe mode removed.
- Go to Plugins > Installed Plugins and deactivate every plugin except your page builder and, for Elementor, Elementor Pro.
- Open the page in the builder. If it loads, a plugin you turned off is the cause.
- Turn plugins back on one at a time, and open the builder after each one.
- When the editor fails again, the last plugin you turned on is the cause.
- Leave that plugin off, contact its author, or look for a different plugin with the same job.
- If the editor still fails with only the builder active, switch to a default theme such as Twenty Twenty-Five under Appearance > Themes and test again.
Cache and minify plugins deserve a check first, because they change the JavaScript the editor loads. Beaver Builder's guide says to clear the Beaver Builder cache under Settings > Beaver Builder > Tools by clicking Clear Cache before you test other plugins.
How do you fix cache, Rocket Loader, and script problems?
Turn off Rocket Loader, purge every cache, and turn off JavaScript minify tools, then open the editor again in a private browser window.
Rocket Loader defers JavaScript until after the page renders, so it can delay or break the scripts a page builder needs. Cloudflare's Rocket Loader docs say to disable Rocket Loader and retest if you see JavaScript or jQuery issues.
Elementor's help page gives the same advice for Cloudflare users who get stuck on the grey loading page.
- In Cloudflare, go to Speed > Settings, open Content Optimization, and set Rocket Loader to Off.
- In Cloudflare, purge the cache for the site.
- In WordPress, go to Elementor > Tools and click Regenerate CSS and Data, or in Divi go to Divi > Theme Options > Builder > Advanced and clear the Static CSS File Generation cache.
- Purge your cache plugin, and clear your browser cache or use a private window.
- Turn off JavaScript minify, combine, and defer settings in your cache or speed plugin, then test the editor again.
If the editor loads after this step, turn the speed settings back on one at a time to find the one that broke it. Leave Rocket Loader off for the editor if your builder vendor advises it. Our guide to Cloudflare cache rules for WordPress covers cache settings that can cause stale pages.
How do you check the browser console and site addresses?
Open the browser console, look for a red error, and check that your WordPress Address and Site Address match, because both problems stop the editor frame from loading.
Right-click the grey editor page, choose Inspect, and open the Console tab. A red error names the file or script that failed.
A message about X-Frame-Options means a security header is blocking the editor frame. Elementor's help page says to ask your host to set X-Frame-Options to SAMEORIGIN instead of DENY in that case.
- Check Settings > General and compare WordPress Address (URL) with Site Address (URL). They must use the same protocol and domain.
- Go to Settings > Permalinks and click Save Changes, even if you change nothing, to refresh the permalink rules.
- Try a different browser, or a private window, to rule out a browser add-on. Elementor lists browser add-ons as a cause when they block editor scripts.
- Turn off any browser add-on that blocks scripts or ads, then reload the editor.
- In Elementor, go to Elementor > Settings > Advanced and turn on Switch Editor Loader Method, which changes how the editor data loads.
How do you fix a single page that will not open in the builder?
Fix one page by clearing its builder cache, testing it in safe mode, and removing the last widget or code you added to it.
A single-page failure is different from a site-wide failure. The rest of the site loads, but one page has a broken widget, a bad embed, or a layout that is too large for the memory limit.
Beaver Builder's support forum notes that a page with many revisions can push a single page over the memory limit, and suggests adding &norevisions to the editor URL for that page.
- Open the page in safe mode and see if it loads. If it does, a widget or custom code on that page is the cause.
- Duplicate the page, if your builder allows it, and test the copy.
- Remove the most recent widget, HTML module, or embed from the page, then test again.
- Clear the builder CSS cache for that page, then purge your cache plugin.
- If the page still fails, restore it from a backup or a revision made before the problem started.
How do you know the fix worked, and when should you contact your host?
The fix worked when the editor opens, the widget panel loads, you can edit and save a small change, and the live page shows that change.
Test with a small, visible change, such as a heading word, then save and view the live page in a private window. If the change does not show, clear the cache again and check the live page. Our guide to changes not showing on a WordPress site covers stale cache steps in full.
Contact your host when safe mode does not help, when Site Health still shows a low memory limit after you edited wp-config.php, or when the console shows a server error such as a 500 or 403 error.
Ask the host for the PHP error log and the PHP memory_limit for your account. If the builder still fails in safe mode, the cause is likely on the server, not in a plugin. For a 500 error, see our guide to the 500 internal server error.
What mistakes should you avoid?
Do not change five settings at once, do not skip the backup, and do not keep an old builder version because an update feels risky.
Changing many settings at once hides the cause, so you cannot tell which change fixed the editor. Editing wp-config.php without a backup can lock you out if a line is typed wrong.
Keeping an old builder, theme, or PHP version leaves the exact bug that the update fixed in place. Test each fix, note the result, and only then move to the next step.
Frequently asked questions
Why does my page builder load on some pages but not others?
A single page can fail when it has a broken widget, a bad embed, or a layout large enough to hit the memory limit. Test that page in safe mode, remove the most recent widget or code you added, and clear the builder cache. If it still fails, restore the page from a revision made before the problem started.
Is it safe to use safe mode on a live site?
Yes. Safe mode in Elementor and Divi disables third-party plugins, themes, and custom code only for your logged-in user, so visitors still see the normal site. Turn safe mode off after the test, then use the normal plugin test to find the exact cause.
How much memory does a page builder need?
Elementor lists 256 MB as the minimum WordPress memory limit, with 512 MB recommended and 768 MB for best performance, as of November 2026. WordPress tries to set 40 MB for a single site by default, which is far below that level. If your host caps PHP below 256 MB, ask the host to raise it.
Can Cloudflare stop a page builder from loading?
Yes. Cloudflare Rocket Loader defers JavaScript until after the page renders, which can delay or break the scripts a page builder needs. Turn Rocket Loader off in Cloudflare under Speed, then Settings, then Content Optimization, purge the Cloudflare cache, and open the editor again in a private window.
What should I send my host if the builder still will not load?
Send the host the page URL, the exact error or screen you see, whether safe mode helped, and a copy of Tools, then Site Health, then Info. Ask for the PHP error log and the PHP memory limit for your account. Those two items show whether the server stopped the editor.
Should I reinstall the page builder to fix it?
Reinstalling is a late step, not a first step. Run safe mode, raise memory, clear caches, and test for a plugin conflict first, because those steps find the cause. Reinstall only if the builder files are damaged or an update failed, and keep a full backup before you remove the plugin.
Sources
- Can't Edit with Elementor - What Should I Do? Elementor
- System Requirements to Use Elementor Elementor
- Oops it, looks like the Divi Builder failed to load Elegant Themes
- Plugin conflicts Beaver Builder
- Requirements WordPress.org
- Rocket Loader Cloudflare
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
