“We probably need a whole new website.” I hear that a lot, usually right after someone’s site took eight seconds to load in front of a customer. Most of the time they don’t need a new site. They need an afternoon of cleanup. Slow WordPress sites are slow for the same handful of reasons, and I check them in the same order every time.
Images, always images first
It’s the least technical problem and the biggest one. Photos uploaded straight from a phone at 4000 pixels wide, displayed at 400. A homepage carrying 30MB of images. Before touching anything clever, I compress and resize the images on the heaviest pages. On most small business sites, this alone gets the biggest win of the whole project.
Then the plugin pile
Every active plugin potentially adds scripts and database queries to every page load. I look for the usual suspects: two caching plugins fighting each other, a slider plugin loading on pages with no slider, social feed widgets pulling from three networks on every visit. Deactivate, measure, repeat.
Caching, done once, done right
- One caching plugin, configured properly — not three, half-configured
- Page caching on, so WordPress isn’t rebuilding every page per visitor
- Browser caching so returning visitors reuse what they already downloaded
- If the host offers server-level caching, use theirs and keep it simple
And sometimes, it’s the hosting
There’s a floor below which no cleanup can help. A $3-per-month shared server stuffed with five hundred sites will be slow no matter what I do. When the cleanup is done and the site is still dragging, I test the same site on better hosting. When the difference is dramatic — and it often is — that’s the answer, and moving is far cheaper than rebuilding.
The pattern in all of this: measure, change one thing, measure again. Speed work without measurement is just superstition. Every site I tune keeps a before-and-after record, and the number the owner cares about — how fast it feels on their own phone — is the one I optimize for.
