The editor takes forever to load, the preview stays gray, or the finished page builds up sluggishly? That’s not unusual with Elementor \u2013 and it’s almost never Elementor alone. Usually it’s a mix of server settings, plugins and content. Here are the seven most common causes and how to fix them.<\/p>\n
Is it not the website but the editor itself that hangs?<\/strong> Then read our guide Elementor stuck loading? How to fix the loading screen problem in 9 steps<\/a>.<\/p>\n Elementor is a large plugin: the editor loads lots of widgets, settings and templates at once. By default, WordPress itself only sets a memory limit of 40 MB for the frontend. That’s enough for a simple blog, but not for a page builder. For Elementor Pro, you should plan for at least 512 MB<\/strong>.<\/p>\n Typical signs:<\/strong> The editor doesn’t load completely, you see a white page, or you get the error message \u201cAllowed memory size exhausted\u201d.<\/p>\n Solution:<\/strong> Increase the memory limit \u2013 we explain how step by step in our article How to increase the Elementor memory limit<\/a>.<\/p>\n Newer PHP versions run the same code much faster than old ones. If your site is still on PHP 7.x, you’re leaving noticeable performance on the table \u2013 and you no longer get security updates.<\/p>\n Solution:<\/strong> Switch to PHP 8.1 or newer. In Plesk, you’ll find this under \u201cPHP Settings\u201d for your domain. Make a backup first and afterwards check that all plugins still work.<\/p>\n Every plugin loads its own code, often in the editor too. Elementor add-on packs with dozens of widgets are especially heavy, even if you only use two of them.<\/p>\n Solution:<\/strong> Deactivate plugins you don’t need and turn off unused widgets in add-on packs. Rule of thumb: one good plugin for a task beats three that overlap.<\/p>\n A photo straight from the camera can easily be 5 MB or more. On a page with ten images like that, the visitor waits \u2013 and so does the editor.<\/p>\n Solution:<\/strong> Resize images to the width you actually need before uploading (1,600 to 2,000 pixels is enough for most layouts) and save them as WebP. An image optimization plugin can also do this automatically.<\/p>\n Without caching, WordPress rebuilds every page on every request: run PHP, query the database, generate HTML. With Elementor pages, this takes especially long.<\/p>\n Solution:<\/strong> OPcache on the server keeps compiled PHP code in memory, and a page cache serves ready-made pages. At servflix.com, OPcache is enabled in every plan.<\/p>\n Containers in containers in containers \u2013 every level adds extra HTML that the browser has to process. On top of that, there are often several Google Fonts in many weights.<\/p>\n Solution:<\/strong> Keep layouts flat, handle recurring styles with global classes and colors, and limit yourself to two fonts with just a few weights. In the Elementor settings under \u201cFeatures\u201d, you’ll also find performance options such as optimized asset loading.<\/p>\n Elementor pages access many files and database entries on every request. If these sit on slow disks or overloaded servers, even the best optimization can only help so much.<\/p>\n Solution:<\/strong> When choosing hosting, look for NVMe storage, a fast web server like NGINX and plenty of RAM. We explain the difference between NVMe and classic SSDs in our article NVMe vs. SSD for WordPress<\/a>.<\/p>\n1. Not enough memory (PHP memory limit)<\/h2>\n
2. Outdated PHP version<\/h2>\n
3. Too many plugins and add-ons<\/h2>\n
4. Large, uncompressed images<\/h2>\n
5. No caching<\/h2>\n
6. Overly nested layouts and too many fonts<\/h2>\n
7. Slow storage at your web host<\/h2>\n
Checklist: speed up Elementor<\/h2>\n