@Rad that is strange. i was working on the site the whole time! i activated the plugins right away after i noticed they had been deactivated. so no worry. but you should be able to log in anytime. i did not chance any credentials. pls s. secure note for a different user.
Hi there,
I used the credentials and spent so much time on your website to find out why this is happening and it is slow while using the header builder. Using the Network tab of my Google Chrome browser I found out that the start of the loading keeps in the pending mode:
That means the server does not respond and waits for a long period of time to respond, as soon as the response is initiated the rest of the code loads blazing fast.
I double checked the case with my 5 local installations, and 3 other live servers. None of them took that much time in pending mode for a load of the cornerstone endpoint.
I am not sure why this is happening on your server but you will need to contact your hosting service provider and ask them to investigate. Maybe there is a security measure of some kind that slows down the connection or something else that I am not aware of.
Please kindly check the exact same website in another temporary server. I am not telling you that you need to change the server, I just say test the case please with another server and compare them. As you mentioned I am sure that your server is fast enough, but it is not a matter of the server being fast, something here is preventing the initial response which my guess it has something to do with a setting or a measure on your server.
Thank you for your understanding.
hi christopher, thanks so much for taking so much time to check the problem out! i am already in contact with the provider but up to now they could not find the reason for the problem. i will contact them again with your information! moving to another server will - i am also very sure of that - solve the loading time problem. i might need to do that anyhow before wasting your and my time on this anymore. thanks again. i appreciate your help a lot! kai
Youâre welcome, Kai,
Let us know how it goes.
Cheers!
here is another reply from the hoster. they think it could be a keep-alive function which cornerstone might depend on. is that correct?
So wie der Support das erklĂ€rt klingt es ganz danach als wĂŒrde Cornerstone zwingend die
keep-alive Funktion benötigen um die Verbindung konstant aufrechtzuerhalten fĂŒr Anfragen. Leider ist diese Option nicht möglich weil diese einen extremen Ressourcenlast aufbaut auf Shared Hostings. Was dennoch merkwĂŒrdig ist, ist das die js Datei erst so spĂ€t abgerufen wird. Ich denke nicht das die Lösung nur keep-alive sein kann. Wenn der Entwickler seine Software optimieren wĂŒrde sollte diese auch auf Servern ohne keep-alive laufen.
machine translation:
As explained by the support, it sounds like Cornerstone is compelling to use the
keep-alive function to maintain a constant connection for requests. Unfortunately, this option is not possible because it has an extreme resource load based on shared hosting. Whatâs strange is that the js file is retrieved so late. I donât think the solution can only be keep-alive. If the developer would optimize his software, it should also run on servers without keep-alive.
Hi there,
Ajax requests depend on Keep-Alive connection, especially for Wordpress that has built-in heartbeat and admin-ajax. So itâs not just about Cornerstone, itâs about all scripts that will utilize Wordpress ajax.
What they are doing is optimizing it and trying to minimize the processing and resources being used. If itâs their rule then I think thereâs nothing we can do about it but move to the different host. Plus, they mentioned that youâre on a shared hosting, and itâs understandable that they should limit your siteâs capability since multiple sites are running on same allocated resources. Shared hosting is usually slow due to limitations, you canât even increase the memory limit.
Please check this https://www.keycdn.com/blog/admin-ajax-php-slow/
Thanks.