Hi there!
In all sites I am currently working on (that is four, all with pro installed), I experience the same problem:
Header & footer builders need a very long time to launch. No plug-ins installed yet, and I have tried safari as well as firefox and chrome - all the same.
Do you know about that already? Any suggestions?
Kind regards,
Malte
Hello,
Thank you for writing in!
Let me know if only the Cornerstone is causing it? Because you can check this article to see some tricks about increase the velocity of your site: https://wpengine.com/blog/site-speed-make-wordpress-lightning-fast/
If the issue persists, provide to us your WP credentials and the website link in a secure note, please.
Header and footer builders need half a minute (and sometimes longer) to launch. I provided the information needed in a secure note. Thank you for your help!
Hello There,
Thanks for sharing login details.
Regarding maltekreutzfeldt.de website I don’t see much of delay in load time. However I noticed that you are running Pro version 1.1.0. We have already released version 1.1.1 which is a maintenance release. We recommend you to please update the theme and then try again on your end. Here is the changelog:
Can you please confirm the URL for Patta where WordPress is installed? I am trying to login/browse website using the url you have shared and few other permutations and combination but I am unable to access the website. Here is the error message I am getting:
Object not found!
The requested URL was not found on this server. If you entered the URL manually please check your spelling and try again.
If you think this is a server error, please contact the webmaster.
Error 404
The hope page http://www.patta-ev.de/ looks like a static website. Kindly confirm the url.
Thanks.
Uh. Stupid me. Sorry. Now the URL is correct (see Note, please).
Hello There,
Thanks for updating in! It seems that you are experiencing PHP memory limit exhaustion. We recommend that you increase your memory allocated to PHP. To increase it, please edit your wp-config.php file and insert these lines:
define( 'WP_MEMORY_LIMIT', '256M' );
define( 'WP_MAX_MEMORY_LIMIT', '512M' );
You can add it before the line
/*That's all, stop editing! Happy Blogging. */
We would loved to know if this has work for you. Thank you.
Hey RueNel, on a sunday … uh, thanx.
On the one hand you were right: Although I already added these line in my wp_config, the system did not change the limit (for what reason ever). So I changed the .htaccess and … boom. Succeeded.
…BUT…
On the other hand, unfortunately, things stay the same: launching header builder took ages.
Any other proposals or ideas?
Would be more than welcome.
m.
Hi there,
The first site has incorrect credentials, I couldn’t check it.
While the second site, there is a 404 error which makes the loading slower ( I fixed it ), then a javascript error, and slow-loading resources from SoundCloud.
Though, the one that makes the loading slower is the endpoint that takes 59 seconds to load. Would you mind providing your FTP login credentials as well? Maybe I could find something from the debug logs.
Thanks!
Iam, glad to hear you found something wrong to work on. I left a secure note with the information needed. Thank you for your help! m.
Hi there @sentifux,
Thanks for providing the additional details much appreciated. Unfortunately nothing particularly useful is being generated by WP_DEBUG.
Do you have the complete server error logs, slow logs and access logs that you could include in a secure note (as links to perhaps a dropbox folder or similar).
That way we can review the logs and see if there’s anything specific, the slow log will be the most helpful as that’ll specifically mention scripts that are taking longer to execute.
Thanks!
Hi Jack, this took me a while … 
No slow_queries log. Sorry. Shared hosting.
… but …
A staff member of my provider (Hosteurope here in Germany) migrated my installation on a fast, local machine to check performance. He experienced the exact same result: 1min for the first launch of header builder.
He checked why. Here is what he wrote:
“Header builder is calling the database and sends it to “sleep” immidiately, for about a minute. Meanwhile, the SQL-database is waiting for data, but the script does not send any. Why the script is connecting to the database and what data is transferred I cannot see or retrieve. Additionally, the script seems to call the database only when launched the first time of a session.”
Isn’t that surprising?
Any ideas?
Thanks!
m.
Hi there,
It’s only normal to have one connection for each session(for each request between browser and server) and upon the page or ajax load. Wordpress keeps the connection open until it finished loading, that way, other functions that needed database transactions are executable while it’s open. Much faster than having one connection for each query, which only means fewer traffics. Plus, we’re not having issues with this kind of setup in any of our installations and it’s Wordpress standard.
Could you try it with fresh installed Wordpress and Pro theme? Try it on another machine (your machine) and see if it’s just because of your existing installation. I can’t find any abnormal activity from your site either. Maybe he tested it on the same hosting environment where the issue is present.
Thanks!
Hello.
Was there ever a resolution to this? I am evaluating switching to the pro version (trying the free one in my account) and running into this issue. Header/Footer builders take a long time to load. Two different sites, one a new install.
Hi there!
No, unfortunately not - launch of header/footer builders take 1 minute.
But what might be helpful to consider is the following: Once you loaded the builder, saving or changing things is normal. The phenomenon only appears each first time when you start working.
@themeco_staff: As my provider figured out, some code is putting the database in sleep mode for 59secs.
This is weird … and still not solved.
Kind regards,
m
Hi there,
May I know which could, maybe I can check that part and test it 
I don’t have this kind of issue in any of my installation, so it must be specific to your host which can be sensitive to that code’s action.
Thanks!
As of Pro Update 1.2.6, this is fixed.
Launching header builder is working perfectly fast.
Thank you, folks. Good job.
m
You’re welcome!