Support

Ah, the infamous NoDaddy support strikes again with a reply that BOFH would be envious of. Here's one support reply that makes no sense whatsoever: "the problem is with the sites showing latency to check coding optimization and database closing". For someone who actually understands what we're talking about, this is nothing but a big hot pile of cow manure. First indication it's nonsense: if a site could "check coding optimisation" it would be able to rewrite its own code to optimise it! Sadly, in this Universe, there is no such thing as a site which can rewrite and optimise its code. Maybe the support guy watched Terminator 2 one too many times as a kid or was trying to be funny. Second indication: "latency in database closing". This is a polite way of saying "your site is actually trying to do something which takes some time". I will comment on that in a few. Bear with me.

So, what's a 503 error? Normally it means "this server's broken, we'll be back in a few". But it's a code usually abused, so let me put it in layman's terms. It simply means that the web server can't cope with the request for internal reasons. What can this reasons be? Back in the old days it used to be bandwidth, i.e. how much data has been moved by your site this month. Clearly, that's not the case here. So we have to go with the second suspect. Usually cheap, low quality servers impose resource usage restrictions, for example CPU usage restrictions. When anything tries to run longer than an arbitrarily small amount of time it triggers 503 errors. In short, these errors are caused because you are attempting to host a resource-intensive site on a very bad host. You'd have the same problem if you didn't use Akeeba Backup and simply reconstructed this site on GoDaddy from scratch.

My suggestion: a. change hosts or b. put your site on a strict diet (uninstall as many components, plugins and modules as possible). Speaking of which, if I were you, I'd change hosts a.s.a.p. GoDaddy is commonly referred to as NoDaddy among Internet professionals. If you want to see what the performance difference can be, try loading a stock (default installation) Joomla! site on GoDaddy and on the Joomla! Demo platform (which is in fact a free trial of the cheapest CloudAccess.net hosting plan). The difference is not just huge, it's quantum. That's a huge difference. So you have to weigh what matters most to you: saving a few bucks per month and get hosted on a dead slow server which requires you to remove as much content from your site as possible to even have it run or pay a little extra and get a speedy site which will also make it fare much better in search engines (which do take site speed into account)? It's ultimately your site and your choice.