What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
If a WordPress site breaks after a plugin change, first record the exact symptom, check Tools > Site Health, and make sure you have a restorable backup before changing anything. Then isolate plugins and themes one at a time. If a fatal error blocks access, try WordPress Recovery Mode; if that is unavailable, use a reversible file-manager fallback or ask your host for help.
Start by documenting what failed
Before deactivating anything, note whether the problem affects the public site, wp-admin, or both; when it began; and what changed shortly beforehand. Record the exact error text and the time it appeared. Recent plugin, theme, WordPress, and PHP changes can help narrow the investigation, but a blank page or critical error does not by itself prove a plugin is responsible. WordPress lists plugin and theme conflicts alongside PHP errors, memory exhaustion, and database issues as possible causes of these symptoms. WordPress.org’s lesson on plugin and theme conflicts explains the range of causes.
As an Amazon Associate I earn from qualifying purchases.
Check Site Health and secure a restore path
Review Site Health
In the dashboard, go to Tools > Site Health. On the Status tab, review critical issues, recommended improvements, and passed checks. Then open the Info tab for configuration and installed-component details. Site Health can flag issues such as blocked HTTP requests, configuration problems, or debug output. Its information can be exported, but review the export and share only the details needed for diagnosis because it may contain sensitive information. See the Site Health screen documentation.
Back up before changing the live site
WordPress.org’s troubleshooting lesson recommends making a full backup before troubleshooting. Confirm that you can restore it before deactivating plugins, switching themes, or editing files. Keep a short record of each change and test whether the original symptom remains before making another change. This makes it easier to identify the cause and undo an unsuccessful step. WordPress.org’s troubleshooting lesson
Choose the safest way to isolate a plugin or theme
The right method depends on whether you can log in, whether the site is live, and whether you can tolerate changing what visitors see.
| Method | When it fits | Effect and access needed |
|---|---|---|
| Troubleshooting mode | You can access wp-admin and want to test suspected conflicts. | Disables plugins and switches to a default theme for your administrator session; visitors continue to see the normal site. Requires dashboard access. |
| Manual deactivation in wp-admin | You can access the dashboard and can test changes on the site. | Changes active plugins for the site, so visitors may be affected. Reactivate components individually to identify a trigger. |
| Recovery Mode | WordPress detects a fatal PHP error during a regular page load and sends the administrator a recovery email. | Pauses the failing plugin or theme for that administrator session. It does not handle every error or background task. |
| Rename a plugin folder | You cannot use wp-admin and suspect a plugin. | Requires FTP or the hosting file manager. Temporarily renaming the folder deactivates that plugin; restore the original name after diagnosing or resolving the problem. |
These behaviors are described in WordPress.org’s troubleshooting lesson and its troubleshooting documentation.
Use troubleshooting mode when dashboard access works
WordPress.org’s learning material describes troubleshooting mode as a way to deactivate plugins and use a default theme for the current administrator session without changing the version visitors see. Activate the mode through the Health Check and Troubleshooting plugin, then check the affected page. If the problem disappears, re-enable plugins one at a time and test after each activation. Also test with a default theme if the issue could be theme-related. When the fault returns, record the component and the steps that reproduce it.
Free tools Windows power users keep installed
One-click scans. No signup required.
Use manual deactivation only when site-wide changes are acceptable
If you cannot use session-only troubleshooting, the WordPress.org lesson describes deactivating plugins in wp-admin and reactivating them individually. Because this changes the active plugins for the site, consider the impact on visitors before proceeding. Test the failing page after each change and keep notes so you can restore the previous state.
Rank #3
Recover access after a fatal error
Try WordPress Recovery Mode
Introduced in WordPress 5.2, Recovery Mode can help when WordPress detects a fatal PHP error during a regular page load. WordPress emails an administrator a special login link; the failing plugin or theme is paused for that administrator’s session, and dashboard notices can identify the component. After addressing the cause, exit Recovery Mode and verify that the site works normally. Recovery Mode is not a guarantee for every error, including failures in other execution contexts. Details are in the WordPress troubleshooting documentation.
If the recovery email does not arrive
Check spam and verify the administrator email address. If the link remains unavailable and a plugin is suspected, WordPress documents temporarily renaming its folder using FTP or the hosting provider’s file manager to deactivate it. This requires access to the site’s files and is a recovery measure, not a fix. Keep the change reversible; if you are unsure which folder to change or cannot regain access, ask your hosting provider for help.
Use debug logs privately and temporarily
WordPress’s Advanced Administration Handbook says WP_DEBUG is assumed false by default and recommends debug tools for local or staging installations rather than live sites. With debugging active, WP_DEBUG_LOG can send errors to wp-content/debug.log or another configured path. The log may include notices and warnings as well as fatal errors, and debug output can expose sensitive details. Avoid displaying errors publicly; when finished, turn debugging off and protect or remove any logs you created. Consult the WordPress debugging handbook and the Site Health screen documentation.
Recommended Free Tools
Escalate with evidence when the issue persists
Contact your hosting provider if you cannot regain access, the recovery email is missing, or the problem requires server-level access. For a plugin-specific issue, you can also seek help through the relevant support forum. A concise report helps others investigate without requiring unrestricted access to your site.
- The exact error text, affected page, and time it began.
- What changed shortly before the failure, including plugin, theme, WordPress, or PHP updates where known.
- WordPress, PHP, and relevant plugin or theme versions, if available.
- What you tested and whether each step changed the symptom.
- A reviewed, sanitized Site Health export or relevant log excerpt; remove secrets and other sensitive information before sharing.
WordPress’s troubleshooting documentation also recommends contacting a professional hosting provider when recovery steps do not resolve the problem.
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.
