Skip to content
Agencei
Urgency : moderate

Slow WordPress site: how to diagnose and speed it up

A slow WordPress site means pages that take several seconds to appear, an admin area that is painful to use and, often, a drop in search rankings and conversions. Google includes Core Web Vitals in its ranking and visitors leave a page that does not respond quickly.

Slowness is rarely caused by WordPress itself. It almost always comes from hosting, poorly built plugins, unoptimised images, missing caching or a bloated database. Each cause has its own symptoms and its own diagnostic method.

This page helps you identify what is slowing your site down, run the basic checks yourself and know when it is more cost-effective to hand the optimisation to a professional.

Typical symptoms

  • Pages take more than three seconds to display, even on a good connection.
  • The WordPress dashboard is slow; saving a post or loading the editor takes a long time.
  • PageSpeed Insights or Lighthouse report a high server response time (TTFB).
  • The site becomes very slow at peak hours or during an email campaign.
  • Images appear late and the layout jumps around while loading.
  • Your host warns you about CPU, memory or PHP execution time limits being exceeded.

Possible causes

Undersized hosting

An overloaded shared server, an outdated PHP version, no OPcache or a badly configured MySQL make every request longer. A high TTFB is the most common sign.

Too many plugins, or badly coded ones

Each plugin adds SQL queries, scripts and sometimes external HTTP calls to every page. Page builders, built-in statistics plugins and some security suites are particularly heavy.

No caching

Without page caching, every visit runs all the PHP code and queries the database. Without object caching, the same queries are repeated dozens of times per page load.

Unoptimised images

Photos uploaded at full resolution, without compression, WebP format or lazy loading, multiply the weight of each page.

Bloated database

Accumulated post revisions, expired transients, tables left behind by old plugins and, above all, oversized autoloaded options in wp_options slow down every request.

Heavy theme and third-party resources

External fonts, tracking scripts, embedded videos, social widgets and ads block rendering and depend on servers you do not control.

Checks to perform

  1. 1

    Measure and locate the slowness

    Run PageSpeed Insights or WebPageTest on the home page and an inner page. If the server response time (TTFB) is high, the problem is on the hosting or PHP side; if it is low but the page is still slow, the cause is in the browser (images, scripts, theme).

  2. 2

    Install Query Monitor

    This free plugin shows, for each page, the time spent per plugin, slow or duplicated SQL queries and external HTTP calls. It is the fastest way to point at a culprit.

  3. 3

    Disable plugins one by one

    Use the Health Check & Troubleshooting plugin to disable plugins for your session only, without affecting visitors, and measure at each step.

  4. 4

    Check PHP and memory

    In Tools > Site Health > Info, check the PHP version and the memory limit. An unsupported PHP version or a memory_limit set too low in wp-config.php are frequent bottlenecks.

  5. 5

    Inspect the wp_options table

    In phpMyAdmin, run SELECT SUM(LENGTH(option_value)) FROM wp_options WHERE autoload = 'yes'. A result of several megabytes means every page needlessly loads large amounts of data.

  6. 6

    Verify that caching works

    In the Network tab of the browser developer tools, look at the page response headers (x-cache, cf-cache-status, cache-control, age). A page served from cache should respond within a few tens of milliseconds.

  7. 7

    Look at server load

    If you have SSH access, top or htop show whether PHP-FPM or MySQL are saturating the CPU; df -h checks that the disk is not full, which slows MySQL and makes cache writes fail.

Solutions

Set up full caching

Page caching (WP Rocket, LiteSpeed Cache, WP Super Cache or Nginx cache), OPcache enabled on the PHP side and a Redis or Memcached object cache for content-heavy or WooCommerce sites.

Optimise images

WebP conversion, compression, dimensions matched to display areas and lazy loading. A CDN offloads the server and brings files closer to visitors.

Prune plugins

Remove those no longer needed, replace the heaviest ones with lighter alternatives and move non-critical functions (statistics, backups) out of the rendering path.

Clean and tune the database

Delete revisions and transients, purge orphaned tables, reduce autoloaded options, convert tables to InnoDB and add indexes for the slow queries identified.

Update PHP and WordPress

Moving to a supported PHP version alone brings a noticeable gain. Check theme and plugin compatibility on a staging copy before switching versions.

Resize or change hosting

If the server is still saturated after optimisation, a properly configured VPS (Nginx, PHP-FPM, tuned MariaDB) or managed WordPress hosting solves the problem for good.

When should you call a professional?

  • The site is still slow after setting up caching and optimising images.
  • Query Monitor shows slow SQL queries or resource-hungry plugins that you cannot fix without breaking the site.
  • You sell online with WooCommerce and the slowness affects the cart, customer account or checkout, which cannot be cached.
  • You have no server access, no staging environment or no time to run the diagnosis yourself.
  • You are considering switching hosts and want to be sure it is the right answer before migrating.

How Agencei can help

  1. 1

    Performance audit

    Measurements from several locations, profiling with Query Monitor and an APM tool, review of PHP-FPM and MySQL logs (slow query log) to pinpoint the bottlenecks.

  2. 2

    Server optimisation

    PHP-FPM tuning, OPcache activation, Nginx or Apache configuration, MySQL/MariaDB tuning, Redis set up for object caching.

  3. 3

    Application clean-up

    Plugin triage, theme slimming, optimisation of existing images and automation for future uploads, database clean-up.

  4. 4

    Caching and CDN

    Page cache configuration with appropriate exclusion rules (cart, account, forms), Brotli or Gzip compression, HTTP/2 and a CDN where relevant.

  5. 5

    Before and after measurements

    You receive a report comparing load times and Core Web Vitals before and after the work, with the remaining recommendations.

  6. 6

    Follow-up

    On request, regular WordPress maintenance keeps performance stable over time: tested updates, monitoring and periodic clean-up.

Frequently asked questions

Is a caching plugin enough to speed up WordPress?

It greatly improves static public pages, but it does not fix an overloaded server, a bloated database or dynamic pages such as the cart or the admin. Caching is one of the building blocks, not the only one.

Do I need to change hosting provider?

Not necessarily. An audit shows whether the server is really at fault. Many sites become fast on the same hosting after their plugins, images and database have been optimised.

Why is the admin slow while the public site is fast?

Page caching does not apply to the admin. Its slowness usually comes from plugins loading scripts on every admin page, the Heartbeat API, heavy WordPress cron tasks or an oversized wp_options table.

How long does an optimisation take?

The diagnosis often takes a few hours. The fix ranges from a few hours for caching and images to several days if the server needs reconfiguring or the theme reworking.

Do too many plugins necessarily slow the site down?

It is their quality that matters, not their number. A single badly coded plugin can slow things down more than twenty lightweight ones. Query Monitor lets you measure the real impact of each.

Tell us about your project

Describe your need in a few lines: we come back to you with a first analysis and the next steps.