Every business owner wants a faster website. Every website also seems to want 27 plugins, a homepage video, three tracking scripts, and a cookie banner that loads before anything else. Sometimes these goals have a complicated relationship.
Three things cause almost every WordPress speed problem, and you need to know which one is actually hurting you before spending money on a fix. Running a caching plugin on bad hosting does not fix anything. Buying a premium theme does not fix anything. You need to diagnose first.
Cause 1: Bad hosting
Cheap shared hosting puts hundreds of websites on one server. When traffic spikes on any of them, response times for every site on that server climb. Your site becomes slow because of someone else's traffic.
How to test: Open GTmetrix or Google PageSpeed Insights and look at Time to First Byte (TTFB). Anything over 600ms is a server problem — not a theme or plugin problem.
The fix is moving to a VPS or managed WordPress host. Options range from VPS platforms like Cloudways to managed hosts like WP Engine and Kinsta; check current pricing with each. If TTFB is the bottleneck, a server upgrade improves load time without touching a single plugin.
Cause 2: Too many plugins
Plugins pile up quietly. Many end up doing the same job twice. A cache plugin, a security plugin, a backup plugin, an SEO plugin, a page builder, and six deactivated plugins that still load their assets on every page. (The website came with 47 plugins. Which is impressive considering it only had five pages.)
How to test: Install Query Monitor. Look at the number of database queries on a single page load. Anything over 50 queries on a simple page is worth investigating.
For each active plugin, ask one question: what does this do, and do I actually need it? Deactivate and delete anything you cannot answer clearly. Test load time after each removal. You will typically find two or three plugins responsible for most of the overhead.
Cause 3: Unoptimized images
This is the most common cause and the easiest to fix. A business owner uploads a 4MB photo from their phone. The theme displays it at 300px wide. The browser downloads 4MB to show a thumbnail.
How to test: Run your site through GTmetrix. Open the waterfall view. If you see image files over 200KB loading on a single page, you have an optimization problem.
Install ShortPixel or Imagify. Run a bulk compression on all existing images. Set them to compress new uploads automatically going forward. Images are usually the heaviest files on a page, so this fix alone often makes the biggest single dent in page weight and improves Core Web Vitals scores.
Fix them in the right order
Fix hosting first if your TTFB is over 600ms — no other optimization matters on a slow server. Fix images second, because it is free and has the biggest impact on download size. Fix plugins third, since that requires careful testing and may break things.
The pattern I see most often is decent hosting, more plugins than the site needs, and no image optimization at all. In that situation, fixing images and removing dead plugins is where most of the gain is, before anyone touches the hosting. WooCommerce stores have additional speed requirements on top of this baseline.
When it is still slow after all three
If you have addressed hosting, plugins, and images and the site is still failing Core Web Vitals, the problem is the theme or custom code. Page builders like Elementor and Divi add significant CSS and JavaScript weight. A poorly coded custom theme can add dozens of render-blocking requests.
That requires a different kind of audit — looking at what CSS and JavaScript is loading, whether it is needed on every page, and whether render-blocking resources can be deferred. If you need help diagnosing this, Digital Invento's performance optimization work starts with exactly this kind of audit.
