Performance9 min readPublished: 28 Mar 2025Updated: 9 Nov 2026

Why WordPress Speed Should Not Rely on Plugins

Caching and optimisation plugins run PHP before they help. Here is why WordPress speed should not rely on plugins, and what your hosting should do instead.

G7Cloud Engineering
Platform team
Share:
Abstract stack of translucent blue glass panels receding into shadow, suggesting compounding layers.
  • Every active plugin runs PHP on every request before it can help, so plugins add work before they save any.
  • A caching plugin still starts WordPress just to decide whether to serve its saved copy.
  • Page caching, object caching and opcode caching each belong in a different layer. The fastest page cache sits in front of PHP.
  • Bot and attack traffic is best stopped by a firewall before it reaches PHP, not by a plugin inside WordPress.
  • Removing overlapping performance plugins cuts conflicts, updates and unexpected slowdowns.

Why shouldn't WordPress performance depend on plugins?

WordPress speed should not rely on plugins because every active plugin runs PHP on every request before it can help. A caching plugin has to start WordPress just to decide whether to serve a saved page. The lasting fix sits in the hosting: each site kept separate, a firewall in front of PHP, and caching in the right place.

Plugins make WordPress flexible, and they are good at adding features. Speed is a different job: it depends on how much work the server does for each request, and how much it can skip. A plugin cannot skip work it is part of.

The distinction that matters

Plugins are good at adding features. They are a poor place to fix speed, because they can only speed up work they first make WordPress do. The cheapest request is the one PHP never has to serve.

How much does each WordPress plugin cost on every request?

Each active plugin adds fixed work to every uncached request. WordPress loads its core, then every active plugin's main file, registers each plugin's hooks, and reads the autoloaded settings from the database. With 30 active plugins, that happens 30 times on every request, before your theme shows a word.

The cost builds up in three ways. Hooks: plugins attach code to events such as init and the_content, and WordPress runs every one in order. Queries: many plugins add their own database reads on each page. Autoloaded options: plugins save settings in the wp_options table marked to load on every request, so WordPress reads all of them into memory each time. A bloated autoload set is one of the most common causes of slow time to first byte (TTFB, how long the server takes to start sending the page) on sites we migrate.

What each plugin adds per requestWhy it costs time
Loading the plugin filePHP reads and starts the plugin before your page renders
Hooks on init, wp_loaded, the_contentWordPress runs every one in order, on every request
Extra database queriesPHP waits for each one to come back
Autoloaded wp_options rowsThe whole set is read into memory on every request

Fixed cost on every uncached request, multiplied by the number of active plugins.

You pay this on uncached requests

Logged-in admin pages, the WooCommerce cart and checkout, search and personalised pages usually cannot be served from a saved copy. That is where a heavy plugin list hurts most, because each of those requests runs every plugin.

What does a caching plugin do, and where should caching happen?

A caching plugin saves a finished HTML copy of a page and serves it to the next visitor instead of rebuilding it. That helps. But the plugin still loads inside WordPress on every request to check whether a valid copy exists. It removes the cost of building the page, not the cost of starting PHP.

Three kinds of caching often get lumped together, and each belongs in a different layer. A page cache stores the finished HTML. An object cache (usually Redis) stores the results of expensive database queries so they are not repeated. An opcode cache (OPcache) keeps compiled PHP in memory so the server does not re-read your code each time. A plugin can drive a page cache and connect to Redis, but OPcache and the fastest page cache live below WordPress, in the server and the layer in front of it.

Cache typeWhat it storesWhere it belongs
Page cacheThe finished HTML of a pageIn front of PHP, so WordPress never starts on a cache hit
Object cache (Redis)Results of expensive database queriesA cache store the site connects to, not a file on disk
Opcode cache (OPcache)Compiled PHP in memoryThe PHP setup on the server

Three caches, three layers. Only one is a job a plugin is well placed to do.

Do image optimisation plugins slow WordPress down?

They can, usually at busy moments rather than on every page. They compress uploads and sometimes convert formats, all inside PHP. During a bulk run or a traffic peak, that work competes with your pages for the same processor and memory. Many also add their own hooks and settings, so they carry the same per-request cost as any other plugin.

Pro Tip

The cheapest optimisation is the one your server never does. Export images at the size they are shown, compress them before upload, use modern formats, and let the browser lazy-load anything below the fold with the native loading="lazy" attribute.

Images matter for Core Web Vitals: the largest image at the top of the page is often what Google measures for Largest Contentful Paint (LCP, how long the main content takes to appear). Getting it right before upload beats fixing it through a plugin. Our Core Web Vitals guide for WordPress explains each score and what moves it.

When are caching and optimisation plugins still the right tool?

They are the right tool when you cannot change the server. On shared hosting you rarely control the web server, the PHP setup or anything in front of WordPress. A caching plugin is then the only lever you have, and a good one makes a real difference. That is why they became standard advice.

They also earn their place for object caching. Connecting WordPress to Redis cuts repeated database work on dynamic pages, and that connection is made through a plugin or a drop-in file. Plugins are not the problem. The point is to use them for the layers you can reach, not as a stand-in for hosting that already caches pages and filters traffic below WordPress.

What should the hosting do instead of plugins?

The hosting should handle the jobs that are infrastructure rather than content: keeping sites separate, filtering traffic, caching in front of PHP, backups and monitoring. When the platform does these, your plugin list shrinks to the features you need. Fewer plugins means fewer conflicts, fewer updates and steadier speed.

JobDone by a pluginDone by the hosting
Page cachingRuns after WordPress starts, on every hitServed in front of PHP, before WordPress loads
Bot and attack filteringPHP inspects each request after it arrivesA firewall stops it before it reaches PHP
Protection from busy neighboursNothing you can do inside WordPressEach site in its own container with its own database
BackupsA plugin running inside your siteScheduled by the platform, stored off the site
Uptime monitoringA plugin adding hooks and scheduled tasksOutside checks every minute, with alerts

The same jobs, done around WordPress instead of inside it.

A practical rule

Keep plugins for features. If a plugin's main job is speed, security or backups, check whether your hosting already does it. If it does, the plugin is usually overhead you can remove.

How many WordPress plugins is too many for performance?

There is no fixed number. A well-written plugin with one hook costs far less than a page builder that loads its own framework on every request, so quality matters more than count. On the sites we migrate, uncached time to first byte starts to climb noticeably past about 30 active plugins.

Overlap is the better test. Two caching plugins, two image optimisers, or three plugins touching the same checkout add their costs, not their benefits, and raise the odds that one update breaks another. Pick one plugin per job, or let the hosting do the job.

How do I find which plugins are slowing my site?

Measure each plugin's cost, then remove overlap. Query Monitor, a free developer plugin, shows the database queries, hooks and PHP time each plugin uses on a page. Run it on your slowest uncached pages, such as a category archive, the WooCommerce cart and a logged-in admin page.

StepWhat to look for
Measure with Query MonitorPHP time, query count and hooks for each plugin
Test uncached pagesCart, checkout, search, logged-in admin, category archives
Find overlapTwo or more plugins doing the same job
Check autoloaded optionsLarge rows, or rows left behind by old plugins
Compare with your hostingCaching, firewall, backups and monitoring the host already does

A repeatable plugin audit, from measuring to removing.

Pro Tip

Change one thing at a time and measure again. If you switch off five plugins at once and the site gets faster, you still do not know which one mattered.

If you have shell access and want the exact cause, troubleshooting high CPU and memory on WordPress walks through the access log, the slow query log and the autoloaded options table.

On G7Cloud WordPress hosting, each site runs in its own container with its own database and its own Redis object cache, and ScaleShield filters bots and abusive traffic before it reaches PHP. Our WordPress performance page shows how each layer fits together.

Frequently asked questions

Why shouldn't WordPress speed rely on plugins?

Because every active plugin runs PHP on every request before it can help, and a caching plugin still starts WordPress just to decide whether to serve its saved copy. Speed comes from doing less work per request, which is a job for the hosting. Keep plugins for adding features.

Do caching plugins actually make WordPress faster?

Yes, especially on shared hosting where you cannot change the server. They serve a saved HTML copy instead of rebuilding the page. But the plugin still loads inside WordPress on every request, so a cache served in front of PHP is faster again, because WordPress never starts.

What is the difference between page caching, object caching and opcode caching?

A page cache stores the finished HTML of a page. An object cache, usually Redis, stores the results of expensive database queries. An opcode cache keeps compiled PHP in memory so the server does not re-read your code each time. Each belongs in a different layer, and only object caching is a natural fit for a plugin.

How many plugins are too many for WordPress performance?

There is no hard limit, because quality matters more than count. On sites we migrate, uncached time to first byte starts to climb noticeably past about 30 active plugins. Overlap matters more: two plugins doing the same job add their costs, not their benefits.

How do I find which WordPress plugin is slowing my site?

Install Query Monitor and load your slowest uncached pages, such as the cart, checkout or a logged-in admin page. It shows the PHP time, queries and hooks for each plugin. Switch off suspects one at a time and measure again.

Put this into practice on G7Cloud

Every site runs in its own dedicated container behind ScaleShield, with daily backups that are restore-tested every night. Start on the free plan, no card needed.

About G7Cloud Engineering

Platform team

Articles written by the engineers who build and run G7Cloud: UK managed hosting and the AI Website Builder. We write about what we operate every day: containers, backups, databases, and the small-business websites that run on them.

More about G7Cloud →