Why website uptime and speed tests aren’t as important as you think – News Nation USA

Everyone has their own idea of what makes a great web host. Loads of features, powerful servers, or maybe great support, low prices, or maybe some combination of these and other functionality important to the individual.

Some specialist web hosting review websites also place a high weight on their own web hosting benchmarks, though, especially speed and host uptime (the proportion of time a website is available online). That seems like the logical thing to do but does it actually make sense?

There’s nothing wrong with running these tests – indeed we’ve done them ourselves – and the results can feel like valuable information. No-one wants a slow or unreliable website, and anything which highlights a good host, or warns you about a poor one, has to be welcome.

However, you must be careful how you interpret these figures. Although the high-precision results make them look objective, they’re often based on a number of very subjective judgements, and that can significantly affect their reliability. In this article we’ll look at some of the issues you need to think about in this respect.

Understanding the tests

Measuring web host speed and uptime is complicated, with many factors involved. Which servers are checked? Which sites? How often? Is the speed figure a server response time, the ‘time to first byte’ (the time between requesting site content), the time to load a sample site, or something else?

It’s like browsing a chart comparing the 20 top electric cars. The rankings might change radically depending on the test driving style, environment, traffic conditions, weather, temperature and more, and until you understand the details, there’s no way to tell how relevant they might be to you.

When a hosting review presents you with an uptime or speed figure, don’t take it at face value. Read the review in full and look for any explanation of how it’s calculated. If you don’t see anything, look for a ‘How we test’ site-level article with more details.

Just reading the explanation of what’s going on can tell you a lot. Is it clear what’s going on, exactly what’s being checked, how the tests are run? Do you feel there’s enough information that you could carry out the same tests yourself?

If it’s all a little (or extremely) vague, or there’s no explanation at all, that alone makes the figures almost meaningless as you’ve no idea what’s being checked. Most review sites do have a decent explanation of what they’re doing, fortunately, but that can also raise many more issues.

Bitcatcha Sample Speed Test Report

(Image credit: Bitcatcha)

Speed tests

The first question to consider with any web host speed test is what, exactly, is being tested?

We typically benchmark a shared hosting plan, and almost all web hosting review sites do the same. That’s a reasonable starting point, but it doesn’t indicate what sort of performance you’ll see from a host’s managed WordPress plans, VPN or dedicated hosting.

Even if you’re shopping for shared hosting, there are complications. For example, many hosts have multiple levels of shared hosting, where each plan gets a different level of system resources (CPU, RAM and so on). The test designer must decide which level of shared hosting to include in the benchmarks.

The simplest option is to pick the cheapest shared hosting product in any range – but the trouble is, that penalizes providers who offer basic consumer hosting. Provider X may have some of the best high-end hosting products around, for instance, but because it also has a very basic $1 a month starter plan (which should be a plus), it’s likely to drop down the speed test ranks.

A fairer approach is to choose equivalent hosting packages from each provider, so the test compares similar products. But does ‘equivalent’ mean a similar price, or features, or some mix of the two? There’s a lot of subjective judgement involved in figuring that out. And even if the tester somehow comes up with the perfect choice of comparable products, that might all change the very next day if the host updates its feature list or prices.

This doesn’t mean the results have no value at all. If host X tops the current list for baseline shared hosting speeds, and host Y trails behind in a distant last place, then that’s useful information. And it’s certainly better than having no information at all. Just keep in mind that it might not accurately represent the speeds you’ll see with your preferred product.

UptimeRobot.com Speed Chart

(Image credit: UptimeRobot.com)

What is ‘speed’ anyway?

The next benchmarking issue to consider is how the test measures speed. There are two common methods.

The first checks server response time, or how long the server takes to respond to a request. That’s a simple statistic and easy to compare, but it’s mostly about network speed, and doesn’t cover a long list of relevant factors. If your server is short on CPU power, or RAM, or has slow storage devices, for instance, that’s not going to be properly reflected in a response time, as it’s not loading a full website page.

The second option measures the load time for a test site, perhaps a simple WordPress template. That’s an improvement, as it takes account of more performance factors, but it’s still most unlikely to reflect your situation. Your own site is probably very different to the test template, maybe runs on a different CMS, with your own custom plugins, and none of that will be reflected in the test results.

Template-based speed tests are almost always based on a web host’s default setup, too. Does the host automatically enable Cloudflare or some other CDN, say? Is it using the latest and fastest version of PHP, and the most speed-optimized PHP settings?

Doing it this way has some value for first-timers who’ll accept the default settings and never change anything, but it’s not much use for anyone else. If you might integrate a CDN yourself, change your PHP version, or make a single speed tweak, ever, anywhere in your hosting control panel, that could be enough to radically change your host’s test speed ranking.

Picture of the Earth with a web of links over the surface

(Image credit: Shutterstock / NicoElNino)

Location, location, location…

The extra complication with any speed test is figuring out the locations involved. Where in the world is the test site, and where are the servers running the tests? It can make a huge difference.

Many web hosts have several data centers, for instance, and it’s most unlikely that they’ll offer the same performance. If the test site is in Los Angeles, but you’ll choose New Jersey, or London, or Brisbane, or somewhere else, that’s likely to have a significant effect on the results. (Most of the review sites we checked didn’t even mention the issue, so you’re probably not going to find out.)

The best speed tests are typically carried out by an automated service which runs simultaneous performance checks from multiple locations. For example, Bitcatcha runs tests from the US (east and west coasts), London, Singapore, Sao Paolo, Mumbai, Sydney, Japan, Canada and Germany, and gives you a rating based on the overall results.

The advantage of this approach is it allows you to compare web hosts anywhere for their worldwide performance. The problem is that if your site doesn’t have a worldwide audience – most visitors are from your home country, maybe – then the figures you need are for their locations only, and that could give you a very different rating.

As we’ve said above, this doesn’t mean the figures have no value. Any test results are welcome. But don’t take any single speed rating as a cast-iron guaranteed measure of a host’s overall performance – it could take some thought to figure out what the data actually means for you.

HRank.com Reports Website Uptimes

(Image credit: HRank.com)

What is ‘uptime’ anyway?

At first glance, measuring website uptime seems relatively easy. It’s just the amount of time your site is up and running, expressed as a percentage. If a web host gives you 99.9% uptime annually, for instance, that translates to 8 hours 46 minutes of downtime over the year. Simple.

Except, well, it really isn’t. Web hosts often define ‘uptime’ as meaning your server is accessible, not your site. For example, HostGator’s Uptime Guarantee page says: “Just because your website does not work, this does not mean your server has downtime. As long as the server is available to deliver your content, then the guarantee is met.”

Many review and testing sites also focus largely on server availability. For instance, UptimeRobot says it detects downtime by sending HTTP requests to a website, and looking for HTTP status error responses, or no response at all.

The problem is there are many situations where the server might be up and running, but a website is close to unusable. Just think of all the times you’ve seen this. You visit a site but see strange error messages, maybe some features don’t work at all, or speed is so poor you give up and go somewhere else.

Issues like this are arguably the worst you can get. If your site is inaccessible, people might wonder if it’s some ISP or network issue. If they can reach your site, but it doesn’t work, they’re far more likely to blame you. And yet, if your server is available and can return a page – even if it says ‘sorry, we’ve got problems, come back later’ – it’s possible that none of this will be reflected in the uptime figures.

Uptime.com Uptime Report

(Image credit: Uptime.com)

More uptime complications

There are plenty of other potential uptime testing complications. As with the speed tests, for instance, it’s important to understand which servers are included in the benchmarks. If they’re covering a specific product only (the cheapest shared hosting), they won’t necessarily tell you anything at all about the rest of the range.

Uptime checks can sometimes falsely report a site is down, too. This happens often enough that Uptime.com has a FAQ page on the topic, where it lists quite a few potential causes: ‘Most likely candidates include local issues, firewalls, blacklists, timeouts, and load balancer issues.’

These problems may not be common, but they’re still something to consider. The difference between uptimes of 99.99% and 99.98% is only around 18 minutes a year, for instance – if the test checks a site every minute, that represents only 18 misleading fails out of 525,600 tests over a year, or one error for every 29,200 attempts.

None of these issues mean you should ignore uptime and speed results entirely. Even if they’re covering basic shared hosting and you’re after a VPS, say, it’s interesting to see if a provider is racing ahead of the competition, or lagging far behind.

But don’t assume the figures give you a complete and accurate picture, either. They’ll give you a general idea of how the web host performs in some areas, but those may not be the areas most relevant to you, and they certainly don’t give you the full performance story.

What TechRadar advises

Always take uptime and speed tests with a handful of salt. Because they are often the only objective-looking numerical tests that web hosting review sites can perform, they tend to be put in the limelight and placed firmly on a very high pedestal. In our opinion though, they should only be considered as secondary, minor, parameters when choosing which web hosting company to go for and that is reflected in our review process.