Finding the Plugin That Is Slowing Down Your Store
Plugins are not slow, hooks are. Binary search, query logging, asset loading, admin-ajax and cron, plus the four pieces of conventional advice that waste time.
Every WooCommerce store owner eventually installs a plugin that turns out to be slow, and the usual response is to install three more plugins to compensate. This is a method for finding the actual culprit instead.
The premise: plugins are not slow, hooks are
A plugin only costs time when its code runs. A well-built plugin that adds a shortcode runs only on pages using that shortcode. A poorly built one runs a query on every page load, including the admin, including AJAX, including the REST API.
So the question is never “how many plugins” but “what runs on this page, and why”.
Method 1: binary search in a staging copy
Unglamorous and effective. On a copy of the site, with caching disabled:
- Deactivate all plugins except WooCommerce and your page cache
- Measure a product page and a category page
- Reactivate half the remaining plugins, measure again
- Keep whichever half is slower, split it, repeat
Ten plugins take about four rounds. You end up with the specific plugin and a before/after number.
Caveats worth knowing before you start:
- Never do this on production — deactivating a payment or shipping plugin can corrupt configuration
- Some plugins add database tables or options that stay after deactivation, so measure cleanly with a restored copy
- Two plugins can be slow only together; if the total is worse than the sum of the halves, test combinations
Method 2: query logging
Enable query logging and load a single page. Group queries by the table they hit and the plugin that likely spawned them.
The pattern to look for: a plugin running its query once per product on the page. A store showing 24 products on a category page with a plugin doing one query per product adds 24 queries nobody asked for. On the product page it may add related items; on the cart it may recalculate shipping per line.
Signals that a plugin is responsible:
- Queries on custom tables with the plugin’s prefix
- Queries on
postmetawith a specific meta key, repeated - The same
SELECTappearing 20+ times on one request
Method 3: what loads on pages that do not need it
Open the page source of your homepage and search for the CSS and JavaScript of plugins whose features are not on that page. Every hit is a file the customer downloads for nothing.
A store with a forms plugin, a slider plugin, a gallery plugin and a reviews plugin often loads all four on every page. Asset optimisation plugins can defer some of this, but the honest fix is to stop loading assets where they are unused.
WooCommerce itself is a meaningful share of this: by default it loads cart fragments on every page. Stores that do not display a cart count in the header can often remove that safely — but test, because some themes depend on it.
Method 4: check what runs on admin-ajax and REST
Many plugins register AJAX handlers that fire on every page for logged-out users too — usually for “recently viewed”, “live search” or tracking.
Open the network tab, load a category page, and look at requests to admin-ajax.php or /wp-json/. Each one is a full WordPress bootstrap: often 100–300ms of server time for a small piece of data.
Recently-viewed products and live search implemented through admin-ajax are two of the most common performance culprits on WooCommerce stores, and both typically cost more than the feature is worth.
Method 5: the cron problem
WP-Cron runs on page loads. A plugin scheduling heavy work — stock sync, feed generation, index rebuilding — will make the site slow for whichever unlucky visitor happens to trigger it.
Check what is scheduled:
- Look for cron events belonging to plugins with intervals under 15 minutes
- Check whether any event overlaps with others at the same time
- Check whether the site receives enough traffic to trigger cron at all — low-traffic stores can have cron backed up for hours
The fix is usually to move cron to a system scheduler and stagger the heavy jobs. Our inventory sync plugin has the same consideration, and the note applies generally: scheduled work belongs in system cron, not in page loads.
What is almost never the problem
Some advice is repeated so often it becomes a reflex, and it wastes time:
“Too many plugins.” Thirty well-built plugins can be faster than five badly built ones. Count hooks, not plugins.
“Switch to a lighter theme.” Theme weight matters, but a slow server will make any theme slow. Measure server time first — the sequence in our diagnosis guide exists to prevent exactly this mistake.
“Install a caching plugin.” Caching hides query cost for anonymous visitors and does nothing for checkout, which is the most expensive page. It is necessary, not sufficient.
A practical order of operations
- Confirm the server is not the bottleneck
- Find which page type is slowest — not the homepage
- Log queries on that page; look for repetition
- Binary search only if query logging is inconclusive
- Check AJAX and cron before blaming the plugin list
- Fix one thing, measure, write the number down
The last item is the one people skip. Without before-and-after numbers, a “performance project” becomes a series of changes where nobody can say which one helped. If you need an outside read on a store that has been optimised twice already and is still slow, that is the work we do under speed optimisation.