The fastest way to speed up a WordPress site is to fix things in order of impact: measure with real-user data first, then sort out hosting and PHP, add page caching, shrink images, and only then trim plugins, scripts and fonts. Most slow WordPress sites are slow for two or three reasons, not twenty. Find those reasons before you install another “speed” plugin.
This guide is written for business owners and in-house marketers who want a site that loads quickly for customers on their phones. It explains what to measure, which fixes usually matter most, and which popular tweaks are a waste of time.
Run your homepage and your most important service or product page through Google PageSpeed Insights. The report shows two kinds of results, and they answer different questions.
If your site doesn’t have enough traffic for field data, use the Core Web Vitals report in Google Search Console as it fills in, and use the lab results to find problems. Always test the mobile result, because that’s where most WordPress sites struggle.
| Metric | What it measures | “Good” | Common WordPress cause when it fails |
| Largest Contentful Paint (LCP) | How long until the main content, often the hero image, appears | 2.5 seconds or less | Slow server response, huge hero images, sliders, render-blocking CSS |
| Interaction to Next Paint (INP) | How quickly the page reacts when someone taps or clicks | 200 milliseconds or less | Heavy JavaScript from page builders, chat widgets, tracking tags and pop-ups |
| Cumulative Layout Shift (CLS) | How much the layout jumps while loading | 0.1 or less | Images without set sizes, late-loading banners, web fonts swapping in |
Google assesses these at the 75th percentile of visits, so a page passes when most visitors, not just you on office Wi-Fi, get a good result. INP replaced the older First Input Delay metric in 2024, which is why many older WordPress speed guides don’t mention it.
If your server takes a long time to send the first byte of the page, nothing you do to images or scripts will fully make up for it. In PageSpeed Insights, look for “Reduce initial server response time” or a high Time to First Byte (TTFB) figure.
WordPress runs on PHP, and newer PHP versions are generally faster and better supported. The official WordPress requirements page currently recommends PHP 8.3 or greater, and the WordPress hosting handbook for WordPress 7.0 suggests PHP 8.4 or 8.5 for new installs. PHP 8.2 stops receiving security fixes at the end of 2026. You can see your version under Tools > Site Health > Info > Server. Before switching, take a backup and test on a staging copy, because an old plugin or theme may not support the newer version.
Very cheap shared hosting can be fine for a small brochure site with light traffic. It becomes a bottleneck when your server response is slow even on simple pages, your site slows down at busy times, or you run WooCommerce, memberships or bookings, which can’t be fully page-cached. Signs that an upgrade is worth pricing:
Ask your host whether they offer server-level page caching and an object cache such as Redis. Many managed WordPress hosts include both.
Without caching, WordPress builds each page from the database every time someone visits. A page cache saves a ready-made copy and serves that instead, which usually cuts server response time sharply.
Recent WordPress releases also add some speed help on their own. Since WordPress 6.8, core uses speculative loading by default for logged-out visitors, prefetching pages a visitor is likely to open next so that navigation can feel faster. You don’t need a plugin for that, though caching and optimization plugins may change how it behaves.
On most small business sites, images are the heaviest part of the page. A single 4 MB hero photo straight from a camera can wreck your mobile LCP on its own.
The number of plugins matters less than what each one loads. One poorly built plugin that adds scripts to every page can cost more than ten small ones that only run in the admin area.
Page builders make editing easy but can add a lot of extra code. You don’t have to abandon yours. Turn off builder features and widgets you don’t use, avoid nesting many containers inside each other, and limit animations. If a multipurpose theme loads several icon libraries and demo features, a lighter theme or a custom build may be the cleaner long-term fix.
Chat widgets, heatmaps, review badges, social feeds, video embeds and multiple tracking tags are frequent causes of poor INP. Keep the ones that earn their place, load them after the main content where possible, and remove old tags from tools you no longer use. For YouTube or Vimeo videos, a lightweight “click to play” preview avoids loading the full player on page load.
Some speed advice sounds technical but rarely moves the numbers that matter:
| What you notice | Most likely cause | Try first |
| Every page is slow to start loading | Server response, hosting, no page cache | Check TTFB, enable caching, review hosting and PHP |
| Text appears, then the big image takes ages | Oversized or lazy-loaded hero image | Resize, convert to WebP, load the hero immediately |
| The page looks loaded but taps feel laggy | Heavy JavaScript | Audit chat, tracking and builder scripts |
| Content jumps around while loading | Missing image sizes, late banners, font swaps | Set dimensions, reserve space for banners, limit fonts |
| Only the admin area is slow | Plugins running admin tasks, limited server resources | Plugin audit, object cache, hosting review |
Google confirms that Core Web Vitals are used by its ranking systems, but it also says it will show the most relevant content even if the page experience is weaker. In practice, speed won’t lift a thin page above a genuinely better answer. Where it does matter is when several good pages compete, and in what visitors do after they arrive. A page that loads slowly on mobile gives people time to hit the back button. If your site has traffic but few enquiries, speed is one of the causes covered in our guide on why a website isn’t getting leads.
Speed also isn’t a one-time job. Plugin updates, new tracking tags and fresh uploads can slowly undo your work, which is why speed checks belong in any WordPress maintenance checklist.
Aim to pass Google’s Core Web Vitals in field data: main content visible within 2.5 seconds, responses to taps within 200 milliseconds and very little layout movement. There’s no single “seconds to fully load” target that applies to every site.
The best one is usually the one that matches your host. Many managed hosts have their own caching and recommend a specific plugin or none. Whatever you choose, use only one page caching solution at a time.
Yes, for many of the basics: resizing images, removing unused plugins, turning on your host’s caching and updating PHP with a backup in place. Server tuning, script optimization on page builders and theme changes are easier to get wrong, so use a staging site or get help.
Field data covers a rolling 28-day window, so improvements usually take a few weeks to show fully in PageSpeed Insights and the Search Console Core Web Vitals report.
Our WordPress development service includes technical performance and compatibility tuning, where we reduce bloat and improve load speed while keeping builds update-safe. To keep a site fast after the work is done, our WordPress maintenance plans cover speed hygiene and asset optimisation, staging-based updates and uptime monitoring.
Not sure what is slowing your site down? Contact us with your website address and the pages that matter most.
Talk to our team about your project. Book a free consultation, no obligation.