header image

Who’s best for WordPress hosting GoDaddy Vs Bluehost

Well – I’d finally had enough of GoDaddy’s incessant time outs which they’d attributed to common run of the mill plugins like JetPack and others.

I’d installed their recommended caching plugins to try and improve page load times and even installed their own proprietary P3 profiler plugin to measure my blog stats but it didn’t tell me anything I already knew, that my tiny wordpress blog was responding like a fly stuck in a jar of honey. Granted I’m on a shared plan and I take it as a given that the page load times won’t be instant on a shared host – but page time out’s and ultra slow load times I will not stand for.

So it was time to up sticks and move to another provider.

My main criteria for moving was that the host have great performance and support for WordPress.

There’s a ton of conflicting advice on the internet about the best WordPress host – believe me, I’ve researched this for a long time so I decided to go with the advice from the horses mouth – WordPress itself, and Bluehost it was. Look they’re right up the top, like the gold winning champ they are and it’s been a huge improvement – the time outs and slow page opening times have been eliminated, even though I’m still using Jetpack, – isn’t that strange GoDaddy?

I’ve also found out the reason GoDaddy’s shared hosting can’t cut the cheese – they don’t throttle down “abusive” users like Bluehost do with their shared hosting users.

My advice – go with Bluehost for your WordPress blog, it’ll save the hair pulling and back pain of transferring your blog from GoDaddy when you realise they’re not up to the task. It was a great learning experience, but not something I’d recommend if you don’t have a technical background.


~ by Martin on March 2, 2013.

Blogging, Troubleshooting

One Response to “Who’s best for WordPress hosting GoDaddy Vs Bluehost”

  1. … [Trackback]

    […] Read More: martinbirrane.com/whos-best-for-wordpress-hosting-godaddy-vs-bluehost/ […]

Leave a Reply

%d bloggers like this: