WordPress Speed Optimization: Full Checklist

By Amit Patel

WordPress speed work has a natural priority order — hosting quality first, then caching, then everything else — because no amount of plugin-level optimization compensates for underpowered hosting, and no amount of image compression matters if pages aren’t being cached at all. This checklist follows that order.

Hosting Quality Comes First

Shared hosting with oversold server resources will bottleneck a site no caching plugin can fully compensate for — checking actual server response time (Time to First Byte) under normal load is a better first diagnostic than jumping straight to plugin-level fixes. Managed WordPress hosts generally provide more consistent performance than budget shared hosting specifically because server resources aren’t shared as thinly.

Caching

Whether through a plugin or a host’s built-in layer, page caching is the single highest-leverage speed change available — it eliminates repeated PHP execution and database queries for the exact same rendered output on every repeat visit. See our cache plugins comparison for the options and when your host’s own caching already covers this.

Images

Unoptimized images are consistently one of the largest contributors to page weight on content sites — compression, next-gen formats like WebP, and CDN delivery each compound with the others. See our image optimization guide for the specific tools and what WordPress core already handles for free.

Font Loading

Web fonts loaded without font-display:swap or fallback, or swapped in after page load without proper handling, cause a visible layout shift as text re-flows — a real, measurable Cumulative Layout Shift (CLS) cost that’s easy to overlook because it doesn’t show up in a raw page-weight audit. This site’s own Font CLS Fix plugin exists specifically because this was found live in a prior audit — preloading the body font and adding it to the font-display override list eliminated the shift.

Database Cleanup

Post revisions, expired transients, and spam comments accumulate in the database over years of active use and can measurably slow down queries on a large, long-running site — periodic cleanup (via a plugin like WP-Optimize, or manual query-based cleanup for advanced users) is a maintenance task worth scheduling rather than a one-time fix.

Plugin Count

Every active plugin adds some amount of PHP execution and, often, additional database queries or enqueued scripts/styles on the front end — the practical guidance isn’t “fewer plugins is always better” but rather auditing for plugins that are inactive-but-installed, redundant with another plugin’s functionality, or loading assets on pages that don’t need them.

Core Web Vitals Priorities

Of the three Core Web Vitals, Largest Contentful Paint (LCP) is most directly affected by hosting and caching, Cumulative Layout Shift (CLS) is most directly affected by font and image-dimension handling, and Interaction to Next Paint (INP) is most affected by heavy, blocking JavaScript — diagnosing which metric is actually failing (via PageSpeed Insights or Search Console’s Core Web Vitals report) should come before applying any specific fix.

Frequently Asked Questions

The Bottom Line

Work the checklist in order — hosting and caching first, then images and fonts, then ongoing database and plugin maintenance — and diagnose the specific failing Core Web Vitals metric before applying a fix.