Hello Guys, Welcome to Hosting Lovers!
If you are planning to buy ScalaHosting Cloud VPS hosting, and you want to know the performance of ScalaHosting Cloud VPS hosting, then you are in the right place. In this blog post, We will test the speed and performance of ScalaHosting Cloud VPS hosting with 10+ different and extensive tests.
Let’s Get Started!
ScalaHosting Cloud VPS Hosting
Sclahosting was started in 2007. Currently, Scalahosting has hosted 7,00,000+ websites and gained 50,000+ customers. Scalahosting is known beacuse of it’s affordable pricing and expert and fast support. Scalahosting provides Shared hosting and Cloud hosting.
In this blog post, we will talk about Scalahosting Cloud VPS hosting plans. In Cloud plans of Scalahosting, we can choose Scalahosting servers, Digitalocean servers and Amazon Web Service servers. Specially, Scalahosting and AWS servers are very affordable. But Digitalocean servers are little overpriced if you compare it with CloudWays.
Plans & Pricing
In this testing, I chose start plan from Scalahosting servers. You can also start with the start plan, because later you can scale it easily. With the start plan, you will get 1 CPU core and 2 GB RAM server with 50GB SSD storage in just 10$ for first 36 months.
To test ScalaHosting Cloud VPS hosting speed and performance, I bought a plan. If you are a regular reader of this blog, you will already know that I create the same testing website when I perform speed tests. After buying the plan, I installed WordPress and connected it with my domain which I bought from NameCheap.
In the ScalaHosting Cloud VPS, you will get apache servers default. But, You can create a support ticket, and the ScalaHosting support team will help you install OpenLiteSpeed (free) or LiteSpeed (paid) servers. So, I asked them to install a free LiteSpeed server on my plan. Because LiteSpeed is way better than apache servers.
I do not want to run tests on a blank website, so I installed Blocksy Theme and one of its demo websites called ‘Tasty.’ I have to install four additional extra plugins with the demo website: Blocksy Companion, WP Forms Lite, Stackable, Recipe Card Blocks by WPZOOM.
Hosting: ScalaHosting Cloud VPS (Scalahosting servers)
Server Location: Dallas, USA
WordPress Version: 5.8
Themes: Blocksy (Active), Twenty twenty One
Plugins: Blocksy Companion, WP Forms Lite, Stackable, Recipe Card Blocks by WPZOOM
After setting this testing environment, I did not perform any extra optimizations like caching, Image compressing, modification, or any other kind of speed improvement. It would be best if you always did these optimizations to improve your website, but I wanted to know the actual performance of ScalaHosting Cloud VPS hosting without any optimizations.
I want to inform you guys that all the results are honest and authentic in this blog post. To do these kinds of tests, I have to spend a lot of money from my pocket, So I would like to request that if you want to buy ScalaHosting or any other hosting, please use our affiliate links. You will get an extra discount, and this website will earn a small amount of commission from it. So, we can do more feature speed tests, reviews, and comparisons without any sponsors.
Now, without wasting your precious time, let’s start testing.
TTFB stands for time to first byte. To put it simply, this is a measurement of how long the browser has to wait before receiving its first byte of data from the server. The longer it takes to get that data, the longer it takes to display your page.
TTFB depends on the Hosting server, Themes, and plugins. But most of the part is played by the hosting server. If hosting using a high-performance server, you will get low TTFB, and if hosting uses a standard specifications server, it will be high.
Most of the hosting stores your website files in a single location. From that server, the hosting will send all the files to the visitors. If your hosting server is located in the USA, your website will get very low TTFB in the USA, Canada, and European countries. But it will be much higher in Asia and Australia.
Therefore when you buy hosting from any of the providers, try to choose the nearest server location from your website’s audience. (not closest to you but closest to your website users)
When visitors come to your website, the browser will send all the requests and ask for the required files to the hosting server. After that, hosting will send an initial reply to the browser. Now, the time between browser requests and hosting initial response will be called TTFB.
Your website will load fast if your hosting TTFB is low. Means, as low is the TTFB of your website, visitor have to wait for less. By this, the bounce rate of your website can decrease drastically.
TTFB can be different from location to location and time to time. Therefore, we will do multiple tests from multiple worldwide locations. So, we can get the best accurate value. In the TTFB test, we will use three different tools and will take five different results.
KeyCDN TTFB Test
TTFB test one is done from KeyCDN Tools. This tool will measure the TTFB from 10 different worldwide locations. I have taken three different results of this test from different other days.
|Server Location||Test 1||Test 2||Test 3|
|Frankfurt||456 ms||582 ms||586 ms|
|Amsterdam||428 ms||425 ms||428 ms|
|London||396 ms||423 ms||423 ms|
|New York||191 ms||217 ms||208 ms|
|Dallas||84 ms||115 ms||92 ms|
|San Francisco||211 ms||215 ms||210 ms|
|Singapore||741 ms||752 ms||736 ms|
|Sydney||683 ms||666 ms||675 ms|
|Tokyo||546 ms||523 ms||529 ms|
|Bangalore||816 ms||819 ms||877 ms|
|Global Average||455 ms||473 ms||476 ms|
GT Metrix TTFB Test
TTFB test two is done from GTMetrix. I have done seven different tests to measure the TTFB from seven different locations.
|Vancouver, Canada||537 ms|
|Hong Kong, China||1.1 s|
|London, UK||604 ms|
|Mumbai, India||1.3 s|
|San Antonio, TX, USA||154 ms|
|Sydney, Australia||1.1 s|
|São Paulo, Brazil||546 ms|
|Global Average||763 ms|
Fast or Slow TTFB Test
TTFB test three is done from Fast or Slow. Fast or Slow will measure the website TTFB and Speed from 18 worldwide locations. This is the heaviest test from all of the tests.
|S Africa||2569 ms|
|S Korea||1911 ms|
|Hong Kong||3052 ms|
|USA (VA)||1598 ms|
|USA (OH)||2083 ms|
|USA (OR)||2492 ms|
Here is the end of the TTFB tests, now we will start the Speed Test.
We will measure the website’s fully loaded time and some core web vitals in the Speed test. The website’s fully loaded time and core web vitals can depend on Hosting servers, Themes, Plugins, and testing page content. But, as I told you before, We used the same testing environment to avoid the Theme, Plugins, and testing page content.
If you want to rank higher in Google search, you should strictly follow the Google Core web vitals. You can measure these parameters from the Google PageSpeed Insights tool, which is the official testing tool of Google.
Therefore, we will do our first speed test in Google PageSpeed Insights. Speed Index and Time to Interactive are parameters we should follow. Google PageSpeed Insights results are not consistent. Therefore, I will conduct three different tests on separate days to get the most accurate results.
|Metrics||Test 1||Test 2||Test 3||Average|
|Time to Interactive||4.8 s||4.7 s||4.8 s||4.8 s|
|Speed Index||3.3 s||4.1 s||2.8 s||3.4 s|
|Metrics||Test 1||Test 2||Test 3||Average|
|Time to Interactive||0.7 s||0.7 s||1.2 s||0.8 s|
|Speed Index||1.5 s||1.8 s||1.1 s||1.4 s|
The second speed test is done with Pingdom from seven different worldwide locations. Load time is the factor that we will consider in this test.
|Server Location||Load Time|
|Tokyo – Japan||2.47 s|
|Frankfurt – Germany||2.46 s|
|London – UK||1.87 s|
|Washington D.C. – USA||854 ms|
|San Francisco – USA||1.11 s|
|Sydney – Australia||3.05 s|
|São Paulo – Brazil||3.49 s|
|Global Average||2.18 s|
The third speed test is done with the GTMetrix tool from seven different worldwide locations. GTMetrix is based on Google PageSpeed Insights. You should look up to Fully Loaded time. I have taken seven different tests from all of the seven locations of GTMetrix. At last, you will see the global average results.
|Server Location||Performance||Speed Index||Fully Loaded Time|
|Vancouver, Canada||94%||1.1 s||1.3 s|
|Hong Kong, China||76%||1.9 s||2.6 s|
|London, UK||81%||1.5 s||3.1 s|
|Mumbai, India||61%||2.5 s||3.3 s|
|San Antonio, TX, USA||98%||774 ms||1.0 s|
|Sydney, Australia||64%||2.4 s||2.9 s|
|São Paulo, Brazil||89%||1.3 s||1.7 s|
|Global Average||80%||1.6 s||2.2 s|
KeyCDN Speed Test
The fourth speed test is done with KeyCDN Tools. There are ten different worldwide locations in the KeyCDN Testing tool. We can measure the website load time, page size, requests, and performance grade with this tool. Page size, requests, and performance grade will be quite the same in all of the tests.
|Server Location||Load Time|
|New York||1.29 s|
|San Francisco||1.51 s|
|Global Average||1.99 S|
Fast or Slow Speed Test
Test 5 is done with Fast or Slow from 18 different worldwide locations. In these results, we measure website interactive time. The Time to Interactive (TTI) metric measures how long it takes a page to become interactive to the site visitor.
|S Africa||4539 ms|
|S Korea||3171 ms|
|Hong Kong||4484 ms|
|USA (VA)||2333 ms|
|USA (OH)||2697 ms|
|USA (OR)||3444 ms|
Good Uptime is one of the most required features in any hosting. If your website stays down most of the time, then it is so obvious that your website will lose all of the readers of all of the customers. Most of the hostings claim 99.9% uptime. That means the chances are your website will be down for 43m 49s in a month. Which is average in all of the hostings.
The reason for downtime can be server maintenance, server technical issues, server upgrading process or it could be any technical issues or also any natural issues like electricity, fire, or anything else. So, we can assume some minor level of downtime in most of the hostings. But, sometimes some of the hostings load too many websites on a single server, or technical issues can cause extra downtime to the website.
I think now you can now understand the importance of Uptime. Therefore I measured the uptime of ScalaHosting Cloud VPS Hosting every 1 minute.
In the Load test, we will send some visitors to the testing website, and after the test, we can see the load handling performance of the hosting. To do the load test, I conducted two different tests. In the first test, I sent 100 virtual users to the website. In the second test, I send 250 virtual users to the testing website.
|Response Times||100 Visits/Minute||250 Visits/Minute|
|Average||267 ms||708 ms|
|Minimum||249 ms||286 ms|
|Maximum||463 ms||1376 ms|
WP Performance Test
These tests are done by WordPress Performance Testing Plugins.
|Queries Per Second||616.52|
|Execution Time (seconds)||1.622|
- Global Average TTFB: 468 ms
- Global Average Load Time: 1.99 s
Overall, ScalaHosting Cloud VPS can be good for you if you are finding Cloud VPS instead of shared hosting. ScalaHosting Cloud VPS can be good choice for you if you want cloud hosting in affordable pricing, Fast control panel, blazing fast and expert live chat support, unlimited free migrations and scalable hosting.
If you like this blog post, please share this article. If you have any suggestions, doubts, or queries, please let me know in the comment section. I will reply to you as soon as possible. If I have made any mistakes, please let me know.
If you want to know more about Hosting Honest Reviews, Extensive Speed tests, Comparisons, and tutorials, then bookmark this website.