How do you speed up a WordPress site?
To speed up a WordPress site, start with fast hosting on a current PHP version, add page caching and a CDN, compress images into WebP or AVIF, remove unused plugins, and trim CSS and JavaScript. Then measure Core Web Vitals in PageSpeed Insights and fix the slowest template first.
WordPress is not slow by default. Sites become slow through cheap hosting, heavy page builders, dozens of plugins and uncompressed images. The good news is that most of these problems are fixable without a rebuild.
This guide covers 14 fixes in order of impact. It updates our original checklist for 2026, with changes such as Interaction to Next Paint, native AVIF support and speculative loading in WordPress core.
Why does WordPress site speed matter in 2026?
Site speed matters because it shapes user experience, conversions and search visibility. Google uses Core Web Vitals as part of its page experience signals, and slow pages are harder for crawlers and AI systems to fetch and process.
Google's Core Web Vitals guidance recommends good scores for success in Search. The three metrics and their "good" thresholds, per web.dev, are:
| Metric | Measures | Good threshold |
|---|---|---|
| Largest Contentful Paint (LCP) | Loading speed | 2.5 seconds or less |
| Interaction to Next Paint (INP) | Responsiveness | 200 milliseconds or less |
| Cumulative Layout Shift (CLS) | Visual stability | 0.1 or less |
INP replaced First Input Delay as a Core Web Vital in March 2024, as web.dev announced. Many WordPress sites that passed the old test now fail INP because of heavy JavaScript.
Speed alone will not make weak content rank. But between two useful pages, the faster one gives users, and crawlers, less reason to leave.
How do you measure WordPress speed before changing anything?
Measure first with PageSpeed Insights, which shows real-user Core Web Vitals data from Chrome users plus a lab test from Lighthouse. Test your homepage, a blog post and a product or service page, because each template behaves differently.
Record a baseline for mobile and desktop. Focus on the field data at the top of the report when it exists. It reflects real visitors over the past 28 days. The lab score below it is useful for debugging but is not what Google uses.
Also check:
- Search Console's Core Web Vitals report for groups of failing URLs.
- Time to First Byte (TTFB), which reveals hosting and caching problems.
- Page weight and request count in the browser's network tab.
Change one thing at a time and retest. That way you know which fix actually helped. It also protects you from plugins that promise speed but break layouts.
Which hosting and server fixes make the biggest difference?
Hosting and server setup make the biggest difference because every other fix sits on top of them. A slow server produces a slow TTFB that no plugin can hide. Move to quality managed or VPS hosting and run a current PHP version.
1. Use fast hosting. Shared hosting that crowds hundreds of sites onto one server often produces TTFB above one second. Managed WordPress hosts or a well-configured VPS usually respond far faster.
2. Upgrade PHP. WordPress.org's requirements page recommends PHP 8.3 or greater and MySQL 8.0 or MariaDB 10.11 or greater. Check PHP's supported versions list; unsupported versions stop receiving security fixes. Test on staging first, since old plugins can break.
3. Enable object caching. A persistent object cache such as Redis or Memcached stores database query results in memory. It helps most on WooCommerce, membership and logged-in sites where page caching cannot apply.
4. Serve over HTTP/2 or HTTP/3. Modern protocols load many small files in parallel. Most good hosts and CDNs enable them automatically.
How do caching and a CDN speed up WordPress?
Caching speeds up WordPress by serving a saved HTML copy of each page instead of rebuilding it with PHP and database queries on every visit. A CDN then delivers that copy, plus images and scripts, from servers close to each visitor.
5. Add page caching. WordPress's own caching documentation explains the options. Many hosts include server-level caching. Otherwise, a single caching plugin such as WP Rocket, LiteSpeed Cache or W3 Total Cache will do. Never run two page-caching plugins together.
6. Use a CDN. Services like Cloudflare, Bunny or your host's built-in CDN reduce latency for visitors far from your server. Full-page caching at the edge can cut TTFB dramatically for anonymous visitors.
7. Set browser caching and compression. Static files should carry long cache lifetimes. Text files should be compressed with Brotli or Gzip. Most caching plugins and CDNs handle both.
Remember to exclude cart, checkout and account pages from page caching on WooCommerce stores. Caching them causes users to see stale or wrong data.
How should you optimise images on WordPress?
Optimise WordPress images by resizing them to the size they display at, compressing them, and serving modern formats such as WebP or AVIF. Also make sure the main above-the-fold image loads early and is never lazy-loaded.
8. Compress and convert images. WordPress has supported WebP for years, and WordPress 6.5 added AVIF support when the server supports it. The core team notes AVIF can be much smaller than JPEG at similar quality. You can also compress files before uploading with our free image compressor.
Other image rules that help Core Web Vitals:
- Upload images no wider than your content area needs.
- Always keep width and height attributes, so the browser reserves space and avoids layout shift.
- Let WordPress lazy-load below-the-fold images, which it does by default.
- Exclude the hero or featured image from lazy loading. It is usually the LCP element.
- Offload large video to YouTube, Vimeo or a media host instead of your server.
How do you reduce CSS, JavaScript and plugin bloat?
Reduce bloat by removing plugins you do not need, loading scripts only on pages that use them, and deferring non-critical JavaScript. Heavy JavaScript is the main cause of poor INP scores on WordPress sites.
9. Audit plugins. The number of plugins matters less than what they load. One slider plugin that adds scripts sitewide can cost more than ten lightweight utilities. Deactivate each suspect plugin on staging and measure the difference.
10. Use a lightweight theme. Block themes and lean themes like GeneratePress, Kadence or Astra ship far less code than bloated multipurpose themes. Heavy page builders add wrappers, CSS and JavaScript to every page.
11. Optimise CSS and JavaScript. Minify files, remove unused CSS, and defer or delay non-essential scripts such as chat widgets, heatmaps and social embeds. Test carefully, because over-aggressive delay can break menus and forms.
12. Use speculative loading. WordPress 6.8 added speculative loading to core. It prefetches likely next pages so navigation feels near-instant, with conservative defaults.
How do you clean up the WordPress database?
Clean up the database by limiting post revisions, deleting spam and trashed comments, clearing expired transients and removing tables left behind by uninstalled plugins. A lean database keeps queries fast, especially on older sites and stores.
13. Limit revisions. WordPress stores every saved revision by default. You can cap them with the WP_POST_REVISIONS constant in wp-config.php, as described in the official wp-config documentation. A limit of five to ten revisions is plenty for most sites.
14. Optimise tables and autoloaded options. Large autoloaded options in the wp_options table load on every request. Tools like WP-Optimize or Query Monitor help you find oversized entries left by old plugins.
Other quick wins:
- Paginate or lazy-load long comment threads.
- Disable pingbacks and trackbacks.
- Schedule cleanups monthly rather than running them daily.
Always take a full backup before database cleanup. A single wrong deletion can break a site, so test changes on staging first.
When should you get professional help with WordPress speed?
Get professional help when you have tried caching, image compression and plugin cleanup but still fail Core Web Vitals, or when speed problems come from the theme, page builder or custom code. These issues usually need a developer, not another plugin.
Signs you need a deeper fix:
- TTFB stays high even with caching enabled.
- INP fails because of theme or builder JavaScript.
- WooCommerce checkout is slow for logged-in users.
- Speed plugins conflict and break layouts.
Sometimes the right answer is a lighter rebuild. Moving from a heavy page builder to a custom block theme can remove most of the bloat at once. Meek Media's WordPress development team handles speed audits and rebuilds, and every quote is custom after a free audit.
Frequently asked questions
What is a good page load time for WordPress?
Aim for a Largest Contentful Paint of 2.5 seconds or less on mobile, the threshold Google's web.dev guidance defines as good. Also target an INP of 200 milliseconds or less and a CLS of 0.1 or less. Real-user field data in PageSpeed Insights is the most reliable way to judge this.
Why is my WordPress site so slow?
The most common causes are slow shared hosting, an outdated PHP version, no page caching, oversized images, and heavy themes or plugins that load large scripts on every page. Measure TTFB first. If it is high, fix hosting and caching before anything else.
Do more plugins always make WordPress slower?
Not always. What matters is what each plugin loads and when. A handful of poorly coded plugins that add sitewide scripts or heavy database queries can slow a site far more than many small, well-built ones. Test plugins individually on staging to find the real culprits.
Which caching plugin is best for WordPress?
The best caching plugin depends on your host. LiteSpeed Cache suits LiteSpeed servers, while WP Rocket and W3 Total Cache work on most setups. Many managed hosts include server-level caching and recommend no extra plugin. Use only one page-caching solution to avoid conflicts.
Does WordPress speed affect AI search visibility?
Indirectly, yes. AI systems and search crawlers must fetch and process your pages, and fast, server-rendered pages are easier to retrieve reliably. Google also counts AI Overview visibility within normal Search, where page experience remains part of its ranking systems. Speed supports visibility; content quality still decides it.
Is it worth switching from a page builder to speed up WordPress?
Often, yes, if the builder is the main source of bloat. Page builders add extra markup, CSS and JavaScript to every page. Rebuilding key templates with a lightweight or block theme can dramatically improve Core Web Vitals. Test a single template first to confirm the gain.