payless.host
Why a WordPress site is slow, and what to fix first
Updated Nov 22, 2026
A slow WordPress site loses visitors before they see what you built. Most slowdowns come from a small set of causes, and most can be fixed without rebuilding anything.
Unoptimised images are eating your bandwidth
Images that load at their original resolution cost more to serve and take longer to reach a visitor's browser. Compress them before upload, or install a plugin that does it automatically. A 2MB photograph that could have been 200KB is ten times the weight for no visible improvement on a phone or laptop screen. Ignore this and mobile users on slower connections will leave before the page renders.
No caching means the server rebuilds every page from scratch
WordPress assembles a page from the database every time someone requests it. A caching plugin stores the finished page and serves that instead, which is faster by orders of magnitude. Without caching, every visitor forces the server to repeat work it already did. The cost shows up as load time when traffic increases, and as hosting bills when you scale to handle it.
Too many plugins, or poorly written ones
Every active plugin adds code that runs on each page load. Twenty plugins doing small jobs can slow a site more than three doing large ones, and one plugin written without care for performance can stall everything behind it. Deactivate anything not in use, and test speed after each new install. The symptom is a site that was fast when it launched and got slower as features were added.
Database bloat from revisions and transients
WordPress saves every draft, revision, and temporary value. A site running for two years can carry thousands of post revisions and expired transients that slow down every database query. Optimise the database monthly, limit the number of revisions kept, and clear transients that are no longer needed. Hosting with managed WordPress plans often handles this automatically — DreamHost's DreamPress 1 at 14.99 EUR/month includes database optimisation, while shared plans leave it to you.
A theme doing too much
Themes marketed as "multipurpose" or "all-in-one" load features you will never use. A theme built for an online shop loads shop code even if your site is a blog. Choose a theme designed for your use case, not one that tries to be all things. Switching themes is easier than optimising a bloated one, and a lighter theme often needs fewer plugins because it does less.
Hosting that cannot handle the traffic
Shared hosting works until it doesn't. If a site slows during peak hours but is fast at 3am, the server is underpowered or oversold. Shared plans from HostGator start at 3.75 USD/month, but those plans share resources with dozens of other sites. Moving to a VPS or managed WordPress host gives dedicated resources and usually solves the problem outright. InterServer charges 2.50 USD for the first month of shared hosting, then 7.00 USD after, which is among the highest monthly renewal rates here — know what you're committing to before the intro period ends.
No content delivery network
A visitor in Sydney loading a site hosted in Virginia waits for data to cross an ocean. A CDN caches static files on servers closer to the visitor, which cuts that wait to near zero. Most hosts now include a CDN or integrate with one. Cloudflare offers a free tier that works with any host. The speed improvement is largest for visitors farthest from your server, and the setup usually takes less than an hour.
What to fix first
Start with images and caching — those two deliver the largest improvement for the least effort. Then check plugins and database size. Move to better hosting only after optimising what you have, because throwing resources at unoptimised code costs more and fixes less than the reverse order. A slow site on shared hosting is often still slow on a VPS if the images are 2MB each and nothing is cached.
