While preparing this guideline I found very quickly that some optimizations are only possible if the website operator can influence the configuration of the Apache web server in its entirety. This is not possible in a shared hosting tariff generally, since the customer is provided only a very limited ability to adapt and installation of additional modules.
What the Shared hosting also sometimes have problems – especially in terms of performance – leads, is the fact that there are many different websites (in our case about 100) are located on a server and thus share the available computing power. Then finds, for example, on a hosted Web sites a rush of visitors instead of the other sites automatically go to their knees or in part are no longer accessible. The curve shown in the last article of the back-end-time is a prime example of what you can expect volatile response times in a Shared-Hoster. The constant charging time is different.
Another disadvantage of the shared hosting has to do with the subject of SEO. All websites on the web space of a shared web host are reachable via the same IP address, which can influence the ranking on Google under negative circumstances. The reasons for this are buried (bad neighborhood) in the keyword “Bad Neighborhood”. Are on your webspace for example websites hosted that were punished by spamming or not allowed SEO techniques from Google, then this can also have an impact on the ranking of your page because it is reachable via the same IP address.
By changing to a V-server with its own IP address for you the theme “Bad Neighborhood” is no longer relevant.