To identify a problematic WordPress plugin, note when the issue began, check WordPress Site Health and the Plugins screen, then test a suspected plugin by deactivating it and observing whether the same symptom disappears. A warning or timing clue is not proof on its own: back up before troubleshooting, change one thing at a time, and verify the result.
Start with the symptom and its timing
Write down what is going wrong, when it started, and whether anything changed just before it began. A problem that appears shortly after installing or updating one plugin makes that plugin a reasonable first suspect. An error message that names a plugin file is another useful clue. Neither proves the plugin caused the problem; a theme, another plugin, or site configuration may also be involved.
- Record the exact error text and the page or action that triggers it.
- Note recent plugin installations, updates, and other site changes.
- Check whether the issue happens consistently or only under particular conditions.
Check WordPress Site Health and the Plugins screen
Review Site Health
In the WordPress dashboard, go to Tools > Site Health. The Status tab highlights configuration items that need attention, while the Info tab provides technical details, including plugin names and versions and whether auto-updates are enabled. WordPress notes that critical issues can relate to security vulnerabilities or serious performance concerns. A Site Health alert is a site-level finding, however, and does not by itself identify a plugin as the cause. See the WordPress Site Health screen guide.
Inspect installed plugins
Open Plugins > Installed Plugins and look for update notices, recently changed plugins, or a plugin that failed during activation. WordPress may show an update notice for a plugin hosted in the WordPress.org directory when a newer version is available. A fatal activation error warrants investigation, but still needs to be understood in context. Check the Plugins screen documentation and the Manage Plugins troubleshooting guidance.
#1 Best Overall
Check the plugin’s documentation and support information
Look up the plugin’s documentation, support forum, and update information. Search using the plugin name together with the exact error message or observed problem; this is more useful than searching for a broad phrase such as “plugin broken.” Check whether other users describe the same symptom and whether the documentation addresses your WordPress setup. A reported issue can help narrow the diagnosis, but it does not confirm that your site has the same cause.
Isolate a plugin conflict safely
Before changing a live site, make a backup you can restore. Learn WordPress recommends backing up before troubleshooting changes; your hosting provider may offer a backup option, or you can use a solution appropriate to your site. See Troubleshooting your site: Plugin and theme conflicts and Troubleshooting Basics.
If one plugin is the likely cause
- Record the current symptom and confirm that you have a usable backup.
- In the dashboard, go to Plugins > Installed Plugins and deactivate the suspected plugin.
- Repeat the same page action or workflow that previously produced the issue.
- If the symptom goes away, reactivate the plugin and repeat the check. If the issue returns, that is stronger evidence of a connection; note the result before deciding what to do next.
If you do not know which plugin is responsible
- Deactivate one plugin at a time from Plugins > Installed Plugins.
- After each change, repeat the same test and record whether the symptom remains.
- If the problem stops after one plugin is deactivated, reactivate that plugin and test again to see whether the symptom returns.
WordPress’s documented advice is to “Try deactivating plugins one at a time until you find the one that’s causing the issue.” Keeping the test consistent and changing one plugin at a time makes the result easier to interpret. If the problem persists with the suspected plugin deactivated, that test does not support it as the cause; continue investigating other plugins, the theme, or site configuration.
Decide what to do with the result
Once you have a repeatable connection between a plugin and the symptom, check its current documentation and support information for a relevant fix or compatibility guidance. When considering another plugin, compare it against your actual needs: whether it supports your WordPress setup, provides the needed feature without reproducing the issue, addresses the observed error in its documentation or support information, and is receiving updates. No single signal guarantees that a plugin is safe or suitable.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallHandle suspected security vulnerabilities responsibly
If you believe you have found a vulnerability in a plugin available through the WordPress.org directory, keep the details confidential and report it to the developer and the WordPress plugins team. Do not publish vulnerability details as a troubleshooting shortcut. See WordPress.org’s Security guidance and the developer documentation on Reporting Plugin Security Issues.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
