Essential WordPress Performance Checklist: 20 Steps to Faster Site

If your WordPress site feels slow, you’re losing visitors and rankings. I’ve put together a 20-step checklist that covers the essentials. It’s not about theory—each step is something you can implement today.

1. Enable Page Caching

Caching stores a static version of your pages so the server doesn’t rebuild them for every visitor. Most performance plugins (like WP Rocket, W3 Total Cache, or LiteSpeed Cache) offer one-click caching. I recommend starting with page caching before anything else. It’s the biggest bang for your effort.

If you’re new to caching, read my Beginner’s Guide to WordPress Caching to understand the basics. Then enable page caching and test using browser incognito mode.

2. Set Up Object Caching

Object caching stores database query results in memory (like Redis or Memcached). It reduces repeated queries for the same data. Many hosts offer it natively. If yours doesn’t, a plugin like Redis Object Cache can help. This step especially helps if your site uses a lot of custom queries or WooCommerce.

3. Optimize Images

Large images are one of the biggest speed killers. Use a plugin like ShortPixel or Imagify to automatically compress and resize images on upload. Serve next-gen formats like WebP where possible. Also, set explicit width and height attributes to avoid layout shifts—that’s a Core Web Vitals requirement.

4. Implement a CDN

A CDN (Content Delivery Network) stores your static files on servers around the world and delivers them from the one closest to your visitor. This cuts latency significantly. How to Configure CDN for WordPress: Step-by-Step Guide walks you through the whole setup. CDNs like Cloudflare have free tiers that work well.

5. Minify CSS, JavaScript, and HTML

Minification removes unnecessary characters (spaces, comments, line breaks) from your code files. Most caching plugins include this feature. Be careful with JavaScript—reordering can break functionality. Test thoroughly after enabling minification.

6. Defer or Async JavaScript

Defer and async tell the browser to load JavaScript without blocking the page render. Use defer for most scripts (they execute in order after parsing) and async for independent scripts like analytics. This improves render-blocking resources, a key metric in PageSpeed Insights.

7. Eliminate Render-Blocking Resources

CSS and JS at the top of your page can block the browser from painting content. Inline critical CSS and load the rest asynchronously. WP Rocket and similar tools automate this. Reducing render-blocking files is one of the highest-impact changes you can make.

8. Optimize Your Database

WordPress accumulates post revisions, spam comments, transients, and unused tables. Clean them regularly using a plugin like WP-Optimize or Advanced Database Cleaner. I recommend doing this monthly. A lean database means faster queries.

9. Use a Performance-Minded Theme

Not all themes are built equal. Avoid multi-purpose page builder themes with tons of shortcodes. Look for lightweight themes like GeneratePress, Astra, or Kadence. If you’re attached to your current theme, audit its page size with a tool like GTmetrix.

10. Audit Your Plugins

Every plugin adds code and possibly database queries. Deactivate and delete plugins you don’t need. For essential plugins, check their performance impact using Query Monitor or a similar profiling tool. Watch out for plugins that load scripts on every page when they only need a few.

11. Lazy Load Images and Videos

Lazy loading means images and videos only load when they scroll into view. This reduces initial page weight and speeds up first paint. Most caching plugins include this, or you can use a dedicated plugin like Lazy Load by WP Rocket.

12. Optimize the Critical Rendering Path

The critical rendering path is what the browser must do before showing anything. Keep your HTML lightweight, inline above-the-fold CSS, and defer non-critical resources. This directly impacts Largest Contentful Paint (LCP).

13. Use HTTP/2 or HTTP/3

HTTP/2 allows multiple requests over a single connection, reducing latency. Most modern hosts and CDNs support it. Check your site with a tool like KeyCDN’s HTTP/2 Test. If your server still runs HTTP/1.1, ask your host to upgrade.

14. Enable Gzip or Brotli Compression

Compression reduces the size of files sent from your server to the browser. Brotli is more efficient than Gzip but not all servers support it. Check your response headers to see which is active. Many CDNs handle this automatically.

15. Set Proper Cache Headers

Cache headers tell the browser how long to keep files locally. Set long cache lifetimes for static assets (CSS, JS, images) but shorter ones for HTML. If you change assets often, use versioning (e.g., style.css?v=2) to bust caches.

16. Reduce External HTTP Requests

External scripts (fonts, analytics, ads, social widgets) add round trips. Self-host fonts when possible. Consider delaying non-critical third-party scripts. Tools like Perfmatters let you control when scripts load.

17. Enable Keep-Alive

Keep-Alive allows multiple requests over the same TCP connection, reducing overhead. Most servers have it on by default, but it’s worth checking. In Apache, this is the KeepAlive On directive.

18. Fix Cumulative Layout Shift (CLS)

CLS happens when elements shift after the page loads. Common causes: images without dimensions, late-loading ads, and web fonts. Always set explicit sizes for images and embeds. If you’re using Google Fonts, consider preloading or using font-display: swap.

19. Monitor Core Web Vitals

Google’s Core Web Vitals—LCP, FID, CLS—are ranking factors now. Use Google Search Console’s Core Web Vitals report and tools like PageSpeed Insights to track them. Aim for LCP under 2.5 seconds, FID under 100 ms, and CLS under 0.1.

20. Regular Performance Audits

Performance isn’t a one-time fix. Run a full audit every month. Tools like GTmetrix, PageSpeed Insights, and WebPageTest give you actionable reports. Compare before and after changes to see what works. Keep a log of changes so you can backtrack if something breaks.

This checklist covers the fundamentals. Start with caching and images—they give the quickest wins. Then work through the rest. Avoid common pitfalls by reading about 5 Common WordPress Caching Mistakes and How to Fix Them. Every site is different, so test each change. Your visitors will thank you with lower bounce rates and better engagement.

Frequently asked questions

What is the most important step in a WordPress performance checklist?

Enabling page caching is typically the most impactful step. It reduces server load and delivers static HTML to visitors, cutting load times significantly. Combine it with image optimization and a CDN for the best results.

How often should I optimize my WordPress database?

I recommend cleaning your database at least once a month. Remove post revisions, spam comments, and expired transients. Regular maintenance keeps queries fast and prevents database bloat from slowing down your site.

Do I need a CDN for a small WordPress site?

Even small sites benefit from a CDN. It reduces latency for visitors far from your server and offloads static file delivery. Free CDNs like Cloudflare are easy to set up and can immediately improve your PageSpeed Insights scores.

How do I know if my plugins are slowing down my site?

Use a profiling plugin like Query Monitor. It shows database queries, PHP warnings, and script enqueues per page. Identify plugins that load heavy assets or run many queries on every page. Deactivate or replace them.

What is render-blocking resources and how do I fix it?

Render-blocking resources are CSS and JavaScript files that the browser must download before painting the page. To fix them, inline critical CSS above the fold, defer or async JavaScript, and load non-critical CSS asynchronously. Many caching plugins automate this.