Okay, here comes the interesting part. This is the trigger point that makes me want to leave Just Host shared web hosting as soon as possible. Unprofessional Just Host live chat support.
Just Host live chat support sucks
I hate people ended my chat conversation when I am not done yet. This is so unprofessional. Furthermore, Just Host live chat support is slow to response. And does not willing to provide help on the spot. Then, what is the purpose of having live chat support?
In the end, I sent an email request to Just Host support. Can’t the live chat support agent helps to escalate it? Err…
Yes, Just Host database server sucks. Why? I am a WordPress user for more than 4 years. I faced “WordPress database error Can’t create/write to file ‘/tmp/#sql_39d0_1.MYI’ (Errcode: 28)” for the first time when using Just Host shared web hosting. What is error 28 meant? Based on Linux, error 28 == no space left on device. Come on, this is what Just Host called ~ Unlimited GB’s of Space??? Does Just Host support team do their job by monitoring server disk space? I doubt that.
The outcome after getting this error 28. WordPress categories and tags are gone. And even worst sometimes, all the posts are gone because database server cannot write anymore on the tmp folder. So basically, your blog are down for good. How frequent do I get this? Once in a week if I am lucky. Else even worst ~ daily…
By the way, you will get this kind of error when all the post are gone ~ “WordPress database error Table ‘./YourBlog/wp_posts’ is marked as crashed and last (automatic?) repair failed for query SELECT wp_posts.* FROM wp_posts…”
Back to Just Host sucks series ~ Just Host web hosting sucks. Yes, I did lot of website optimization to improve the loading speed. And tested PrettyGirl2u.com on CloudFlare CDN service too. Found out that PrettyGirl2u did not perform well when overloaded with sudden high traffic (with multiple benchmarks from WebPagetest servers at the same time). At first, I suspected CloudFlare was causing the slowdown issue. But I was wrong in the end…
Just Host web hosting sucks
Lot of tests were performed after disabled CloudFlare service (test result). So just direct load from Just Host with W3 Total Cache WordPress plugin enabled. Just Host web hosting cannot even handle the traffic by just loading the static page with W3 Total Cache’s help. More than 8 seconds are needed to start loading the page. Some tests took even longer time ~ 17 seconds. I wonder how many visitors can stay that long…? By the way, I did the same test on HostMonster and HostGator too. Both of them passed with flying colours…
Are you still going to use Just Host web hosting with this kind of performance?
Err… I am not an easy angry person. I won’t post it at blog if someone just made me angry 1 or 2 times purposely. But more than that? I am sorry, I can’t keep it to myself because I need to warm other from falling into my situation.
Thanks to “top web hosting” Google search result. I found this ‘wonderful’ Just Host shared web hosting company. Just Host must pay quite some money to get into top 10 listing. Or does it deserve to be on that list? NO is my answer. Why? Just Host web hosting suck. Just Host database server sucks. Just Host live chat support sucks. Just Host domain management tool sucks. Just Host cancellation team sucks. Just Host refund team sucks…
Stay with me. I will post why Just Host sucks one by one. In short, stay away from JustHost.com web hosting!!!
P/S – posting this might get some traffic from search engine as people love to search the word ~ suck.
Posted by Jayce Ooi as Blogging tips
Most of our WordPress blogs are hosted on Linux Apache server. And there is a guide to speed up your website with Apache .htaccess file tweaks. Saw this one at AllGure.NET for quite some times but did not implement it until now. By the way, this is one of the W3 Total Cache feature ~ “Instant” second page views (browser caching after first page view). But too bad, I enabled it on W3 Total Cache and failed to work. So I stick with AllGure.NET guide, and work like a charm.
“Instant” second page view
If you did not implement it, you will see lot of not modified 304 status codes responded by your web server. You are wasting server CPU resources and user time as browser actually makes a request to web server to request for those files which are not modified. And they should be cached at browser level. So no addition requests to web server. Here are the examples using WebPagetest before and after.
How to speed up WordPress blog with Apache .htaccess?
# Turn on Expires and set default expires to 3 month
ExpiresByType image/x-icon A14515200
# Set up caching on media files for 1 month
# Set up caching on commonly updated files 1 month
# gzip compression