In case you suffer from the Elementor slow performance while loading in the backend, please read the following article carefully.
The recommended and default Jupiter X page editor is Elementor. While the plugin itself requires more resources than usual (at least 128M of Memory), adding more elements via other plugins also adds to this requirement more and more. So, the biggest issue with performance when you are using Elementor is with Memory Limit. By default WordPress Memory Limit is 40M and you need to manually increase your Memory Limit to fix a part of the issue. Here you can find more about how to increase the WordPress Memory Limit:
Increasing the WordPress Memory Limit
And you can find more information about why you should keep your active plugins at minimum to avoid memory limit issues:
Why should I keep my active plugins at minimum?
It’s only one side of the problem. Sometimes even increasing the Memory Limit doesn’t resolve the issues. So, in these cases, you need to see what server configurations is limited and causes a slow performance. The best thing you can do it to ask your web host to monitor and see if it’s the CPU limitation, Memory or Database limitation which is causing slowness on the Elementor or even blank screen of death. However, a common issue here is the lack of GZIP OUTPUT COMPRESSION which will reduce the loading time a lot. Check the following screenshots. The first one is taken on a SiteGround minimal plan while all of the bundled plugins were active.
SiteGround does not enable GZip output compression by default. As you can see, the page tries to load almost 40MB of JSON data inside the page. (This image is taken while the Elementor 2.5 beta was on, it has a lazy loading function that help investigating issues like this). Now check the the below screenshot while the gzip output compression was on:
The difference is noticeable. the first one took 2.5 minutes to load, while the second one only took 22 seconds. The only thing we added here was to enable gzip output compression by adding this code to .htaccess file:
<IfModule mod_deflate.c>
AddOutputFilterByType DEFLATE text/plain
AddOutputFilterByType DEFLATE text/html
AddOutputFilterByType DEFLATE text/xml
AddOutputFilterByType DEFLATE text/css
AddOutputFilterByType DEFLATE text/json
AddOutputFilterByType DEFLATE application/xml
AddOutputFilterByType DEFLATE application/xhtml+xml
AddOutputFilterByType DEFLATE application/rss+xml
AddOutputFilterByType DEFLATE application/javascript
AddOutputFilterByType DEFLATE application/x-javascript
AddOutputFilterByType DEFLATE application/json
</IfModule>
<IfModule mod_substitute.c>
SubstituteMaxLineLength 20M
</IfModule>
So, beside deactivating the plugins, it’s necessary to enable the gzip output compression as mentioned above. And also enable the module mod_substitute on your web host.
Another issue which could cause performance problems on your website is checking for update on some of the plugins. Jet Blog plugin (which is bundled in the Jupiter X for free) is one of them. While it tries to access their own servers to check if it has a new version everytime it tries to load the Elementor, in case the server responds back slowly or there was a blockage from your server to their servers, it will cause a huge delay on loading the Elementor.
Other plugins such as Ultimate packs will also causes slowness. Sometimes, the frameworks inside the plugins such as Cherry framework which is used by Zemez group (the authors of Jet Plugins) causes conflict with other plugins and it leads to a slowness issue while you are loading Elementor.
In some cases, you need to upgrade your PHP version to 7+. Some Elementor plugins will require PHP 7. Although for Jupiter X you need PHP 5.6+, some Elementor elements requires the 7 and more versions to work. Otherwise you will face issues again.
