A slow WordPress site frustrates visitors, hurts your Google rankings and quietly costs you enquiries and sales. The good news: most WordPress speed problems come from the same handful of causes, and fixing them does not require rebuilding your site.
Below is the step-by-step process we use when clients ask us to speed up their WordPress site, in order of impact. If you are new to the metrics, read our Core Web Vitals guide first.
Step 1: Measure before you change anything
Record a baseline so you know what actually helped:
- Google Search Console (Core Web Vitals report) for real-user data across your site.
- PageSpeed Insights for your home page, a blog post and your most important landing page.
- Query Monitor (free plugin) to spot slow database queries and heavy plugins.
Always test on a staging site before changing plugins or themes on a live business website.
Step 2: Fix your hosting
No amount of optimisation can fix a slow server. If your time to first byte (TTFB) is above about 600 ms, hosting is likely your bottleneck.
Look for:
- Managed WordPress or cloud hosting with server-level page caching
- A current version of PHP (older versions are noticeably slower)
- Object caching (Redis or Memcached) for dynamic sites such as WooCommerce stores
- Data centres close to your visitors, or a CDN in front
Step 3: Turn on page caching
Caching serves pre-built HTML instead of running PHP and database queries on every visit. It is usually the single biggest win.
- Use one caching layer, not three. If your host provides server caching, pair it with a lightweight plugin rather than stacking several.
- Popular choices: WP Rocket, LiteSpeed Cache (on LiteSpeed servers) and W3 Total Cache.
- Exclude cart, checkout and account pages on WooCommerce.
Step 4: Use a lightweight theme
Multipurpose themes and heavy page builders often load hundreds of kilobytes of CSS and JavaScript on every page, whether you need it or not.
- Choose a lean theme (GeneratePress, Kadence, Astra or a custom block theme).
- If you use a page builder, enable its performance options and avoid stacking add-on packs.
- Read our take on the pros and cons of page builders.
Step 5: Optimise images properly
Images are usually the heaviest part of a page and the most common cause of slow LCP.
- Resize images to the size they are displayed at; never upload 4000 px photos for an 800 px slot.
- Convert to WebP or AVIF (Imagify, ShortPixel or your CDN can do it automatically).
- Lazy-load images below the fold, but never your hero image.
- Set width and height so the layout does not jump (good for CLS).
Step 6: Audit and reduce plugins
Every plugin can add CSS, JavaScript and database queries. Go through your list and ask:
- Is this plugin still used?
- Does it load files on pages where it is not needed? (Plugins such as Perfmatters or Asset CleanUp can unload them per page.)
- Can one well-built plugin replace three single-purpose ones?
- Is it maintained and compatible with your PHP version?
Sliders, social feeds, related-post plugins and old analytics plugins are frequent offenders. See our list of must-have WordPress plugins for what is actually worth keeping.
Step 7: Minify and defer CSS and JavaScript
- Minify CSS and JavaScript to remove whitespace and comments.
- Defer or delay non-critical JavaScript, especially third-party scripts like chat widgets and heatmaps.
- Generate critical CSS so above-the-fold content renders before the full stylesheet loads.
- Test after every change, since aggressive JavaScript delay can break menus and forms.
Step 8: Optimise fonts
- Use fewer font families and weights; each one is another download.
- Self-host Google Fonts instead of loading them from a third-party server.
- Preload your main font file and use
font-display: swap.
Step 9: Add a CDN
A content delivery network serves your files from servers close to each visitor. Cloudflare, BunnyCDN or your host’s built-in CDN all work well, and Cloudflare can also cache full HTML pages at the edge for even faster responses.
Step 10: Clean up the database
Over time, WordPress collects post revisions, spam comments, expired transients and leftover tables from deleted plugins.
- Limit post revisions in
wp-config.php(for example,define('WP_POST_REVISIONS', 5);). - Clean transients and spam regularly with WP-Optimize or a similar tool.
- Check for autoloaded options bloat, which slows every single page load.
Step 11: Keep everything updated
Updates to WordPress core, PHP and plugins often include performance improvements as well as security fixes. A regular WordPress maintenance routine keeps your site fast and safe.
WordPress speed checklist
- Baseline measured in Search Console and PageSpeed Insights
- Hosting with server caching and a current PHP version
- One page-caching solution configured
- Lightweight theme; page builder tuned or replaced
- Images resized, converted to WebP/AVIF and lazy-loaded below the fold
- Unused plugins removed; assets unloaded where not needed
- CSS/JS minified; third-party scripts delayed
- Fonts self-hosted and preloaded
- CDN enabled
- Database cleaned; revisions limited
- Monthly speed check scheduled
Get your WordPress site fast, without the guesswork
Speed work is fiddly: one wrong setting can break a checkout or a contact form. Our website speed optimization service handles the whole process on a staging copy and reports before-and-after Core Web Vitals, and our WordPress maintenance plans keep it fast month after month. Contact Webyant for a free speed audit.
- wordpress speed
- core web vitals
- website optimization
Jayanti Solanki
Founder, Webyant Technologies
For 17+ years, Jayanti has been turning designers' visions into websites that actually work: pixel-perfect, lightning-fast and built to convert. A Computer Applications honours graduate and certified Shopify Expert, Jayanti founded Webyant in 2016 and now leads a team crafting WordPress, Shopify, Webflow and Next.js websites (and, lately, AI assistants) for brands from Deesa to around the world. On this blog, Jayanti shares the practical, no-fluff lessons learned from shipping 100+ real projects.
Need help with this? Explore our services




