Short answer: most slow WordPress sites are slow for one of four reasons — unoptimized images, a bloated page builder loading unused assets on every page, shared hosting with no caching, or too many plugins doing overlapping jobs. Fix those four in order and you’ll usually cut load time by half before touching anything else.
We’ve run speed audits on client sites for over 15 years, and the pattern repeats itself constantly: people blame their theme first, when the theme is rarely the real problem. Here’s the checklist we actually use, in the order that gives you the biggest win first.
1. Check what’s actually loading on your homepage
Before changing anything, run your site through Google PageSpeed Insights and note two numbers: Largest Contentful Paint (LCP) and Total Blocking Time (TBT). These map to what a real visitor experiences — LCP is how long the main content takes to show up, TBT is how janky the page feels while it loads.
If LCP is over 2.5 seconds, don’t guess — the report tells you the exact file causing it. Nine times out of ten it’s an unoptimized hero image or a video background.
2. Images: the single biggest win
A hero image straight out of a phone camera or stock photo site can easily be 3-5MB. That alone can add 2-3 seconds to load time on its own.
- Compress everything with a plugin like Imagify or Smush — aim for WebP format, not JPEG/PNG
- Never use raw video files (.mov, .avi) as backgrounds — convert to compressed .mp4 or, better, use a static image with a subtle CSS animation
- Turn on lazy loading for anything below the fold
3. Page builders load more than they need to
If you’re on WPBakery, Elementor, or a similar builder, every page can load CSS/JS for every element type available — even the ones you’re not using on that page. Most builders now have an asset optimization or “unused CSS” mode. Turn it on. It’s usually one checkbox and it’s the difference between loading 40 CSS files and loading 4.
4. Hosting and caching
No amount of plugin tweaking fixes a server that’s slow to respond in the first place. Check your Time to First Byte (TTFB) — if it’s over 600ms before any caching, the problem is the server, not WordPress.
- Use a real caching plugin (WP Rocket, LiteSpeed Cache, or W3 Total Cache) — page caching alone often cuts load time 30-50%
- If you’re on shared hosting and traffic has grown, a VPS with NVMe storage (Vultr, DigitalOcean, etc.) makes a measurable difference for database-heavy WordPress sites
- Enable a CDN so images and static files load from a server near the visitor, not just your origin server
5. Plugin audit
Every plugin adds database queries and often its own CSS/JS. Go to Plugins and ask, for each one: is this still doing something, or did we install it for a project two years ago and forget about it? Deactivating five unused plugins is often worth more than an hour of manual optimization.
How long does this actually take?
For a typical business site, images + caching + one round of plugin cleanup takes half a day and is usually the difference between a 6-second load and a 2-second load. Hosting migration is the only step here that takes longer — plan a few hours and do it during low-traffic hours.
Frequently asked questions
Does site speed actually affect Google rankings?
Yes — Core Web Vitals (which include LCP) are a confirmed Google ranking factor, and slow sites also convert fewer visitors into leads regardless of ranking, so it’s worth fixing either way.
Is a page builder like WPBakery or Elementor bad for speed?
Not inherently — the issue is unused assets loading on every page. Most modern builders have an optimization setting for this; it’s usually off by default.
Do I need to switch hosting to fix speed?
Not always. Try images, caching, and plugin cleanup first. Hosting only becomes the bottleneck when TTFB is high even with caching enabled.
If you want a second pair of eyes on your own site’s numbers, run it through PageSpeed Insights first — the report itself usually points straight at the fix.
