Choosing a Web Host - Warning Signs of a Bad Provider
April 9, 2007 | Comments (7) | Filed under: Hosting
In the last 5 years or so, I’ve had the opportunity to test out A LOT of different web hosting companies. While I’d love to tell you that this is because of my insatiable lust for knowledge, the reality is that I just never seem to be able to find one that’s right. I think the biggest issue I’ve had to deal with is that some hosts seem great in the beginning, but really start to degrade their service over time. This makes it almost impossible to judge a host without giving it a test run, kind of like an old Volkswagen Rabbit. You never know what you’ll get till you put your foot on the gas…
I’ve done my fair share of provider hopping. All told, I have switched from 10 different web hosts for a variety of reasons. I won’t specifically list which companies (you can send me a message if you want to know) but my problems have run the gauntlet from horrible amounts of downtime to shoddy customer service. One thing I’ve learned, though, is some of the signs of a bad host. Hopefully my pain becomes your gain and I can help you avoid your own run ins with bad hosts…
Before Signing Up
- Look for a community around the site. Things like regularly updated blogs and web forums are good indicators that the host has nothing to hide. You’ll find a lot of sites will avoid these tools to prevent other users from alerting you to problems.
- Find out what happens if you want to leave in the middle of a paid month outside your trial period. If the host offers anything other than a partial refund for time unused and immediate cancellation, then you need to take a step back. Many web hosts that know their service is bad, implement plans that ensure they milk you out of those last few bucks before you go.
- Check the hosting packages. If they seem too good to be true, then most likely the company is saving money by overloading servers and hurting everyone who hosts with them. Reasonable sites have reasonable packages.
- Look into the servers and backbone the hosting company uses. Quite a few webhosts simply load their servers on another companies backbone and then sell packages to you as if they ran it themselves. While this is not bad in and of itself, you might want to research the REAL company hosting your sites.
- Look into the companies policy on requests to transfer to another server. Sometimes bad luck can hit you and you get hosted on a server with another site whose traffic starts to take off (thus slowing down yours). If you ask your webhost for a transfer to a less populated server, what will they say? Most good hosts will accommodate the request if they can, no questions asked…
- Look at the extra features they provide to you. If a web host charges you extra for services such as SSH and FTP you need to be careful. While obviously there are limits (especially on number of users) basic access to these tools is free for them to setup and takes seconds to configure and maintain. Charging you a regular fee just for convenience in accessing your site over SSH is a sign of a greedy webhost and one who is most likely also overloading servers to save a buck.
- Find out when and why you can contact technical support. All decent hosts should have 24/7 support and respond within minutes of a problem. You don’t necessarily require phone support, online chat and forums work too, but having real people there to solve your problems shows an extra level of commitment. Having no people to answer your problems, only answering machines, is another problem altogether.
- Check for a guarantee on number of sites per server. Some hosting companies will let you know specifically how many sites they will allow per server. This is a sign of commitment to upgrading their system as required to stay on top of their own growth. It’s one thing to say it though and another to actually do it. Look for news items indicating addition of new servers to their infrastructure.
After Signing Up
- Check your site at all hours of the day, especially peak ones, for the first few weeks. Peak downtimes can indicate overloaded servers or underpowered equipment while off peak downtimes can indicate that you might be sharing your server with regular spammers or at least traffic guzzling neighbor sites.
- Watch out for intermittent database drops. You’d be surprised how many webhosting providers are unaware of how to configure MySQL or PostgreSQL to support a large number of databases and users. If your site is staying up, but you are losing connections to your database once in a while, this is a good indicator that either the server is overloaded or the provider does not have the skill set to administrate your database properly.
- Look into the speed of the hosting tools your host provides you. I signed up with a host once that had site management tools that were so slow they timed out all the time when using them. If your host can’t make it painless for you to upload your site, your real pain is just around the corner.
- Related to the previous point, check your site speed against the speed of the web hosts own site. Obviously their site will be on a more dedicated setup, but your performance should be somewhat similar to theirs. If your host has a site that is lightning fast but your plain HelloWorld HTML page is taking 60 seconds to load, then there is definitely an issue. If the webhost itself is not hosting on the same backbone and same equipment, how can you trust it to work for you?
A lot of these points are guidelines, and you have to use your own common sense to decide whether or not you have a warning sign. Currently, Bookmark Bliss hosts all our sites with Site5. As of right now, I have been pretty happy with their service. Will that hold up? Time will tell I guess. Finding a good web host can be a painfully long process. Whenever you can, talk to others and take advice from them. A lot of hosts play some really dirty games and getting some recommendations can save you a lot of headaches in the long run.
feel free to leave a comment
Comment Guidelines: Basic XHTML is allowed (a href, strong, em, code). All line breaks and paragraphs are automatically generated. Off-topic or inappropriate comments will be edited or deleted. Email addresses will never be published. Keep it PG-13 people!
XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>
All fields marked with " * " are required.



7 people have left comments
Hey, what a pitty! I have just bought a new hosting for my website… I’m always too late
Useful post anyway!
Thanks
Stark, these are great tips! Another way of researching hosting companies is getting on some web hosting information forums and check out what the others say about certain companies.
Glad you guys found the tips useful. You wouldn’t believe how many bad hosts I’ve been with. With one host, *cough*midphase*cough*, my site would go down every day at exactly 1:15pm and would stay down for 15 minutes. We used to joke that it was probably the time the spammers flipped the on switch to send out their viagara ads….
Maybe that wasn’t far from the truth
finding a good webhost is hard job.. i chose 1and1 but they didn’t welcome customers outside of US and canada so my next option was Godaddy.
Sometimes luck play a great deal went it comes to a host.
I’ve had an expensive host that repeatedly broke down in the middle of the week without even sending me as notice that something went wrong.
I also had a cheap hosting package that is around $10 a year that has stood the test of time better that the above web hosting company.
Anyway, to hem acharya, I had been a GoDaddy customer before.
And I don’t recommend their service.
You’re better off finding other web hosting company that gives you more freedom over your account. The GoDaddy panels are too restrictive, confusing and slow.
I agree with that as well. I worked for a client one time who used godaddy, and I found their tools to be very poor. The client received very poor service as well (laggy site, constant disconnects) and GoDaddy was very restrictive and inflexible with their configurations.
For example, my client wanted to use the Drupal CMS to power his site, but was unable to get GoDaddy to give his account enough permissions on the database to actually run it correctly…