Why is my WordPress site so slow?
Short answerUsually it’s one or more of: cheap shared hosting, too many plugins, a heavy page builder or theme, oversized images and no caching. Each adds weight or server time. Test with PageSpeed Insights to see which is hurting most, then fix in order: hosting and caching first, then images, then plugins and theme.
Slow WordPress site? Send me the link.
I’ll check hosting, plugins and images and tell you what’s slowing it down. Free, within two business days.
The longer answer
Find out where the time goes
Run your key pages through PageSpeed Insights on mobile. Look at Time to First Byte first. If it’s slow, the server is struggling before anything loads, which points to hosting or missing caching. If TTFB is fine but LCP is poor, the problem is on the page: images, scripts, fonts or the theme. The field data section shows what real visitors experience.
Test a few page types, not just the homepage. A blog post, a service page and a page with a form can each have different problems.
The usual culprits
- Hosting. Crowded shared servers respond slowly, especially under load.
- No caching. WordPress builds every page from the database on each visit unless cached.
- Page builders. They often add a lot of nested markup, CSS and JavaScript.
- Plugins. Each can add scripts to every page, even where unused.
- Images. Uploading full-size photos without resizing or WebP.
- Third-party scripts. Chat widgets, sliders, multiple analytics tags.
Often it’s several of these at once. A modest theme on decent hosting can carry a few plugins easily, while the same plugins on a crowded server feel painful.
Fixes in the order I’d try them
Move to solid managed hosting and turn on page caching. Add a CDN. Resize and compress images, and lazy-load those below the first screen. Deactivate plugins you don’t need and replace heavy ones with lighter options. If the page builder is the bottleneck, no plugin will fully fix it. That’s when a rebuild, on a lean theme or off WordPress entirely, is worth considering.
Test after each change, one at a time, so you know what actually helped and can undo anything that breaks a page.
What I’d do
Nick Lovett, founder of Tavro
I’d look at Time to First Byte and the plugin list before anything else. Those two usually tell the story. Hosting and caching fixes are quick wins. Image cleanup is tedious but effective. If the site is built on a heavy page builder, I’d be honest that tuning only goes so far. At that point the choice is a lean rebuild in WordPress or a move to a prerendered custom site, which is what I build and where speed comes almost for free.
Follow-up questions
There’s no fixed number. One heavy plugin can do more harm than ten light ones. Remove any you don’t actively use.
It often helps a lot with server response. It won’t fix oversized images or a bloated page builder.
It can. Google considers page experience, though relevance matters more, and slow pages lose visitors before they convert.
Keep reading
- nick@tavro.ca
- 587-439-9994
- Calgary, Alberta