Why Is My WordPress Site Slow? How to Speed It Up

CloudSprout team · November 2026 · 12 min read

Picture a customer in Hamilton searching for a plumber on their phone. Your site shows a blank screen for four seconds. They tap back and call the next name on the list. You never see that lost call in any report. WordPress speed optimization means finding what makes your pages slow and fixing it in the order that pays off most: measure first, then deal with the hero image, caching, plugins, PHP version and hosting, then check again on a schedule. Most small-business sites are slowed by a handful of the same causes, and you can find yours in about 30 minutes.

This guide is written for owner-operators, not developers. Each technical term is explained once, in plain words, and every step says what it takes and where it usually goes wrong.

TL;DR

  • Test your homepage and one inner page on mobile three times before you change anything. Write the numbers down.
  • Fix the biggest image at the top of the page first. Images are the largest single cause of slow WordPress pages, according to WordPress.com’s own support guide.
  • Turn on page caching and delete plugins you do not use. Both are the first, easiest wins named in the official WordPress optimization guide.
  • If the server is slow to answer, no front-end tweak will rescue the page. That is a hosting or caching problem.
  • Retest after every change, then once a quarter. Speed slips back when new plugins and updates pile up.

Table of Contents

What “slow” actually means (and why Google cares)

When people say a site is slow, they usually mean one of three different things. Google measures each one separately, and together they are called Core Web Vitals.

  • Largest Contentful Paint (LCP): how long until the biggest thing on screen, usually your top photo or headline, appears. The target is 2.5 seconds or less.
  • Interaction to Next Paint (INP): how long the page freezes after someone taps a button or menu. The target is 200 milliseconds or less. INP replaced an older measure called FID in March 2024, as this Core Web Vitals guide explains.
  • Cumulative Layout Shift (CLS): how much the page jumps around while loading, like a button that moves just as you tap it. The target is 0.1 or less.

There is a fourth number worth knowing: TTFB, or time to first byte. It is how long your server takes to start sending the page. It matters because everything else waits for it. A page that takes 2 seconds just to start cannot reach a 2.5-second LCP, even if every image after it loads instantly, as the same guide points out.

For a local business the stakes are simple. Most searches for “electrician near me” or “restaurant open now” happen on a phone, often on mobile data between jobs or in a parking lot. A page that drags loses the call before your pitch has a chance.

Step 1: Measure before you touch anything

Guessing is the most common mistake. Owners install three speed plugins, the site feels the same, and now there are three new things to maintain. Start with a baseline.

What you need: Google’s free PageSpeed Insights, plus a second tool that shows a waterfall chart (a timeline of every file your page loads, longest bars first). Pick a test location close to your customers, such as Toronto, rather than a server on the other side of the world.

How to do it:

  1. Test your homepage and one important inner page, such as your main service page or your contact page.
  2. Test on mobile first. Google indexes the mobile version of your site, and mobile scores are almost always worse than desktop.
  3. Run each test three times and use the middle result. The first run often looks slower because nothing is cached yet.
  4. Write down LCP, INP, CLS and TTFB for each page.

Where it goes wrong: People test once, see a score in the 60s, and panic. Mobile scores in that range are common even on sites that are well built, so judge the trend and the individual numbers, not a single score. Also, people test from the wrong place. If your host is in Europe and your customers are in Ontario, you are measuring distance, not your site.

What the numbers tell you:

What you see What it usually means Where to look
TTFB is slow (a second or more) Page caching is off or broken, or the server is overloaded Caching, then hosting
LCP is slow but TTFB is fine The top image or a large font or script is holding the page up Hero image, fonts
INP is slow Too much JavaScript running when people tap Plugins, scripts
CLS is high Images without set sizes, ads or embeds that pop in late Image dimensions, embeds

For a deeper look at the server side of this, our guide on fixing TTFB first to improve Core Web Vitals walks through why it comes before everything else.

Step 2: Fix the big image at the top

Open the waterfall chart and look at your LCP element. On most small-business sites it is the large photo or banner at the top of the homepage. This single file is often the biggest lever you have.

Electrician working beside a home service panel

Unoptimized images are the biggest contributor to slow WordPress sites, both in the size of each image and the number of images on a page, according to WordPress.com’s site speed guidance. A photo straight off a phone or a stock library can be several megabytes. Your visitor only needs a fraction of that.

What to do:

  • Resize it. If the image displays 1,200 pixels wide on the page, upload it at about that width, not at the 4,000 pixels your camera produced.
  • Compress it and use a modern format. WebP is a format that keeps quality at a much smaller file size. Most image-optimization plugins can convert for you.
  • Do not lazy-load the top image. Lazy loading means images load only as you scroll to them. That is great for photos lower down and harmful for the first one, which should load right away.
  • Set width and height on images so the page does not jump while loading. That fixes most CLS problems.

Where it goes wrong: An image plugin set to compress aggressively can leave a logo or product photo looking muddy. Check your top five pages by eye after any bulk compression. And if your theme uses a slider with five large photos, the real fix is usually to replace the slider with one strong image. Sliders are a classic cause of slow LCP.

Step 3: Turn on page caching

Without caching, WordPress rebuilds each page from scratch every time someone visits: it asks the database for your content, assembles the page, then sends it. Caching saves a finished copy and hands that out instead.

The official WordPress guidance says caching plugins can improve performance “several hundred times over” for fairly static pages, because they serve ready-made files (WordPress.org optimization guide). For a brochure-style business site, where the content rarely changes between visits, that is exactly your situation.

There are three layers worth knowing:

  1. Page caching: saves the finished HTML page. This is the one that fixes slow TTFB.
  2. Browser caching: tells a returning visitor’s browser to keep your logo and stylesheets, so the server can answer “nothing changed” instead of sending them again.
  3. Object caching: saves the results of repeated database lookups. Without it, the server reads your site options from the database on every page view, which slows things down and can strain the database in a traffic spike.

Where it goes wrong: Run only one page-caching tool. Two at once can conflict and produce broken pages. Also, pages with carts, bookings or logged-in areas should not be cached the same way as static pages, so if you take online orders or bookings, test checkout after switching caching on. And remember to clear the cache after you edit a page, or you will wonder why your changes do not show.

Step 4: Cut the plugin clutter

The official guide calls plugins the first and easiest place to start: deactivate and delete the ones you do not need, and switch others off selectively to see what each one costs your server (WordPress.org). WordPress.com’s list of common slowdown causes also includes outdated plugins, themes with inefficient code, embedded media such as YouTube and social feeds, and external scripts and ads (WordPress.com).

It is not the number of plugins that matters most, it is what each one does. A small plugin that adds a footer link costs almost nothing. A page builder add-on that loads its own scripts on every page, or a social feed that calls an outside service each time, costs a lot.

A simple plugin audit:

  1. List every active plugin and write one line on what it does for your business.
  2. Delete anything inactive or duplicated. Two SEO plugins, two security plugins and three “widgets” packs are common.
  3. Replace heavy features with lighter ones. An embedded video can be a thumbnail that links out, and a social feed can become a few plain links.
  4. If a page is still slow, a diagnostic plugin such as Query Monitor shows which plugin runs slow database queries. Switch it on only while you diagnose and switch it off afterwards, since it adds overhead of its own.

Where it goes wrong: Deleting a plugin that quietly powers a form, a booking button or your tracking. Take a backup first, delete one plugin at a time and click through your key pages after each. If something breaks, you will know exactly which plugin did it.

Step 5: Update PHP and look at your theme

PHP is the programming language WordPress runs on, and your host controls which version you use. Running a recent version means faster processing and better memory handling, which Yoast’s speed guide names as a significant performance gain. Your hosting dashboard usually shows the current version and a dropdown to change it.

Where it goes wrong: Older plugins or themes can break on a newer PHP version. Make a backup, switch versions, then check your site and forms. If something fails, the usual cause is an outdated plugin, which you should replace anyway.

Your theme matters too. A theme packed with sliders, animation libraries and features you do not use loads that code on every page. WordPress.com’s advice is to choose themes that include only the features you need (source). If a rebuild is on the horizon, a lighter theme is a good place to start.

Step 6: Check your hosting and use a CDN

Sometimes the site is fine and the server is the problem. The official guide says hosting hardware and resource limits affect performance, and that moving to a plan with higher limits can help if you are maxing out the current one (WordPress.org).

Signs that hosting is the bottleneck:

  • TTFB stays slow even with page caching switched on.
  • The site slows down at the same times each day or during a promotion.
  • Your host’s dashboard shows you hitting CPU or memory limits.

A content delivery network (CDN) is a network of servers around the world that stores copies of your images, scripts and styles and delivers them from a location near the visitor. The same guide notes a CDN works best alongside a caching plugin, and that newer CDNs can cache the whole HTML page at the edge too. For a business that serves Ontario customers, the question is mostly whether your files are served from somewhere close to them, which is worth confirming when you test from Toronto.

What to fix first: a priority list

If you have one afternoon, work down this list and retest after every change.

Order Fix Why it comes here
1 Resize and compress the top image, keep it out of lazy loading Usually the biggest LCP gain for the least effort
2 Turn on one page-caching tool Cuts TTFB, which every other metric depends on
3 Delete unused plugins, replace heavy ones Less code to load and fewer things to break
4 Defer non-essential JavaScript Helps INP and LCP
5 Convert remaining images to WebP, set image sizes Helps load time and CLS
6 Update PHP, review hosting Raises the ceiling for everything else

Keeping the site fast over time

Speed is not a one-time project. Every new plugin, every uploaded photo and every theme update can add weight. A simple routine keeps it under control:

  • Each month: run your three tests on the homepage and one key page, and note the numbers next to last month’s. Remove plugins you no longer use. Compress every new image before you upload it.
  • After every major update: retest, because updates are when slowdowns tend to appear.
  • Each quarter: a fuller review of plugins, PHP version, hosting plan and CDN, using the baseline you recorded in Step 1.

This is where most owners fall behind, not because the steps are hard, but because nobody has an hour a month for them. A site that was fast in January is often sluggish by autumn. Security is part of the same upkeep, and our short guide on WordPress security basics for small businesses covers the habits that go with it.

What we think about WordPress speed

We build and look after small-business websites in-house, with no outsourcing, so the person who understands your site is the person you talk to. That shapes how we think about speed.

First, a slow site is rarely one big problem. It is usually six small ones that add up: a heavy hero image, a plugin nobody remembers installing, caching that was never switched on. Fixing one and stopping there is why so many owners feel nothing changed.

Second, speed is a business question before it is a technical one. If your site is not producing calls or quote requests, loading time is one of the first things we check, alongside whether the page tells people what to do next. Our write-up on prioritized fixes for small business website speed lays out how we sequence the work.

Third, the work does not end at launch. We prefer month-to-month arrangements with no lock-in contract, because a fast site is kept fast by regular attention, not by a one-off tune-up.

Cristo

When to hand it to someone

Plenty of owners can compress an image and delete a plugin. The trouble starts with the parts that can break a live site: PHP changes, caching rules for bookings and checkout, hosting moves, and the quarterly retesting that never gets done on a busy week.

At CloudSprout we offer a free trial that includes a full digital audit, so you can see what is holding your site back before you commit to anything. Our monthly plans are Sprout at $300 per month, Grow at $600 per month and Scale at $1,200 per month, each with a one-off setup fee: $500 to $1,500 for Sprout, $1,500 to $3,500 for Grow and $3,500 to $7,500 for Scale. Everything is done in-house, and you speak directly to the people doing the work. See the details on our pricing page.

If your WordPress site needs a rebuild rather than a tune-up, our WordPress development services are built around sites that bring calls, and you can read more about how we work with WordPress sites in Halton and the GTA.

FAQ

How do I speed up my WordPress site without breaking it?

Take a full backup first, then change one thing at a time and retest after each. Start with the top image, then caching, then plugins. If a page breaks, you will know which change caused it and can undo just that one.

Do I need a speed plugin?

A caching tool is the one addition most sites benefit from, since page caching is what brings server response time down. Avoid stacking several optimization plugins that all do the same job. They can conflict, and each one adds its own code.

Is a mobile score in the 60s a problem?

Not by itself. Mobile scores are almost always lower than desktop, and a single score is less useful than the individual numbers: LCP under 2.5 seconds, INP under 200 milliseconds and CLS under 0.1. Look at those three, plus your server response time, and watch the trend month to month.

How often should I test my site’s speed?

Test monthly on your key pages, again after any major update or new plugin, and do a fuller review each quarter. Keep your first set of numbers as a baseline, so you can see when something slips.

Will a faster site get me more customers?

A faster page keeps more visitors from leaving before they see your phone number or contact button, and Google uses Core Web Vitals as part of how it assesses page experience. Speed works best alongside a clear page that tells people what to do next.

Sources

Book a free 30-minute call.