Wordpress Website running EXTREMELY slow on my new vServer

Nonilol

Elite Member
Joined
Mar 1, 2015
Messages
1,959
Reaction score
825
I recently got myself a cheap vServer from Strato.de (German Hosting) for around 10$ per month.
Specs are the following:

4GB RAM
2 cores
300gb ssd / hdd (hybrid, databases on ssd)

It's running Ubuntu. I installed Plesk and then installed wordpress via oneclick installation.
However, it's running extremely slow compared to my previous host.
Saving a simple post in wordpress takes around 20-25 seconds. 10 seconds to navigate from Wordpress Dashboard to plugin list.

Website itself ( https://instasound.net if anyone wants to test) is also pretty slow.
Pingdom Stats: Loadtime 5sec, Pagesize, 1.1MB, 22 requests
Used to be under 1.5sec for a similar website I had on my previous server.
There is almost no traffic on that website. (under 100 UV per day)

What could possibly be wrong?
Any idea?
 
Even 1.5s is horribly slow. Your server has a misconfiguration, or since it's a VPS you could have a bad neighbor on the same hardware. Obvious question: You're caching, right? And you've used ping and traceroute to determine if there are any network issues?
 
Even 1.5s is horribly slow. Your server has a misconfiguration, or since it's a VPS you could have a bad neighbor on the same hardware. Obvious question: You're caching, right? And you've used ping and traceroute to determine if there are any network issues?

It's been like this since I've bought this vServer around two weeks ago.
I am using WP Super Cache to cache my website, when the website is cached in pingdom, loading time is significantly shorter.
I am also using Cloudflare. Speed is the same without Cloudflare, I tested that.

Pinging looks pretty normal to me: (Antwort von = response from)
Code:
Antwort von 104.28.24.196: Bytes=32 Zeit=34ms TTL=57
Antwort von 104.28.24.196: Bytes=32 Zeit=35ms TTL=57
Antwort von 104.28.24.196: Bytes=32 Zeit=37ms TTL=57
Antwort von 104.28.24.196: Bytes=32 Zeit=35ms TTL=57

However here is the result from Tracert:

Code:
  1  2 ms  5 ms  2 ms  fritz.box [192.168.178.1]
  2  25 ms  24 ms  24 ms  a81-14-248-241.net-htp.de [81.14.248.241]
  3  25 ms  25 ms  28 ms  a81-14-249-60.net-htp.de [81.14.249.60]
  4  29 ms  30 ms  69 ms  bei-b1-link.telia.net [62.115.8.185]
  5  36 ms  43 ms  93 ms  hbg-bb1-link.telia.net [62.115.112.153]
  6  37 ms  36 ms  38 ms  hbg-b1-link.telia.net [80.91.246.7]
  7  34 ms  34 ms  33 ms  cloudflare-ic-314537-hbg-b1.c.telia.net [62.115.61.202]
  8  45 ms  34 ms  34 ms  104.28.24.196

The last hop takes some time to load.
It first goes:
Code:
  8  45 ms  34 ms  34 ms
then there is a 3-5 second delay, then it goes
Code:
  8  45 ms  34 ms  34 ms 104.28.24.196
 
The last hop is probably firewalled and it times out. To rule out wordpress entirely what happens when you place a plain old html file in the document root?
 
The last hop is probably firewalled and it times out. To rule out wordpress entirely what happens when you place a plain old html file in the document root?
Hmm, a simple html file loads quickly. (260ms)
Plesk admin panel seems to have okay loading times, too.

Does this mean something is wrong with wordpress?

Edit: Server has default configurations, except some php settings are changed in order to run the Avada WP theme.
 
Do a website speed test to locate where the flaw is.

I often use webpagetest.org for that task. Then you can define if it your server, wordpress, a js script (plugin?), an uncompressed image and so on. Test it and post your results here if you don't know how to analyze it/how to fix it.
 
Do a website speed test to locate where the flaw is.

I often use webpagetest.org for that task. Then you can define if it your server, wordpress, a js script (plugin?), an uncompressed image and so on. Test it and post your results here if you don't know how to analyze it/how to fix it.

Thanks for the advice! As it seems, most of the time the speedtest is waiting for an answer from the server.
Here is a link to the webpagetest result: http://www.webpagetest.org/result/160624_BM_10PW/
I also attached the result as a jpg file.
 

Attachments

  • instaslow.jpg
    instaslow.jpg
    400.9 KB · Views: 4
Ok so yeah you can improve a little bit.

Firstly, there is one pic that load during 1330ms.That is way too long. You should cut it to adapt it to the actual needed size (no resizing) + compress it. Even consider lazy load.

What is exactly bag2 on your website? Take 2s aswell.

And there is another pic with a 404 error, consider fixing it + doing the same as above.

Redo the test afterwards and let me know.
 
do the above that 001 mentioned then..
move the site over to another server to test it and do another speedtest then compare to rule out the server
 
Ok so yeah you can improve a little bit.
Firstly, there is one pic that load during 1330ms.That is way too long. You should cut it to adapt it to the actual needed size (no resizing) + compress it. Even consider lazy load.
What is exactly bag2 on your website? Take 2s aswell.
And there is another pic with a 404 error, consider fixing it + doing the same as above.
Redo the test afterwards and let me know.
Not sure if you've read my initial post. It's not just the frontend running slow, especially the backend takes forever to load.
I tested a site without that 404 error and without any image on it, problem remains the same:
Almost 2 seconds until first byte .

do the above that 001 mentioned then..
move the site over to another server to test it and do another speedtest then compare to rule out the server
 
it is the redirect to https that is causing it
 
Last edited:
Thanks for everyone who tried to help me.
It turned out it was just my sever being very very slow.
I called Strato and they told me literally "a vServer cannot handle Wordpress, you need to upgrade to a dedicated sever for 30 bucks"

Good bye Strato!
Moved to hosteurope, everything works fine now :)
 
An error message that I received while visiting your web site.

Use a hosting service that is reliable, many website hosting companies are running in the hands of one person.

I hope you understand it
 
Did you use a photo from shutterstock as a placeholder or is that actually how the site is going to look?
 
Fixed the issue - by moving to Hosteurope.
Apparently, Strato is just a shitty webhost.

Did you use a photo from shutterstock as a placeholder or is that actually how the site is going to look?
Just as placeholder to see what it looks like of course.
Did you like it btw? Worth purchasing?
 
do the above that 001 mentioned then..
move the site over to another server to test it and do another speedtest then compare to rule out the server

If it was me I would have done this.
Fixed the issue - by moving to Hosteurope.
Apparently, Strato is just a shitty webhost.

Good decision, you get what you pay for.
 
Back
Top