← All articles
HOSTING GUIDE
A slow website: what hosting can fix and what you must change yourself
Moving to a more expensive server may help if the application lacks resources. But a site with very large images, many scripts or an inefficient database may remain just as slow. Before changing plans, find out where the time is actually spent.
Measure the time until the server starts responding, then the loading and rendering of the whole page. A slow server response may involve the database, code, overload or distance. Slow rendering can result from images and scripts that a new host will not remove. Test several typical pages and repeat the measurements under the same conditions.
Fix the largest bottleneck
Start with images in suitable sizes and formats, remove unnecessary extensions and inspect expensive database queries. Caching can help pages that are served repeatedly to visitors. Set it carefully for personalized pages and carts so one user does not see another user's content. A CDN can bring static files closer to visitors in different countries, but it cannot replace slow application work on the origin server.
Only then change the configuration
If measurements show exhausted memory, CPU or a concurrent process limit, compare a stronger plan or a different service type. Measure again afterwards using the same method. Otherwise you cannot tell whether you paid for a real improvement.
Measure an ordinary visitor and a signed-in user separately. A cached public page can be very fast while content editing or the cart puts much more load on the database. When comparing plans, ask whether you can test your own application. A short trial with the same site version tells you more than a general claim about a fast processor or storage device.
Practical question: Is the first response from the server slow, or does the page take a long time to render in the browser? The answer points to the right place to act.