How to Speed Up a WordPress Website:A Practical Checklist

To speed up WordPress, work in this order: measure, make sure pages are cached, fix images, remove heavy plugins and scripts, clean the database, and only then consider more powerful hosting. Most slow WordPress sites are slowed by one or two specific causes, and fixing those beats installing several "speed" plugins.

Here is the checklist, in the order that usually gives the biggest gain for the least effort.

1. Measure first

Test a few important pages (home, a typical post or product, and a page with a form) with PageSpeed Insights and your browser's developer tools. Record:

• Time to First Byte (TTFB), which shows server-side speed;
• Largest Contentful Paint (LCP), Interaction to Next Paint (INP) and Cumulative Layout Shift (CLS), the Core Web Vitals;
• total page weight and the number of requests.

High TTFB points to the server, PHP or database; good TTFB with poor LCP points to images, fonts and scripts. The method is explained in why is my website slow.

2. Make sure pages are cached

A full-page cache is the single largest improvement for most sites.

• If your host runs LiteSpeed, use the LiteSpeed Cache plugin; see how to configure LiteSpeed Cache for WordPress.
• Otherwise use your host's server cache or one well-maintained caching plugin.
• Use only one page-caching solution.
• Confirm caching works: the second load of a page should show a cache hit in the response headers and a much lower TTFB.

Logged-in pages, carts and checkouts are not page-cached. For those, a persistent object cache helps; see Redis object caching explained.

3. Fix images

Images are usually the heaviest part of a page.

• Resize images to the largest size they are displayed at.
• Compress them and serve WebP or AVIF.
• Let WordPress add srcset so phones get smaller versions.
• Lazy-load images below the fold, but not the main hero image, which should load immediately.

Details are in WordPress image optimization.

4. Audit plugins

• List every active plugin and ask whether you need it.
• Remove plugins that duplicate features (two SEO plugins, two security plugins).
• Watch for known heavy categories: related-post plugins that run expensive queries, statistics plugins that write on every visit, social feeds, and sliders.
• To find the slowest plugin, deactivate plugins one at a time on a staging copy and measure.

5. Reduce front-end weight

• Use a lightweight theme, or limit page-builder widgets and add-ons. Page builders are covered in speeding up an Elementor website.
• Limit web fonts to the families and weights you use, and self-host them.
• Delay or remove third-party scripts you do not need: chat widgets, heat maps, extra tracking tags.
• Load YouTube videos and maps only when the visitor clicks.
• Test CSS/JS minification and deferral carefully; enable one option at a time and check the layout.

6. Clean up the database

Over time WordPress collects post revisions, expired transients, spam comments and leftovers from deleted plugins. The wp_options table can also fill with autoloaded data loaded on every request. See WordPress database optimization. Always take a backup first.

7. Replace WP-Cron on busy sites

By default, WordPress checks scheduled tasks on page loads. On busy sites, set DISABLE_WP_CRON to true in wp-config.php and run wp-cron.php from a real cron job every five or ten minutes.

8. Keep PHP and software current

Newer PHP versions are generally faster. Keep WordPress, themes and plugins updated too. See which PHP version should your website use.

9. Use a CDN if visitors are spread out

A CDN serves static files from locations near your visitors and reduces load on your server. It helps most when your audience is geographically spread or traffic is spiky.

10. Upgrade hosting when the data says so

If uncached TTFB stays high after all of the above, or resource limits are reached regularly by real traffic, the hosting is the bottleneck. See WordPress hosting: what it is and how to choose.

Quick checklist

• Baseline measurements recorded
• One page cache active and verified
• Images resized, compressed and in modern formats
• Unneeded plugins removed
• Fonts and third-party scripts reduced
• Database cleaned (after a backup)
• WP-Cron moved to a real cron job on busy sites
• Current PHP version
• Re-measured after each change

Frequently Asked Questions

What is a good PageSpeed score for WordPress?

Focus on Core Web Vitals passing for real users (field data) rather than chasing a perfect lab score. A score in the 80s or 90s with good field data is excellent.

Do I need several speed plugins?

No. Usually one caching solution and an image optimisation approach are enough. Several overlapping optimisation plugins often conflict.

Will a faster host fix everything?

Only server-side delays. Heavy images, scripts and fonts are slow on any host.

Related reading

This checklist sits within the wider WordPress guide; start with WordPress hosting: what it is and how to choose, and compare ServerNeed WordPress hosting.

Sources

• WordPress Developer Resources: Optimization
• web.dev: Web Vitals