Speed up WordPress on shared hosting
Caching, images and the plugins that quietly cost you a second per page.
Updated 29 Aug 2026
Most slow WordPress sites on shared hosting are slow for the same four reasons.
No page cache. Enable the object and page cache on your plan — both switches live in the control panel, which opens from the account itself rather than from a separate address. A cached page is served without touching PHP or MySQL at all.
Unoptimised images. A 3 MB hero image costs more than every plugin combined. Serve WebP and size images to their display width.
Too many plugins doing the same job. Two caching plugins are slower than one. Audit with Query Monitor and remove anything that adds queries on every request.
A theme that loads everything. Page builders load their entire library on pages that use none of it. Check whether your theme offers per-page asset loading.
How do I know it is the hosting and not the site?
Compare a cached page with an uncached one. If the homepage is fast and the cart is slow, the site is doing the work — carts and search pages skip the cache by design. If everything is slow including a static file, ask us to look; a noisy neighbour is our problem to fix, not yours to tune around.
When is it time to move to a VPS?
When the site is fast for one visitor and slow for thirty. Shared hosting divides one machine between many accounts, so sustained CPU is the ceiling you eventually meet — not disk or bandwidth. A VPS buys reserved CPU and memory; it does not make an unoptimised site fast, and moving one before the four points above are settled usually buys a more expensive version of the same wait.