WordPress Site Speed: The First Ten Things To Check

WordPress site speed problems usually trace to a small set of common causes. Before reaching for deep diagnostic tools, ten quick checks identify the most frequent issues. The checks take 30 minutes total and resolve most speed problems on most sites.

The sequence assumes basic familiarity with the WordPress admin and the browser DevTools. No specialized tools required beyond what's already on most computers.

Check 1: hosting tier appropriateness

Quick assessment of whether your hosting matches your site's needs. Check current monthly visits and compare against your hosting tier's typical capacity.

If you're on entry-tier shared hosting with 100,000+ monthly visits, the hosting is the constraint. Upgrade before further optimization work.

If you're on adequate hosting but performance is still poor, hosting isn't the issue; continue to other checks.

Check 2: caching plugin activation

Open the WordPress admin Plugins page. Verify a caching plugin is installed and active (WP Rocket, LiteSpeed Cache, W3 Total Cache, or similar). If your hosting has built-in caching (Kinsta, WP Engine, SiteGround SuperCacher), verify it's enabled.

No caching is the most common single cause of slow WordPress. The fix is installing or enabling caching, which produces immediate dramatic improvement.

Check 3: image optimization status

Right-click any image on your homepage and choose "Save image." Check the file size. A 1.5MB image in the page is a problem. A 100KB image is appropriate for most contexts.

If images are unoptimized, install an image optimization plugin (ShortPixel, Imagify, Smush). Bulk-optimize existing images. New uploads will be optimized automatically going forward.

Check 4: plugin count audit

Count active plugins. Under 15: probably fine. 15-25: some review warranted. Over 25: high likelihood of plugin-related slowdowns.

For sites with many plugins, identify which ones are essential. Deactivate non-essential plugins temporarily to test impact. The plugins you don't actively need can usually be removed.

Check 5: theme weight

Open the homepage in browser DevTools, Network tab. Reload. Look at the total transferred size. Under 1MB: good. 1-2MB: acceptable. Over 2MB: heavy.

If your theme is heavy, the theme's CSS and JavaScript are usually the largest contributors. Switching to a lighter theme produces dramatic improvement but is a significant project.

Check 6: render-blocking resources

Run PageSpeed Insights on your homepage. Look at the "Eliminate render-blocking resources" section. The list shows CSS and JavaScript files that block initial rendering.

The fix is your caching plugin's CSS/JS optimization features: combine, minify, defer JavaScript, preload critical resources. Most caching plugins handle this with appropriate settings.

Check 7: database size

If you have phpMyAdmin or database access, check the size of your WordPress database. Under 100MB: typical for content sites. 200-500MB: large but acceptable. Over 1GB: investigate.

Large databases often have accumulated bloat: old revisions, expired transients, spam comments, orphaned data. Database cleanup with a plugin like WP-Optimize can recover space and improve query performance.

Check 8: CDN status

Open the page source on your homepage. Look at the image URLs. Do they reference your domain (slow if visitors are far from your origin) or a CDN domain (faster for distant visitors)?

If no CDN is configured, enable Cloudflare's free tier. The setup takes 30 minutes; the improvement is significant for international visitors.

Check 9: PHP version

Your hosting control panel or a plugin like Display PHP Version shows the PHP version. PHP 8.2 or 8.3 in 2026: appropriate. PHP 7.4 or earlier: outdated and slower.

Upgrading PHP often produces 20-40% speedup with no other changes. The upgrade is usually a one-click operation in modern hosting control panels.

Check 10: error log review

Check the error log (WordPress's debug.log if WP_DEBUG_LOG is enabled, or the server's error log). Errors and warnings can indicate problems that affect performance.

Frequent PHP warnings, database errors, or plugin errors might be causing slowdowns. Resolving the errors often improves performance.

The diagnostic priority

After running through the checks, identify which issues are most significant. The fixes that typically produce the largest impact:

1. Hosting upgrade if grossly underpowered (large improvement when applicable)

2. Caching plugin installation if not present (large improvement)

3. Image optimization if images are unoptimized (large improvement)

4. Plugin trimming if plugin count is excessive (moderate improvement)

5. PHP version upgrade (moderate improvement)

6. CDN enablement (moderate improvement for international audiences)

7. Theme switch if theme is genuinely heavy (large improvement but significant project)

The other checks identify smaller issues that compound. Fixing them in aggregate produces meaningful improvement even if no single fix is dramatic.

The validation

After making changes, re-run PageSpeed Insights and compare scores. Document the improvements: which changes produced what gains.

The discipline of measurement prevents accidentally degrading performance. Some "optimizations" produce no improvement or actively hurt. Measurement catches this.

The cases where the ten checks aren't enough

Sites with complex custom code that has specific bottlenecks. The standard checks don't reveal these; deeper diagnostic work (database query profiling, PHP profiling) is needed.

Sites with unusual usage patterns. A site with many AJAX requests, complex search, real-time updates may have performance issues that the standard checks don't catch.

Sites already optimized to standard practices but still slow. The remaining issues are usually specific to the site's architecture and need custom investigation.

For these cases, professional performance audits or specialized tools (Query Monitor, New Relic, Datadog) provide the deeper diagnostics.

The honest framing

The ten quick checks resolve performance issues on most WordPress sites. The pattern of cumulative small problems is more common than dramatic single causes.

The investment is 30 minutes for the checks plus a few hours for implementing the fixes. The result is typically 30-60% page speed improvement.

For sites that haven't been performance-audited recently, the checks identify wins that have been waiting. The audit and fix cycle is repeatable: quarterly review keeps the site at performant baseline.