# Your WordPress or WooCommerce site is slow

> A WordPress site that gradually slows down usually doesn’t have a single cause: it’s often a build-up of plugins, a database that’s never been cleaned, and a cache that’s missing or misconfigured. I measure before fixing, not the other way round.

- Source canonique : [https://allaux.fr/en/wordpress-woocommerce/site-lent](https://allaux.fr/en/wordpress-woocommerce/site-lent)
- Langue : EN
- Dernière mise à jour : 2026-09-30

## Direct answer

> Measure server response time on a product page then on the home page, logged in and logged out: a clear gap means page caching never serves logged-in visitors. Then check the PHP version and whether an object cache is in place under Tools > Site Health, followed by the size of wp_postmeta if the catalogue is large.

## Signs that justify an audit

- Load time increasing over the months with no obvious change
- WordPress dashboard slow to open, even for simple actions
- WooCommerce product page or cart slow to display
- Poor Core Web Vitals score despite decent shared or dedicated hosting
- Slowdown only during traffic spikes

## How I measure before stepping in

1. **Query profiling** — I use a profiling tool (such as Query Monitor) to list the SQL queries run per page, their number, and which plugins trigger them.
2. **Auditing the wp_options table** — I check the size and content of autoloaded data in wp_options: badly uninstalled plugins sometimes leave several megabytes there that load on every page.
3. **Checking the cache** — I check whether a page cache and an object cache (Redis or Memcached if available) are in place and correctly configured.
4. **WooCommerce-specific analysis** — On a shop with a sizeable catalogue, I check the weight of wp_postmeta, which stores product attributes as key-value pairs and can seriously slow catalogue queries if it grows without proper indexes.
5. **Checking the server** — I check the PHP version, whether OPcache is enabled, and the execution mode (PHP-FPM rather than classic CGI), which directly affects response time.

## What I fix most often

The most common case on WordPress is a build-up of active plugins that aren’t really used any more, each adding its own queries and scripts to every page, even when the feature isn’t visible. Disabling what’s no longer needed often has more impact than a complex technical optimisation.

On WooCommerce, the metadata-based data model (each product attribute is a row in wp_postmeta) becomes a performance problem as the catalogue grows, particularly on filtering and search pages. I add targeted indexes or review the costliest queries depending on the case.

Finally, transients (temporary data stored by WordPress) that aren’t properly cleared sometimes pile up by the tens of thousands in the database without ever expiring correctly, weighing down every query that touches the options table.

## More powerful hosting doesn’t fix everything

> Upgrading hosting temporarily masks a problem of unoptimised queries or a cluttered database, but the slowdown returns as soon as traffic or the catalogue grows again.

## Worth reading next

- **Diagnosing a slow shop** — How to measure before buying anything. ([/guides/diagnostiquer-boutique-lente](/guides/diagnostiquer-boutique-lente))
- **Clearing the WordPress cache** — The caching layers and the order to clear them in. ([/guides/vider-cache-wordpress](/guides/vider-cache-wordpress))
- **A very slow WordPress admin** — A slow dashboard doesn’t share the causes of a slow storefront. ([/wordpress-woocommerce/problemes/admin-wordpress-tres-lent](/wordpress-woocommerce/problemes/admin-wordpress-tres-lent))
- **Optimising product images** — Almost always the heaviest part of a product page. ([/guides/optimiser-images-produits](/guides/optimiser-images-produits))

## FAQ

### Do I need to switch hosts to speed things up?

Not necessarily. I measure first where the time is actually lost: often the cause is in the plugins or the database, not the server’s power.

### Could the audit risk breaking the live site?

No, profiling doesn’t modify the site. Identified fixes are then tested before being applied, and I can work outside peak traffic hours.

### What access do I need to give you?

WordPress admin access, FTP or SSH access, and database access. Access to the hosting area helps check the server configuration.

### How long does a performance audit take?

Diagnosis usually takes half a day to a day. Fixes then vary: a database cleanup is quick, rebuilding badly optimised queries takes longer.

### Does site speed affect my SEO?

Yes, speed is one of the Core Web Vitals criteria Google considers, but it’s just one factor among others, not a guarantee of a better ranking on its own.