[rogerachkar]

I contacted the host (Godaddy) and they assured me that there is no issue from their side. Elementor is not loading on all pages and posts.

[Mehmet S.]

Hi Roger,

Thanks for giving us access. I reproduced the problem on your site and found the cause. It is not the theme or Elementor itself; your server is rejecting requests under load.

What happens:

– When the Elementor editor opens, it sends many requests to the server at the same time.

– Your server answers some of them with “503 Service Unavailable” (a 23-byte Apache error, not generated by WordPress).

– The editor preview frame (yoursite.com/test1/?elementor-preview=13486) was one of the requests that received a 503, so the editor stays on the “Loading” screen forever. The browser console shows the matching error: “Blocked a frame … from accessing a cross-origin frame”.

How I confirmed it:

– 8 parallel requests to /about/: 2 succeeded, 6 returned 503.

– 8 parallel REST API requests: 3 succeeded, 5 returned 503.

– 8 parallel requests to a static CSS file: all succeeded in ~250 ms. So the limit is only on PHP processes, not on the network.

– A single page request succeeds but takes 8 to 14 seconds to generate.

– Even the WordPress Site Health page returns 503 when opened while the editor is loading.

Your hosting is CloudLinux based (cPanel / LVE). This pattern (503 as soon as several PHP requests run at once, static files fine) is the Entry Processes / PHP-FPM worker limit of the hosting account being reached. Please send GoDaddy this information and ask them to:

1. Check the account’s LVE / Resource Usage report (cPanel > Resource Usage) for “Entry Processes” and CPU/IO limit faults during the time you tried to open the editor.

2. Raise the Entry Processes / PHP-FPM max children limit, or move you to a plan that allows more concurrent PHP processes.

3. Enable OPcache for PHP (Site Health reports it is disabled).

Things you can do on your side to make each request much lighter, which will reduce the 503s:

1. Elementor > Settings > Performance > CSS Print Method: set to “External File” (currently “Internal Embedding”, which adds ~117 KB of CSS to every page).

2. Essential Addons is printing all of its CSS inline: 500 KB on the home page and 1.1 MB in the editor preview. In Essential Addons > Tools, regenerate assets and make sure the inline/”Generate assets in the uploads folder” option is set to file mode, or disable the Essential Addons elements you do not use.

3. Reduce active plugins (currently 29). Remove duplicates (Loginizer + Loginizer Pro, FormLayer + FormLayer Pro, Filter Everything + Filter Everything Pro keep only the Pro one), and deactivate setup/import tools you no longer need (One Click Demo Import, WordPress Importer, Extendify, Site Assistant, Search & Replace Everything, Envato Market).

4. Install a page cache plugin (for example LiteSpeed Cache or WP Super Cache) so visitors do not trigger PHP on every page load.

5. Turn off debug mode: in wp-config.php set WP_DEBUG to false (Site Health also flags that errors are displayed to visitors).

Our server requirements are listed here:

https://www.pixelwars.org/forums/topic/system-requirements-for-wordpress-themes/

Your PHP version and memory values already meet them, so the remaining issue is the concurrent process limit, which only the host can change.

Let us know what GoDaddy says and we will be happy to look again.

Best regards,
Mehmet
Pixelwars Support

[rogerachkar]

Thank you.

GoDaddy increased the PHP limits and upgraded the PHP to latest 8.5 version.

Now Elementor is finally loading despite being slow.

[Mehmet S.]

Hi Roger,

Great news, thanks for the update. I re-checked your site from the outside and can confirm the fix:

– 8 and 16 parallel requests now all succeed; yesterday 6 out of 8 returned 503.

– PHP is now 8.5.11. Energi 1.0.2 is PHP 8.5 compatible and I see no PHP warnings in your pages.

– Your pages are also much lighter now: the home page went from 812 KB / 14 s to 194 KB / 2.3 s, and the About page from 411 KB / 8.5 s to 139 KB / 1.9 s. The CSS print method and the Essential Addons inline CSS changes clearly worked.

Why the editor still feels slow: the server no longer rejects requests, but it still processes PHP requests almost one at a time. A single page takes about 2 s, but when 8 requests arrive together each one takes about 14 s. The Elementor editor sends dozens of requests when it opens, so it waits on the server. This is CPU / PHP worker capacity of the hosting plan, not the theme.

What will help most:

1. Ask GoDaddy to confirm OPcache is enabled for PHP 8.5 (WordPress Site Health reported it as disabled) and to tell you how many PHP workers / CPU cores your plan allows. If the editor is still slow after that, a plan with more CPU or a different host is the real fix. Our hosting recommendation is in the requirements topic:

https://www.pixelwars.org/forums/topic/system-requirements-for-wordpress-themes/

2. Install a page cache plugin (for example WP Super Cache or LiteSpeed Cache). Your pages are still generated by PHP on every visit (no cache headers), which keeps the server busy and slows the editor for you too.

3. Keep reducing active plugins. Each plugin runs on every one of the editor’s requests.

4. Turn off WP_DEBUG in wp-config.php if it is still on.

If you want, I can take another look inside the admin once the cache plugin is in place.

Best regards,
Mehmet
Pixelwars Support