A slow WordPress site costs money twice: once in lost visitors who leave before the page finishes loading, and again in search rankings, since page speed is a confirmed part of Google's ranking algorithm. The good news is that WordPress speed problems are almost always the same handful of causes — and most of them are fixable without touching a line of code.
Check your current speed first
Before changing anything, get a baseline. Google PageSpeed Insights is free and gives both a performance score and the specific Core Web Vitals metrics Google actually uses for ranking — Largest Contentful Paint (how fast the main content appears), Cumulative Layout Shift (how much the page jumps around while loading), and Interaction to Next Paint (how responsive the page feels). Run your homepage and one or two key inner pages; results can vary significantly by page depending on content and images.
1. Hosting is the foundation everything else sits on
Cheap shared hosting is the single most common cause of a genuinely slow WordPress site — no amount of plugin optimization fixes a server that's overloaded with hundreds of other sites competing for the same resources. Managed WordPress hosting, tuned specifically for WordPress's database and caching needs, typically costs more than basic shared hosting but produces a dramatically faster baseline before any other optimization work even starts. If a site is still slow after fixing images and plugins, hosting is almost always the next place to look.
2. Images are usually the biggest single fix
Photos uploaded straight from a phone or camera are frequently 5–10x larger than what a web page actually needs to display them. Resizing images to their actual display dimensions, compressing them, and serving modern formats like WebP typically cuts page weight dramatically — often the single biggest improvement available on a content-heavy site, and one most site owners can do themselves with a plugin or by re-exporting images at the right size before uploading.
3. Caching turns database lookups into static files
WordPress rebuilds most pages from the database on every single visit by default — a caching plugin instead serves a pre-built static version of the page, skipping that rebuild entirely for most visitors. This is often the highest-leverage single change available without touching hosting, particularly on sites with a lot of dynamic content (blogs, WooCommerce stores, membership sites) where database queries are the main bottleneck.
4. Plugin bloat adds up fast
Every plugin adds its own code, and often its own database queries and scripts loaded on every page — whether that page actually uses the plugin or not. Page builders and "all-in-one" plugins are common offenders, loading large amounts of CSS and JavaScript sitewide for features used on only a handful of pages. Auditing installed plugins and removing ones that duplicate functionality or aren't actively used is free — no purchase required, just cleanup.
5. A CDN speeds up visitors far from your server
A content delivery network caches static files (images, CSS, JavaScript) on servers around the world, so a visitor in Vancouver isn't waiting on a round trip to a server in Toronto for every file. For a site with a genuinely national Canadian audience, or any international traffic, a CDN closes a real gap that hosting and caching alone can't — visitors simply load static assets from a server physically closer to them.
6. What to skip
Not every "speed tip" is worth the effort. Minifying CSS/JS by hand, chasing a perfect 100 PageSpeed score, or rebuilding a site around a "lightweight" theme when the real problem is hosting or images — these are low-leverage compared to the fixes above. The 80/20 rule applies here: hosting, images, and caching solve the overwhelming majority of real-world WordPress speed problems.
Mobile speed is the speed that matters most
For most WordPress sites, the majority of traffic is now mobile, and mobile speed is typically worse than desktop by default — smaller devices on slower connections are hit hardest by unoptimized images and heavy scripts. Google also uses mobile-first indexing, meaning the mobile version of a page is what actually gets evaluated for ranking, not the desktop version. Testing speed on mobile specifically (PageSpeed Insights reports both) rather than assuming desktop results apply is a step that's easy to skip and expensive to skip.
WooCommerce sites have their own bottlenecks
An online store adds database load that a brochure site never sees — product catalogs, cart sessions, and checkout all hit the database on nearly every page view, which is exactly the kind of load that generic caching plugins sometimes handle poorly (caching a cart page for the wrong visitor is a real bug, not a hypothetical one). WooCommerce sites benefit from caching configured specifically to exclude cart, checkout, and account pages from static caching while still caching product and category pages normally. This is a case where "just install a caching plugin" isn't quite enough — the configuration matters as much as the plugin itself.
A realistic order of operations
- Baseline — run PageSpeed Insights on the homepage and 1–2 key inner pages.
- Images — resize and compress anything oversized; this alone often produces a visible improvement.
- Caching — install and configure a caching plugin properly (a badly configured cache can serve stale content, so test after setup).
- Plugin audit — remove anything unused or duplicated in function.
- Hosting — if the site is still slow after the above, this is almost always the next step.
- CDN — worth adding once the fundamentals above are handled, especially for sites with traffic spread across Canada or internationally.
Why this matters beyond user experience
Core Web Vitals are a confirmed part of Google's ranking algorithm, which means speed work doubles as SEO work — one of the few ranking factors that's entirely within a site owner's direct control to fix, without needing new content or backlinks. It also compounds with everything else: a fast site keeps visitors on the page long enough to actually read the content and convert, which is the whole point of the traffic in the first place.
When it's time to stop DIY-ing it
Plugin conflicts, a host that's genuinely undersized for the traffic, or a theme built on outdated code are common walls that a plugin alone won't fix. At that point, a proper technical audit — checking hosting configuration, theme code quality, and plugin stack together — finds the actual bottleneck instead of guessing at fixes one plugin at a time. This is part of what's included in managed WordPress maintenance, which covers ongoing updates, backups, security, and speed monitoring so performance doesn't quietly degrade again after the initial fix.
How to know it's actually working
Re-run PageSpeed Insights against the same pages after each round of changes and compare against the original baseline — not against a theoretical "perfect" score, which isn't the goal. A meaningful improvement shows up as a lower LCP time and a visibly faster feel on a real mobile connection, not just a higher number on the report. It's also worth checking analytics for bounce rate and time-on-page before and after; a real speed fix usually shows up there too, since it's the actual visitor behaviour the speed work was meant to improve in the first place.
Get a speed audit for your WordPress site
Whether it's a one-time speed fix or an ongoing WordPress build that's fast by design from launch, we can help. Managed maintenance plans start at $99/month and include speed monitoring as standard. Get a free, no-obligation quote today — we respond within one business day. Prefer to talk? Call (647) 689-6069.
