Cloudways Is The High-Performance WPEngine Alternative

When you're looking for a new hosting plan it can be hard to directly compare providers. To help you out, we recently tested some of our DigitalOcean plans against Kinsta and WPEngine. Just by working out which of our plans to line up against theirs, we saw how hard it can be.

This article takes you through some ways of comparing us to our competition. We hope it will help if you have a few different "Plans and pricing" tabs open right now.

Method #1 for comparing hosting plans: Look at the numbers

Different hosting providers give you different sets of numbers about their plans, but some comparisons are always possible. It's useful to know which figures represent technical specifications, and which ones don't.

Some figures look like technical specifications but aren't

• "Visits per month" isn't a tech spec - it's a pricing bracket. Some providers cap their plans at a particular number of site visits per month. This isn't about server capacity. It's a reason to bump up your bills as you attract traffic, even if your websites are lean and easy for the server to handle. It's not as objective as it sounds, either. Just ask how they count "visits" and you'll see how much of a grey area this is.
  
  
• "Up to X sites (or CMS installations)" isn't a tech spec - it's customer segmentation. You might have one 40GB website or ten 4GB websites. When it comes to storage space, it's all just data. Some hosting plans limit you to a certain number of sites (or WordPress installations) but this is not a technical constraint. Usually, it's a way for hosting providers to segment their customers and charge some of them more. If you're an agency running a large number of client websites, you're the target.
  
  
• "Concurrent visitors" isn't a tech spec, but it is important. How many people can visit your site at one time before it fails? This is important to know, but it depends on a lot of things. How heavy is your website? How much of it is cached for quick access? How hard does your server need to work for each visitor? And what do you mean by "fail"? We'll talk more about this soon.

Technical specifications to look for

Some raw numbers help you to directly compare servers. Look for:

• Terabytes (TB) or gigabytes (GB) of storage. This is the amount of information that your server can hold. It's the space for all your website content, data your site collects (like customer information), and the tech stack that underpins it all (e.g. PHP and WordPress installations). If you get close to this limit, your server can slow down. Look at the units closely, because 1TB = 1,000GB.
  
  
• GB of RAM. This affects how quickly your server can operate. With more RAM, operations are quicker.
• A number of processors or "cores". Every processor can do one thing at a time, so this tells you whether your server can multitask. With one core, every request is queued up and served one by one. A dual-core server works through two queues at the same time, and so on.
  
  
• GB or TB of bandwidth. This is the total amount of data you can send out to the internet in a month. It's not a technical limitation of the server (exceeding it is more likely to cost you money rather than slow your site down), but it's an objective number that you'll see on almost every hosting plan you find. In some cases, bandwidth limits apply to the CDN rather than the server.
  
  

Remember that different providers will share different sets of specifications, so you might not find all the numbers you want. But do use whatever numbers you find to build a picture of each plan.

One number you almost never see

For a lot of people, the biggest question is "how many people will be able to visit my site before my server crashes from the load"? Unfortunately, that's not always an easy one to answer. But heaping on more and more concurrent visitors will eventually lead to failure, which brings us to real-world testing.

Method #2 for comparing hosting plans: Test results

The basic process that we followed for our most recent benchmarking against Kinsta and WPEngine was:

1. Set up servers to test. For our testing, we used servers that weren't receiving any traffic from the outside world and hosted mock websites (including realistically weighted content) running on common tech stacks.
2. Send a calibrated number of requests to the server. From the server's point of view, each request is the equivalent of a person visiting the site.
3. Measure the response time, i.e. how long each 'visitor' waits for the site to load.
4. Increase the number of visitors and keep measuring until you reach the point of failure.

In this case. 'failure' is when the server slows down to the point of frustration. Our test methodology defined failure as an average response time of over 2.5 seconds.

Even you can check out the detailed comparison of WPEngine with Cloudways and learn why Cloudways is the #1 WPEngine alternative in 2021.