How to Recognize a Bad hosting for WordPress


It is very hard to explain which hosting environment is good for WordPress websites, especially if you want to understand why. There are dozen of different setups which can make WordPress fly and run flawlessly.

In simple terms, and the most convenient definition: A good WP hosting will never make you face ridiculous issues, but will allow you to run your back-end tasks without errors or frozen scripts etc.
Bad WP hosting is just the opposite.

Been there, done that!

I’ve used many hosting types through the years. Most of them are chosen and paid by my clients, and most of them are simple Apache cPanel shared hosting setups. It is not always about the speed, it is about the compatibility and ease of use.
Recently, even I suggested differently, a client bought some very cheap hosting. It’s a cPanel hosting running on Apache with mod lsapi. None of the mentioned is important, but what is important is that WordPress doesn’t function properly within environment.
What I found out was that some of the greatest and most popular plugins didn’t work. The PHP settings were quite off and who knows what else.
For example: the super popular and reliable All in One WP migration (5mil active installations) wasn’t able to deploy a website from a backup. The thing would froze after reaching 100% on upload. The sad thing was that even the hosting provider didn’t know how to fix the problem.
Another problem was that I wasn’t able to run any query to extract a database. It means you can’t automatically create a database backup.
The maximum post max size and upload limit are a joke, even for starters. Without this, you can’t even think about auto-backups/redeployment.
After a while they start sending you email notifications how WP is not secure, and you need ”obscurity” tweaks. Some, like Siteground, will start sending you performance issues threatening emails, warning you that you are using too much CPU resources – just because you work in back-end a lot. Considering the price they charge, their limits are ridiculous. Disabling the WP cron will fix the issue, but why would you do that?


Therefore, what is a bad hosting for WP sites?
It’s the one giving you a hard time from the very beginning. You should definitely try backing up and redeploying from backups just to check if these simple, yet very important chores work out fine. If not, RUN away from that hosting.
If above seems fine, the next thing to check is the speed, and if the speed is satisfactory, then the only thing left to check is if your website works properly by using all of it features as a regular visitor.

Thanks for reading.

Leave a reply

Please enter your comment!
Please enter your name here