Why is my WordPress site slow?

A WordPress site is slow for one of two reasons: the server takes too long to produce the page, or the page is too heavy for the browser to load quickly. The usual causes are weak or distant hosting, no caching, oversized images, too many or badly built plugins, a heavy theme, a cluttered database and an old PHP version. Start by measuring, because the fix depends on which side the delay is on.

Measure before changing anything

Run the home page and one important inner page through a speed testing tool such as Google's PageSpeed Insights. Look for two things.

Server response time. This is called Time to First Byte (TTFB). It is how long the browser waits before the server starts sending the page. Google's web.dev guidance treats 0.8 seconds or less as good and more than 1.8 seconds as poor.

Core Web Vitals. These are Google's three measures of how a page feels to a real visitor:

• Largest Contentful Paint (LCP): how soon the main content appears. Good is within 2.5 seconds.
• Interaction to Next Paint (INP): how quickly the page responds to a tap or click. Good is under 200 milliseconds.
• Cumulative Layout Shift (CLS): how much the layout jumps while loading. Good is below 0.1.

The terms are explained in the Core Web Vitals glossary entry.

If server response is slow, look at causes 1 to 5 below. If the server is quick but the page is slow to appear, look at causes 6 to 9.

Causes on the server

1. Hosting that is too small for the site

WordPress builds each page by running code and querying a database. On a crowded shared plan with limited CPU and memory, that takes longer, and it gets worse when traffic rises. WordPress's performance guide lists upgrading the plan or hardware as a fix when resources are the limit.

2. No page caching

Without a cache, WordPress rebuilds every page for every visitor. A page cache stores the finished page and serves the stored copy. For most brochure and blog sites this is the single biggest improvement available. It can be done with a caching plugin or at the server.

Caching has limits. Carts, checkouts, account areas and other personalised pages cannot be cached this way, so stores and membership sites depend more on good hosting.

3. Distance between the server and the visitor

Data takes time to travel. A server on another continent adds delay to every request. A content delivery network (CDN) shortens the trip by serving copies of your files from locations close to the visitor. Google's guidance recommends a CDN as a high priority for sites that do not have one.

4. Old PHP and server software

PHP is the language WordPress runs on, and newer versions are faster. WordPress.org recommends PHP 8.3 or greater. An opcode cache, which stores compiled PHP so it is not processed again on every request, should also be on. See upgrading PHP on WordPress safely.

5. A cluttered database

Over time the database collects old revisions, expired temporary data and settings left behind by removed plugins. One specific problem is autoloaded options: data WordPress loads on every page view. WordPress's performance guide suggests keeping this under roughly 800 KB. A persistent object cache, where the host offers one, cuts repeated database queries.

Causes in the page

6. Oversized images

This is the most common fault on business sites. A photo uploaded straight from a camera can be many times larger than the space it fills on screen. Fixes:

• Resize images to the size they are displayed at.
• Compress them.
• Use a modern format such as WebP.
• Load images below the first screen only when the visitor scrolls to them.

7. Too many plugins, or the wrong ones

Every plugin can add code that runs on each page and files the browser has to download. The count matters less than the quality. WordPress's guide suggests deleting plugins you do not need, then switching the rest off one at a time and measuring the difference.

8. A heavy theme or page builder

Some themes and builders load large amounts of CSS and JavaScript on every page, whether the page uses it or not. This can be reduced with settings, but it sometimes cannot be fixed without rebuilding templates.

9. Third-party scripts

Chat widgets, tracking tags, embedded maps, video players, booking widgets and social feeds all load from other companies' servers. Each one adds weight, and you have no control over how fast those servers respond. Remove the ones that are not earning their place and load the rest only on the pages that need them.

Other things to rule out

• Unwanted traffic. Login attacks, aggressive bots and other sites hotlinking your images all use server resources. WordPress's guide treats identifying and blocking these as critical.
• Redirect chains. Each redirect adds a delay before the page starts loading. Links and ads should point at the final URL.
• Background tasks. Backups, scans and imports that run during business hours slow the site while they run.

What to fix first

1. Switch on page caching.
2. Fix the images on your most visited pages.
3. Remove plugins and scripts you do not need.
4. Check the PHP version.
5. Add a CDN if visitors are far from the server.
6. If server response is still slow after that, review the hosting.

Measure again after each change, so you know what worked.

When the cause is not obvious

If the easy fixes have been done and the site is still slow, the cause is usually in the theme, a specific plugin or the server setup, and finding it needs profiling tools. Stryx does this as speed optimisation work. For South African sites, mobile networks add their own constraints, covered in website speed for South African mobile users. Contact Stryx if you would like the site looked at.