Identify Slow WordPress Plugin

The Problem

Your site is slow and you suspect it's a plugin, but with a dozen or more active, you have no way to know which one (or which combination) is actually responsible without just disabling them all and hoping.

About this problem

Not all plugins are created equal performance-wise — a poorly coded plugin can single-handedly add hundreds of milliseconds to every single page load, run unnecessary database queries, or load unminified assets on every page even where they're not needed. Generic speed optimisation advice (caching, image compression) often masks the real problem if one specific plugin is the actual bottleneck.

This matters most when you've noticed a clear before/after slowdown correlated with installing or updating something specific, or when general optimisation hasn't moved the needle as much as expected.

What's Included

• Profiling page load time with each plugin isolated to measure its individual impact
• Identifying the specific plugin(s) adding the most load time or database queries
• A written report ranking plugins by actual performance impact
• Recommendations for each offending plugin (configuration fix, lighter alternative, or removal)

What's NOT Included

• Fixing the identified plugin's own code (that's for the plugin's developer, unless it's a configuration issue I can address)
• Implementing every recommendation automatically — you choose what to act on, I can carry out whichever you approve
• General speed optimisation unrelated to plugins (see the dedicated speed optimisation service for that broader scope)

How It Works

1. Establish a baseline page load time and query count with all plugins active.
2. Selectively deactivate and reactivate plugins (or use a profiling tool) to isolate each one's individual contribution to load time.
3. Identify plugins adding excessive database queries, blocking render, or loading unnecessary assets site-wide.
4. Rank findings by actual measured impact, not assumptions.
5. Document specific, actionable recommendations for each plugin flagged.

In practice: you buy the service, send over whatever access or details the job needs, I investigate and do the work, and you confirm it's resolved before we call it done.

Frequently Asked Questions

How can I tell which WordPress plugin is slowing down my site?

By isolating each plugin's individual contribution to page load time and database queries through systematic testing, rather than guessing from the plugin list alone.

Do all WordPress plugins slow down a site equally?

No, the impact varies enormously — a well-coded plugin can add almost nothing, while a poorly coded one can add hundreds of milliseconds or dozens of extra database queries per page.

Will I need to remove every slow plugin you find?

Not necessarily — some can be reconfigured to perform better, replaced with a lighter alternative, or kept if the functionality is worth the (now understood) performance cost.

Can two plugins be slow together but fine individually?

Yes, plugin conflicts can create performance problems that don't show up when testing either plugin alone, which is part of why isolated, methodical testing matters.

Does this include fixing the slow plugin, or just identifying it?

The diagnosis and a ranked report with recommendations are included; implementing a specific fix (reconfiguring, replacing or removing a plugin) can be carried out as part of this or as a quick follow-up.