The Problem with the Reviewer-Hosting RelationshipYou see, any website that reviews hosting services (actually, reviews anything) makes money from doing so. Hosting companies are always searching for new clients, and they pay an affiliate commission for every new client that clicks a link in a review. This is a pretty good idea at its core, one where everybody should benefit: the reviewer gets rewarded for finding an awesome service, the user enjoys it, and the company grows and gets better. Small problem. It doesn’t take human nature into account. What many people discovered is that it’s much more profitable to just hand-pick the web hosts that provide the best affiliate deals, and write a rave review detailing the endless joy these hosts brought into their life. The amazing loading speeds their site visitors enjoy. The fact that it’s never had any downtime. And they’ve been testing! Well, have they been testing? Usually, not at all. It’s too easy to get super-technical with the terminology, make up some numbers (or just copy them from the web host’s homepage), and wrap it up in a convincing way. If you’ve ever seen the notorious Bluehost on a “best services” list, you can be positively sure that it paid its way into it. The people behind “testing” websites like this are basically scammers. They lie to your face and run away with the money. The only good news is that while they make up the majority of online hosting reviews, they’re easy to spot once you realize that they’re not backed by any data. But even data can lie. Which brings us to the second type of performance test offenders.
Why Sometimes Even Data Can’t Be TrustedDue to the rising demand for honest, unbiased web hosting performance tests, a new type of testing website arose. One that collects every bit of possible data, runs a dozen different types of tests, and really monitors each web host’s performance for months. Sounds amazing, right? It really is. We do this too, and are very proud of our work. But some other websites were so hungry for data, they signed a deal with the devil. Let me explain. After setting up a hosting plan with one of the vendors, installing website software (usually WordPress), and connecting to a domain, the site becomes accessible online. In evaluating an online website’s performance, we’d like to know many things: How fast does it load? How fast does it load from different parts of the world? How powerful is the plan, and how many resources does the website have available? What is the website’s uptime? And… How does the website perform under high loads, when many visitors are requesting it at the same time? Now, this last question is where the overreaching begins, and where the testing websites break your trust. Not because it’s not an important question (on the contrary, it definitely is), but because testing it is much more problematic. This type of performance test (usually called a stress test or a load test) is done by sending multiple requests to the server asking for the hosted website. It’s meant to simulate situations where multiple users (hundreds, thousands, even more…) are trying to access your website at once, and to give you an idea of how your website performs under pressure. But trying to run a stress test on a shared hosting plan doesn’t work. Ever heard of a DDoS (distributed denial-of-service) attack? It’s an attack where multiple requests are made to a server in an attempt to overload it and bring it offline. Quite similar to a stress test… only a tad more malevolent. To protect their users from such attacks, almost all web hosts today have powerful DDoS defenses in place. If the server senses that an unusually large number of requests is coming through, it’ll simply block and deny them, shutting down the attempt. So how can these testing websites stress-test the hosts without triggering the defense? They can’t. They have to contact the hosts and ask for all security measures to be removed. But by doing this, they reveal who they are to the hosts, and from this point on, the data they collect is meaningless. Once you’ve explained to the web host what you’re trying to do, you might as well go home. There’s no validity to your results anymore. The web host knows what’s going on, and it has an incentive to play around with the results. Even if it doesn’t manipulate the server setup, the host can’t let anybody run stress tests on a populated shared server – if the server crashes, thousands of paying users can suffer downtime. The only way for a host to let you run a load test without risking the other shared accounts would be to give you an empty server. Are results drawn from testing an empty server relevant to your actual user experience? Nope. Can you trust any data that was produced by revealing that you’re a tester? Definitely not. Every time you see a beautiful graph or an informative table detailing a shared plan’s performance under a stress test, you can be sure the host was involved in the process. That the tester and the testee were in cahoots. That’s reason enough to ignore this data completely. Now, these testing websites say that they have “good faith” in the hosts… that they trust them to play fair. Seriously? How can you have good faith in anybody shelling out 200% affiliate deals for their products? Do not fall for these reviews. Learn to spot the warning signs and don’t get fooled!
The Correct Way to Do ItWas I harsh up until now? Maybe. A teeny bit. But honestly, folks, there’s a good reason for that. I’ve been in the industry for a while, and I’ve seen all kinds of ”tests” and “checks” and promises and whatnot. It looks convincing, but in the end, it’s just more of the same. And it’s your website that ends up being slow, unreliable, and unresponsive. That’s why here at Website Planet, we do things differently. We never, ever, ever, reveal who we are to the web hosts. We always maintain complete secrecy, posing as regular Joes and Janes just trying to get a website up. This is the only way to gather accurate data that is relevant to real users. Our testing process isn’t complicated. It doesn’t have to be. We simply test everything we can test, striving to emulate the experience a normal user would have. We also test more than just performance. We test the support – the actual support experience, the features that are provided, how easy to use is the service, and what value you get for your money. Regarding the server performance tests, this is how we do it. We sign up for the basic shared hosting plan the web host offers. In the few cases where the basic plan can’t handle a WordPress website, we sign up for the first plan that can. Using the hosting control panel and any automatic installation tools provided by the host, we install WordPress. We then upload our customized landing page, The Autonomous Shoes. What are autonomous shoes? Who knows. But it’s a complete landing page that we’ve designed to mirror a real website as closely as possible. It has HD images, cool scrolling effects, some blog posts, and a lot of text content.
After we get our website online, we contact support with a simple question – “My website is slow. Can you help me optimize it?” The reason we do this is to give the web host a chance to show their expertise, and to point us at any handy tool that can help improve speeds. This can be a caching plugin, a CDN, an image optimizer, or whatnot.
We follow the web host’s advice, as long as it’s simple to implement. Our thinking is that we’re not going to do anything that a new user wouldn’t be able to do.
Now that our website is live and optimized to some degree, we start running performance tests. These include the UptimeRobot uptime monitor, a GTmetrix speed loading and optimization test, the Sucuri Load Time Tester tool, and local tests performed on are own testing servers.
Let’s go into greater detail.
Many other testing websites only test a bare WordPress theme, with no images or actual functionality. This is silly, because your website isn’t going to be anything like that. The results we get actually give you a good idea of how your real website will perform.