Time response continues causing me headaches, but I’m discovering causes and differentiating the causes, so I’m progressing in the right direction.
The situation now is that pictures are compressed and with a light weight, no code faults, reduced CSS and JS files, CDN activated, cache, etc.
It depends on the pictures of the main screen that time response differs, anyway the time to load the page yesterday was 3,26s. What’s the main issue?
The first 2 requests take 1,3s (40%) mainly the web browser waiting for response from server (yellow line).
So, the server, what’s happening with the server?
After checking for some weeks the performance of the server, the conclusion is that memory assignment is fine, and there are not faults on the server, the parameter that provokes time response issues is the CPU at 100%.
What does it mean 100%? I have not the data of the speed and number of CPUs, but I have read about strategies of hosting companies about how they co-locate the shared environments and how they do it.
Basically, you can host so many people in one server and be aggressive on price, or host less people on same place and increase the price (providing better quality). I have read about hosting services that co-locate 5-10 people on a server, and other that co-locate over 400 places.
You can easily understand how much neighbors (places) you have in your neighborhood (the shared server) using tools such this:
I work with two different hosting providers, in one I have 29 neighbors, in the other one just 4.
Now I know:
- I have to move to the neighborhood with less neighbors.
Next time I look for a hosting service, I will ask for the number of neighbors.
- The consumers community of shared hosting services should start demanding a clear parameter to understand the quality of the shared hosting. Some offers include infinite disk or bandwidth, what about a minimum CPU assignment in MHz?