A slow WordPress site is not just an annoyance - it is a business problem. Google uses page speed as a ranking factor, and research consistently shows that conversions drop sharply as load times increase. The good news is that most speed problems are fixable, and the first step is knowing exactly what you are dealing with. A speed audit gives you a clear, prioritized list of what to address.
Here is how to run one properly.
Step 1: Choose Your Testing Tools
Three tools do the heavy lifting for a thorough speed audit.
Google PageSpeed Insights (pagespeed.web.dev) is the most important because it measures Core Web Vitals - the exact metrics Google uses for ranking. It shows both lab data (simulated) and real-world field data from actual Chrome users. Always test your homepage and at least one key inner page.
GTmetrix (gtmetrix.com) gives you a waterfall chart - a visual breakdown of every single request your page makes and how long each one takes. This is invaluable for spotting bottlenecks that PageSpeed's summary can miss. Use the Vancouver or Toronto server location for Canadian sites.
WebPageTest (webpagetest.org) is the most advanced of the three. It lets you test from specific geographic locations, simulate different connection speeds, and run filmstrip comparisons. Use it once you have already fixed the obvious issues and want to go deeper.
Step 2: Understand the Scores
Do not panic at a score below 90. Mobile scores are almost always lower than desktop scores, and a score in the 60s on mobile is common even for well-optimized sites.
What matters more than the overall score are the individual metrics:
- LCP (Largest Contentful Paint): How long it takes for the main content to appear. Aim for under 2.5 seconds. This is usually your most impactful metric to fix.
- INP (Interaction to Next Paint): How quickly the page responds to user interactions. Under 200ms is good.
- CLS (Cumulative Layout Shift): Whether elements jump around while loading. Should be under 0.1.
- TTFB (Time to First Byte): How long the server takes to respond at all. Over 600ms is a red flag - it points to a server or caching problem rather than a frontend issue.
Step 3: Investigate the LCP Image
The single most impactful fix on most WordPress sites is optimizing the LCP element - usually the large hero image or banner at the top of the page.
In PageSpeed Insights, look for the "LCP element" callout. If it is an image:
- Serve it in WebP format (plugins like Imagify or ShortPixel handle this)
- Add
fetchpriority="high"to the image tag or use your theme's "preload" option for the hero image - Make sure it is not being lazy-loaded (lazy loading the LCP image actively hurts performance)
- Size it correctly - a 3000px wide image displayed at 1200px is pure waste
Step 4: Check Render-Blocking Resources
In GTmetrix's waterfall, look for CSS and JavaScript files that load before the page can display anything. These are render-blocking resources.
Common culprits in WordPress:
- Google Fonts (self-host them with the OMGF plugin instead)
- Multiple CSS files from different plugins loading in the header
- jQuery and other JavaScript loading before the content
A caching plugin like WP Rocket or LiteSpeed Cache can defer non-critical JavaScript and inline critical CSS, which dramatically improves perceived load speed.
Step 5: Address TTFB
A high TTFB means your server is thinking too long before sending anything back to the browser. This is almost always fixed by enabling full-page caching.
In WordPress, install a caching plugin and enable its "page cache" feature. For hosts running LiteSpeed (like dotCanada), the LiteSpeed Cache plugin is the most effective option and is tightly integrated with the server. For Apache/Nginx hosts, WP Rocket and W3 Total Cache are solid alternatives.
If TTFB is high even with caching enabled, your hosting plan may be under-resourced - a common issue on very cheap shared hosting.
Step 6: Audit Your Plugins
Every plugin adds code. Inactive plugins still load in some cases. Plugins that have not been updated in years can introduce bloat and compatibility issues.
Go to your plugin list and ask: do I actually use this? If not, delete it - not just deactivate it.
Use the Query Monitor plugin to identify plugins that are executing slow database queries. This is often the hidden cause of high TTFB on sites with complex setups.
Building Your Action List
After running all three tools, you will have a list of recommendations. Prioritize in this order:
- Fix LCP image (biggest ranking and UX impact)
- Enable page caching (fixes TTFB)
- Defer JavaScript
- Optimize and convert images to WebP
- Self-host Google Fonts
- Remove unused plugins
Work through the list methodically, testing after each change. A speed audit is not a one-time event - run it quarterly to catch regressions from new plugins or theme updates.
