The short answer
A slow WordPress site almost always comes down to one of a handful of causes: no caching, underpowered hosting, an outdated PHP version, a heavy theme or page builder, too many plugins, or oversized images. WordPress itself is rarely the problem. The fix depends on which of these you have, and guessing tends to end with a stack of “speed” plugins that make things worse.
This article walks through how to measure the problem properly, then the causes in the order worth checking them.
First, measure the right thing
Before changing anything, find out how slow the site actually is, and for whom.
Use field data, not just a score. Google’s PageSpeed Insights shows two kinds of results. The top section, when your site has enough traffic, is field data: how real visitors’ page loads performed over the previous 28 days. The section below it is lab data, a simulated load on one device and one network, which Google describes as useful for debugging (PageSpeed Insights documentation). When the two disagree, the field data is what your visitors experienced.
Don’t chase the 0–100 number. The lab score moves between runs for reasons that have nothing to do with your site: network routing, browser extensions, even antivirus software. Google’s own documentation suggests treating performance “as a distribution of scores, rather than a single number” (Lighthouse performance scoring).
Know the three thresholds that matter. Google’s Core Web Vitals define a good experience as the main content appearing within 2.5 seconds (Largest Contentful Paint), the page responding to a tap or click within 200 milliseconds (Interaction to Next Paint), and a layout shift score of 0.1 or less (Cumulative Layout Shift), measured at the 75th percentile of page loads, with mobile and desktop assessed separately (web.dev).
Test more than the homepage. The homepage is often the most polished page on the site. Test a service page, a blog post, and anything with a form or a gallery. If only one template is slow, the cause is on that template, not the server.
The usual causes, in the order to check them
1. No page caching
Without caching, WordPress builds every page from scratch on every visit: it runs PHP, queries the database, and assembles the HTML. WordPress’s own performance documentation is blunt about this: without a caching solution, “performance will slow to a halt” under load (WordPress optimization guide).
Many hosts include server-level caching. If yours doesn’t, one well-configured caching plugin is usually the single biggest improvement available. One, not three: stacked caching and “optimization” plugins conflict with each other and are a common cause of broken layouts.
Tell-tale sign: the server takes a second or more before anything starts loading, on every page.
2. Hosting that can’t keep up
The cheapest shared hosting plans put many sites on one server with limited CPU and memory. WordPress’s documentation notes that paying for a higher service level “can be very effective” (WordPress optimization guide). That doesn’t mean expensive hosting fixes a badly built site. It means a well-built site can still be held back by a server that’s overloaded.
Tell-tale sign: speed varies a lot by time of day, or the admin area is slow even when you’re the only person using it.
3. An outdated PHP version
PHP is the language WordPress runs on, and newer versions are generally faster. WordPress currently recommends PHP 8.3 or greater (WordPress requirements). As of October 2026, PHP 8.2 receives security fixes only until the end of 2026, and anything older no longer receives them at all (PHP supported versions).
Changing PHP version is usually a setting in the hosting control panel, but it isn’t a blind switch: old themes and plugins can break on a newer version. Test on a staging copy first, with a backup in hand.
Tell-tale sign: the hosting panel or the WordPress Site Health screen flags the PHP version as outdated.
4. A heavy theme or page builder
Multipurpose themes and drag-and-drop page builders load code for every feature they offer, whether a page uses it or not. A simple service page can end up loading sliders, animation libraries, icon fonts, and several stylesheets it never needed. Caching helps the server side of this, but the visitor’s browser still has to download and run all of it, which is why these sites often look fine in a lab test on a fast connection and feel sluggish on a phone.
This is the cause owners most often can’t fix with settings. Sometimes trimming what the builder loads helps enough. Sometimes the honest answer is that the theme is the problem.
Tell-tale sign: pages are slow even with caching on, and the PageSpeed report lists large amounts of unused JavaScript and CSS.
5. Too many plugins, or the wrong ones
The number of plugins matters less than what each one does. A plugin that adds a small settings screen costs almost nothing. A plugin that loads its own scripts on every page, or runs heavy database queries, can cost a lot. WordPress’s guidance is to deactivate and delete anything unnecessary, and to find a slow one by disabling plugins one at a time (WordPress optimization guide). Do that on a staging copy, not on the live site during business hours.
Common offenders: sliders, social-feed widgets, chat widgets, multiple form plugins, and analytics or tracking scripts added through several different plugins.
Tell-tale sign: the site got slower gradually, as features were added.
6. Oversized images
A photo straight off a phone or camera can be several megabytes. Uploaded as-is and displayed at a few hundred pixels wide, it is one of the most common reasons a page’s main content appears late. Resize images before uploading, compress them, and use a modern format such as WebP where possible, which the WordPress documentation also recommends (WordPress optimization guide).
Tell-tale sign: the slow pages are the ones with large photos, and the PageSpeed report points to an image as the Largest Contentful Paint element.
7. A cluttered database
Years of post revisions, leftover data from deleted plugins, and settings that load on every request all add up. WordPress’s documentation singles out “autoloaded options” (settings loaded on every page) as something to keep small (WordPress optimization guide). This is rarely the first problem on a young site and often a real one on a site that has been running, and accumulating plugins, for many years.
Tell-tale sign: the admin area is slow, especially saving posts or loading lists.
What doesn’t usually help
- Installing more speed plugins. Each one adds code and the chance of conflicts. Fix the cause instead.
- Chasing a perfect lab score. A 100 on a desktop lab test says little about a visitor on a phone in a parking lot.
- Moving hosts first. If the theme and plugins are the problem, they move with the site.
Does speed affect your Google rankings?
Somewhat, and it’s worth being precise. Google says good Core Web Vitals align with what its ranking systems reward, but also that it “always seeks to show the most relevant content, even if the page experience is sub-par” (Google Search Central). A faster site removes a drag. It won’t outrank a more relevant page on speed alone.
The stronger reason to fix it is the people using the site. A visitor who waits for a phone number to appear, or taps a button that doesn’t respond, may simply go back to the search results and call someone else.
Fix it, or rebuild?
If the cause is caching, hosting, PHP, images, or a few bad plugins, fixes are almost always cheaper than a rebuild. If the site is built on a page builder that loads everything everywhere, and every change fights it, a rebuild on a lean custom theme can cost less over the next few years than continuing to patch it. Whether WordPress is still the right platform at all is covered in is WordPress still a good choice for a business website?
Webbify’s WordPress website design work starts with a review that says which of those two you’re facing, and recommends the smaller option when it fits. Speed problems that cross into crawling, indexing, and Core Web Vitals across many templates are part of technical SEO. And keeping a site fast after it’s fixed, with updates, backups, and someone checking, is what website care is for.