How to choose the best VPS hosting for Wordpress sites?

Mihai B.

Well-known member
Registered
Joined
Apr 19, 2016
Messages
238
Points
18
Currently many websites selected Wordpress for their foundation by it has many plugins, good themes, easy to use and consistent with a lot of different needs. However, WordPress is a CMS which have a separate operation hence to choose VPS hosting for the WordPress site is very an important task because it will influence the speed of the website. I would like to know on how choose the best VPS hosting for Wordpress sites

Your comments would be appreciated!
 

MooseLucifer

Well-known member
Registered
Joined
May 20, 2016
Messages
149
Points
28
Hey Mihai,

Most of VPS host can run Wordpress site with good performance, the task for that is very easy, you need to configure your VPS correctly to have the best performance. But
In the process of working with WordPress, I realized something very important greatly affected the performance of websites that using WordPress cms. That is Wordpress is often query API to retrieve information on WordPress.org about updates for their new themes and plugins. Therefore the connected line to wordpress.org is extremely important influence WordPress site speed, especially WordPress admin page and we can use this factor to check if our VPS is working as well with Wordpress or not.

Choosing VPS that suitable to WordPress

Use Ping to test the quality of VPS network. Response time of the network is very important in this case, so we will use the Ping command to test the response time of the server to WordPress.org (including wordpress.org and api.wordpress. org)

Code:
ping -c 100 wordpress.org
ping -c 100 api.wordpress.org
I used 100 times and the result is pretty correct
and my results on a VPS is as following

The result of Ping to wordpress.org

Code:
[root@server ~]# ping -c 10 wordpress.org
PING wordpress.org (66.155.40.250) 56(84) bytes of data.
64 bytes from 66.155.40.250: icmp_seq=1 ttl=55 time=85.0 ms
64 bytes from 66.155.40.250: icmp_seq=2 ttl=55 time=84.9 ms
64 bytes from 66.155.40.250: icmp_seq=3 ttl=55 time=85.0 ms
64 bytes from 66.155.40.250: icmp_seq=4 ttl=55 time=85.0 ms
64 bytes from 66.155.40.250: icmp_seq=5 ttl=55 time=85.0 ms
64 bytes from 66.155.40.250: icmp_seq=6 ttl=55 time=85.0 ms
64 bytes from 66.155.40.250: icmp_seq=7 ttl=55 time=85.0 ms
64 bytes from 66.155.40.250: icmp_seq=8 ttl=55 time=85.0 ms
64 bytes from 66.155.40.250: icmp_seq=9 ttl=55 time=85.0 ms
64 bytes from 66.155.40.250: icmp_seq=10 ttl=55 time=85.0 ms
...........................
--- wordpress.org ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9096ms
rtt min/avg/max/mdev = 84.990/85.028/85.067/0.186 ms
In the parameters above, then you are most interested in the following parameters:

packet loss : let you know how many % ping times failed, this number more high more bad VPS network you get.

rtt min/avg/max/mdev you need to concentrate on the value of avg and mdev, if 85.028 and 0.186 ms is more small you get better speed of your VPS.

The result of Ping to api.wordpress.org

Code:
[root@server ~]# ping -c 10 api.wordpress.org
PING api.wordpress.org (66.155.40.188) 56(84) bytes of data.
64 bytes from 66.155.40.188: icmp_seq=1 ttl=55 time=87.0 ms
64 bytes from 66.155.40.188: icmp_seq=2 ttl=55 time=87.3 ms
64 bytes from 66.155.40.188: icmp_seq=3 ttl=55 time=87.1 ms
64 bytes from 66.155.40.188: icmp_seq=4 ttl=55 time=87.1 ms
64 bytes from 66.155.40.188: icmp_seq=5 ttl=55 time=87.2 ms
64 bytes from 66.155.40.188: icmp_seq=6 ttl=55 time=87.2 ms
64 bytes from 66.155.40.188: icmp_seq=7 ttl=55 time=87.2 ms
64 bytes from 66.155.40.188: icmp_seq=8 ttl=55 time=87.0 ms
64 bytes from 66.155.40.188: icmp_seq=9 ttl=55 time=87.1 ms
64 bytes from 66.155.40.188: icmp_seq=10 ttl=55 time=87.0 ms

--- api.wordpress.org ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9101ms
rtt min/avg/max/mdev = 87.069/87.160/87.305/0.241 ms
You can change 100 to your number for how many times you want to ping to wordpress.org

If possible, let us know what is your result when Ping to Wordpress site from your VPS.

Hope it helps!
 

VirtuBox

Well-known member
Registered
Joined
May 3, 2016
Messages
1,622
Points
83
A good VPS for web hosting will be a good vps for WordPress.
Like any other php/mysql CMS WordPress need memory to make more cache and if you have a lot of traffic, php will use cpu
So SSD and RAM are needed, having 2 core could be good to run morn php process but if you are going to run a single WordPress site , a good server setup with a light web server will have more impact on loading speed than the vps choice.
For example , with a small vps (1vCore / 2GB RAM / 10GB SSD) , I'm running WordPress faster than using a dedicated with a control panel.
 

fwh

Administrator
Staff Member
Joined
Dec 8, 2012
Messages
773
Points
63
Insteresting answer @Moose and I also agree with VirtuBox, we will have a Wordpress site with best performacne when its run on a good VPS

For your answer, I would add extra checks from some VPS companies

This is a VPS from Vultr, 4 CPUs

Code:
[root@vultr ~]# ping -c 10 wordpress.org
PING wordpress.org (66.155.40.250) 56(84) bytes of data.
64 bytes from 66.155.40.250: icmp_seq=1 ttl=54 time=82.6 ms
64 bytes from 66.155.40.250: icmp_seq=2 ttl=54 time=82.6 ms
64 bytes from 66.155.40.250: icmp_seq=3 ttl=54 time=82.5 ms
64 bytes from 66.155.40.250: icmp_seq=4 ttl=54 time=82.5 ms
64 bytes from 66.155.40.250: icmp_seq=5 ttl=54 time=82.5 ms
64 bytes from 66.155.40.250: icmp_seq=6 ttl=54 time=82.6 ms
64 bytes from 66.155.40.250: icmp_seq=7 ttl=54 time=82.8 ms
64 bytes from 66.155.40.250: icmp_seq=8 ttl=54 time=82.5 ms
64 bytes from 66.155.40.250: icmp_seq=9 ttl=54 time=82.6 ms
64 bytes from 66.155.40.250: icmp_seq=10 ttl=54 time=82.7 ms

--- wordpress.org ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9094ms
rtt min/avg/max/mdev = 82.524/82.644/82.861/0.377 ms

Code:
[root@vultr ~]# ping -c 10 api.wordpress.org
PING api.wordpress.org (66.155.40.186) 56(84) bytes of data.
64 bytes from 66.155.40.186: icmp_seq=1 ttl=54 time=82.5 ms
64 bytes from 66.155.40.186: icmp_seq=2 ttl=54 time=82.5 ms
64 bytes from 66.155.40.186: icmp_seq=3 ttl=54 time=82.7 ms
64 bytes from 66.155.40.186: icmp_seq=4 ttl=54 time=82.5 ms
64 bytes from 66.155.40.186: icmp_seq=5 ttl=54 time=82.5 ms
64 bytes from 66.155.40.186: icmp_seq=6 ttl=54 time=82.6 ms
64 bytes from 66.155.40.186: icmp_seq=7 ttl=54 time=82.5 ms
64 bytes from 66.155.40.186: icmp_seq=8 ttl=54 time=82.5 ms
64 bytes from 66.155.40.186: icmp_seq=9 ttl=54 time=82.7 ms
64 bytes from 66.155.40.186: icmp_seq=10 ttl=54 time=82.6 ms

--- api.wordpress.org ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9096ms
rtt min/avg/max/mdev = 82.518/82.609/82.794/0.084 ms
and here's from OVH, 4 CPUs too.

Code:
[root@ovh ~]# ping -c 10 wordpress.org
PING wordpress.org (66.155.40.249) 56(84) bytes of data.
64 bytes from 66.155.40.249: icmp_seq=1 ttl=55 time=87.1 ms
64 bytes from 66.155.40.249: icmp_seq=2 ttl=55 time=87.2 ms
64 bytes from 66.155.40.249: icmp_seq=3 ttl=55 time=87.1 ms
64 bytes from 66.155.40.249: icmp_seq=4 ttl=55 time=87.1 ms
64 bytes from 66.155.40.249: icmp_seq=5 ttl=55 time=87.1 ms
64 bytes from 66.155.40.249: icmp_seq=6 ttl=55 time=87.0 ms
64 bytes from 66.155.40.249: icmp_seq=7 ttl=55 time=87.1 ms
64 bytes from 66.155.40.249: icmp_seq=8 ttl=55 time=87.0 ms
64 bytes from 66.155.40.249: icmp_seq=9 ttl=55 time=87.0 ms
64 bytes from 66.155.40.249: icmp_seq=10 ttl=55 time=87.1 ms

--- wordpress.org ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9099ms
rtt min/avg/max/mdev = 87.073/87.131/87.222/0.298 ms
for pinging to API of Wordpress

Code:
[root@srv ~]# ping -c 10 api.wordpress.org
PING api.wordpress.org (66.155.40.202) 56(84) bytes of data.
64 bytes from 66.155.40.202: icmp_seq=1 ttl=55 time=87.1 ms
64 bytes from 66.155.40.202: icmp_seq=2 ttl=55 time=87.1 ms
64 bytes from 66.155.40.202: icmp_seq=3 ttl=55 time=87.2 ms
64 bytes from 66.155.40.202: icmp_seq=4 ttl=55 time=87.1 ms
64 bytes from 66.155.40.202: icmp_seq=5 ttl=55 time=87.1 ms
64 bytes from 66.155.40.202: icmp_seq=6 ttl=55 time=87.0 ms
64 bytes from 66.155.40.202: icmp_seq=7 ttl=55 time=87.1 ms
64 bytes from 66.155.40.202: icmp_seq=8 ttl=55 time=87.1 ms
64 bytes from 66.155.40.202: icmp_seq=9 ttl=55 time=87.0 ms
64 bytes from 66.155.40.202: icmp_seq=10 ttl=55 time=87.0 ms

--- api.wordpress.org ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9097ms
rtt min/avg/max/mdev = 87.053/87.111/87.203/0.297 ms
from ezservers


Code:
root@server [~]# ping -c 10 wordpress.org
PING wordpress.org (66.155.40.249) 56(84) bytes of data.
64 bytes from 66.155.40.249: icmp_seq=1 ttl=57 time=84.9 ms
64 bytes from 66.155.40.249: icmp_seq=2 ttl=57 time=85.0 ms
64 bytes from 66.155.40.249: icmp_seq=3 ttl=57 time=84.9 ms
64 bytes from 66.155.40.249: icmp_seq=4 ttl=57 time=84.8 ms
64 bytes from 66.155.40.249: icmp_seq=5 ttl=57 time=84.9 ms
64 bytes from 66.155.40.249: icmp_seq=6 ttl=57 time=84.8 ms
64 bytes from 66.155.40.249: icmp_seq=7 ttl=57 time=84.9 ms
64 bytes from 66.155.40.249: icmp_seq=8 ttl=57 time=85.1 ms
64 bytes from 66.155.40.249: icmp_seq=9 ttl=57 time=84.9 ms
64 bytes from 66.155.40.249: icmp_seq=10 ttl=57 time=84.9 ms

--- wordpress.org ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9093ms
rtt min/avg/max/mdev = 84.857/84.968/85.172/0.354 ms
Code:
root@server [~]# ping -c 10 api.wordpress.org
PING api.wordpress.org (66.155.40.188) 56(84) bytes of data.
64 bytes from 66.155.40.188: icmp_seq=1 ttl=57 time=84.9 ms
64 bytes from 66.155.40.188: icmp_seq=2 ttl=57 time=84.8 ms
64 bytes from 66.155.40.188: icmp_seq=3 ttl=57 time=84.9 ms
64 bytes from 66.155.40.188: icmp_seq=4 ttl=57 time=84.9 ms
64 bytes from 66.155.40.188: icmp_seq=5 ttl=57 time=84.9 ms
64 bytes from 66.155.40.188: icmp_seq=6 ttl=57 time=84.9 ms
64 bytes from 66.155.40.188: icmp_seq=7 ttl=57 time=85.0 ms
64 bytes from 66.155.40.188: icmp_seq=8 ttl=57 time=84.8 ms
64 bytes from 66.155.40.188: icmp_seq=9 ttl=57 time=84.8 ms
64 bytes from 66.155.40.188: icmp_seq=10 ttl=57 time=84.9 ms

--- api.wordpress.org ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9095ms
rtt min/avg/max/mdev = 84.876/84.945/85.054/0.349 ms
from Arv VPS

Code:
root@myserver [~]# ping -c 10 wordpress.org
PING wordpress.org (66.155.40.250) 56(84) bytes of data.
64 bytes from 66.155.40.250: icmp_seq=1 ttl=55 time=62.7 ms
64 bytes from 66.155.40.250: icmp_seq=2 ttl=55 time=60.7 ms
64 bytes from 66.155.40.250: icmp_seq=3 ttl=55 time=62.3 ms
64 bytes from 66.155.40.250: icmp_seq=4 ttl=55 time=62.0 ms
64 bytes from 66.155.40.250: icmp_seq=5 ttl=55 time=61.3 ms
64 bytes from 66.155.40.250: icmp_seq=6 ttl=55 time=61.8 ms
64 bytes from 66.155.40.250: icmp_seq=7 ttl=55 time=62.1 ms
64 bytes from 66.155.40.250: icmp_seq=8 ttl=55 time=60.5 ms
64 bytes from 66.155.40.250: icmp_seq=9 ttl=55 time=61.1 ms
64 bytes from 66.155.40.250: icmp_seq=10 ttl=55 time=62.0 ms

--- wordpress.org ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9086ms
rtt min/avg/max/mdev = 60.573/61.687/62.746/0.747 ms

root@myserver [~]# ping -c 10 api.wordpress.org
PING api.wordpress.org (66.155.40.188) 56(84) bytes of data.
64 bytes from 66.155.40.188: icmp_seq=1 ttl=55 time=61.7 ms
64 bytes from 66.155.40.188: icmp_seq=2 ttl=55 time=60.5 ms
64 bytes from 66.155.40.188: icmp_seq=3 ttl=55 time=61.3 ms
64 bytes from 66.155.40.188: icmp_seq=4 ttl=55 time=60.7 ms
64 bytes from 66.155.40.188: icmp_seq=5 ttl=55 time=60.7 ms
64 bytes from 66.155.40.188: icmp_seq=6 ttl=55 time=60.6 ms
64 bytes from 66.155.40.188: icmp_seq=7 ttl=55 time=61.0 ms
64 bytes from 66.155.40.188: icmp_seq=8 ttl=55 time=61.3 ms
64 bytes from 66.155.40.188: icmp_seq=9 ttl=55 time=60.8 ms
64 bytes from 66.155.40.188: icmp_seq=10 ttl=55 time=60.6 ms

--- api.wordpress.org ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9087ms
rtt min/avg/max/mdev = 60.565/60.969/61.783/0.463 ms
I also look forward to seeing other tests from web hosting providers on the forum, if you have better results, I would go with your services.


Cheers,
 

VirtuBox

Well-known member
Registered
Joined
May 3, 2016
Messages
1,622
Points
83
It will require to compare those results to WordPress front and admin page to see how much it could impact WordPress speed.
I will make some tests to check that.
Because WordPress run a cron each 3 minutes to check plugins updates but I'm not sure it can impact the website speed even with +/- 50ms.
 
Older Threads
Replies
1
Views
2,240
Replies
14
Views
5,266
Replies
2
Views
3,111
Latest Threads
Recommended Threads
Replies
10
Views
4,881
Replies
8
Views
4,188
Replies
0
Views
1,007
Similar Threads

Latest Hosting OffersNew Reviews

Sponsors

Tag Cloud

You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.

Top