WordPress Development
How to Conduct a WordPress Speed Audit and Fix What You Find
Most WordPress speed problems come from 2–3 specific causes. This guide walks through a systematic audit of every layer — hosting, theme, plugins, images, and third-party scripts — and how to fix each one.
A slow WordPress site costs you visitors, conversions, and search rankings. Most speed problems have a clear cause and a direct fix. This guide walks through a systematic speed audit — identifying exactly what is slowing your site down and how to fix each issue in order of impact.
How to measure your current speed
Before fixing anything, establish a baseline. Run these three tools and save the results so you can measure improvement:
- Google PageSpeed Insights (pagespeed.web.dev) — the most important tool. Shows your Core Web Vitals scores and specific recommendations, separated by mobile and desktop
- GTmetrix (gtmetrix.com) — waterfall chart showing every resource that loads, in order. Essential for identifying which specific files are the bottleneck
- WebPageTest (webpagetest.org) — test from multiple global locations. Shows how your site performs for visitors in different countries
Google uses mobile-first indexing — your mobile performance is what affects rankings. Always run your speed tests from the mobile setting in PageSpeed Insights, not just desktop. A site that scores 90 on desktop and 45 on mobile has a serious problem that most people miss.
Audit layer 1 — Your hosting
Time to First Byte (TTFB) is the time from the browser sending a request to receiving the first byte of response. It is entirely determined by your server. Check your TTFB in GTmetrix under the Waterfall tab — look at the first row and find the ‘Waiting (TTFB)’ time.
| TTFB range | Verdict | Action |
|---|---|---|
| Under 200ms | Excellent | Your hosting is not the bottleneck |
| 200–600ms | Acceptable | Enable page caching if not already active |
| 600ms–1.5s | Poor | Upgrade hosting tier or switch to managed WordPress hosting |
| Over 1.5s | Critical | Hosting is your primary bottleneck — switching hosts should be your first action |
If your TTFB is above 600ms, no amount of plugin-level optimisation will get you to a fast site. The server is the foundation — optimise it first.
Audit layer 2 — Your theme
Your active theme determines how much CSS and JavaScript loads on every page. A feature-heavy theme (Avada, The7, Enfold) can add 500KB–2MB of assets to every page load. Test the theme’s impact:
Go to Appearance → Themes and activate Twenty Twenty-Four. Run a PageSpeed test. If your score improves dramatically, your theme is a major bottleneck.
Install the Query Monitor plugin. Load any page on your site. The Queries tab shows you which assets are being enqueued and by what. Identify scripts and styles added by your theme that you do not use.
If your current theme adds more than 200KB of unused CSS and JS, switching to Astra, GeneratePress, or Kadence — and rebuilding your design with Elementor or Gutenberg — will deliver the largest single speed improvement you can make.
Audit layer 3 — Your plugins
Every active plugin has the potential to add database queries, JavaScript, and CSS to your pages. Some add negligible overhead; others are significant.
With Query Monitor active, check the Queries tab on different page types. Look for plugins running 20+ queries per page or long-duration queries (over 100ms).
Use Asset CleanUp Pro to see which scripts and stylesheets each plugin loads, and on which pages. Disable scripts on pages where they are not needed (e.g., a contact form plugin loading on every page when forms only appear on the Contact page).
For each non-essential plugin, deactivate it and run a PageSpeed test. This identifies which specific plugins have a measurable speed impact. Remove or replace heavy plugins with lighter alternatives.
Common replacements: use CSS-only solutions instead of jQuery-dependent plugins; replace all-in-one plugins with specific single-purpose ones; remove unused social sharing, slider, and animation plugins.
Audit layer 4 — Images
Use GTmetrix’s Waterfall tab to sort assets by file size. Images are almost always the largest resources. For each large image:
- Check if it is actually needed at that size — a 1200px image in a 400px column is wasting 3× the data
- Check its format — JPEG or PNG files should be converted to WebP
- Check its compression — run it through Squoosh and compare file sizes at 80% WebP quality
- Check if it has lazy loading — images below the fold should have
loading="lazy"
Audit layer 5 — Third-party scripts
Third-party scripts — chat widgets, advertising tags, social media embeds, video players — are often the most impactful cause of poor INP (Interaction to Next Paint) scores. They run on your page but on someone else’s server, and you have limited control over their performance.
- Open GTmetrix and look at the Waterfall — any request to a domain that is not your own is a third-party request
- Use WP Rocket’s ‘Delay JavaScript Execution’ to defer third-party scripts until after the page is interactive
- Replace heavyweight embeds with facade elements — a YouTube thumbnail that only loads the full player on click
- Remove any third-party script you cannot justify. Every unneeded script is a performance tax on every page load
Fix hosting first. Fix your theme second. Fix plugins third. Fix images. Then address third-party scripts.
Most WordPress sites have 2–3 major bottlenecks rather than 10 small ones. The GTmetrix waterfall will show you exactly where your time is going. Fix the biggest items first — a 1-second improvement from switching hosts delivers more than ten 100ms plugin optimisations combined.
Need a professional WordPress speed audit?
Simple Automation Solutions performs systematic WordPress speed audits for businesses worldwide — identifying the specific bottlenecks and fixing them in order of impact.
Frequently asked questions
What is a good WordPress PageSpeed score?+
Google’s recommended thresholds: score of 90+ is Good, 50–89 is Needs Improvement, under 50 is Poor. For Core Web Vitals: LCP under 2.5s, INP under 200ms, CLS under 0.1. Target Good on all metrics on mobile. Most sites require fixing hosting, theme, images, and enabling caching to reach 70+ on mobile — the 90+ range requires more advanced optimisation.
How much does switching to managed WordPress hosting improve speed?+
On average, migrating from shared hosting (Hostinger, Bluehost basic plans) to managed WordPress hosting (Kinsta, WP Engine) improves TTFB by 300–800ms. This translates to a 20–30 point improvement in mobile PageSpeed score on most sites, without any other changes. It is the single biggest speed improvement for sites currently on shared hosting.
Can I speed up WordPress without spending money?+
Yes, significantly. The free tier of WP Rocket (no longer available — use W3 Total Cache free) or LiteSpeed Cache (free) with image compression from Smush free and Cloudflare’s free CDN tier can dramatically improve performance at zero cost. The biggest free improvement is usually image optimisation — reducing your largest images can cut page weight by 40–60% with no tools required beyond Squoosh.
