How Do I Identify Conflicting WordPress Plugins?
Your WordPress website was working perfectly yesterday. Today, the contact form has stopped sending messages, the homepage looks completely different, or visitors are complaining that certain buttons no longer work. You haven’t deliberately changed the design, so what has gone wrong?
One possible explanation is a WordPress plugin conflict. Plugins add useful features to your website, but occasionally two plugins interfere with each other, or a plugin stops working properly alongside your theme, WordPress version or server software.
For a small business owner, this can be particularly frustrating. Your website might still be online, giving the impression that everything is fine, while important features such as enquiry forms, booking systems or online payments are failing in the background.
The good news is that there are practical ways to investigate plugin conflicts without immediately deleting software or rebuilding your website. The important thing is to work methodically, identify what changed and test possible causes without putting your business website at unnecessary risk.
Quick Answer
To identify conflicting WordPress plugins, start by checking which features have stopped working and whether any plugins were recently installed or updated. Go to Plugins > Installed Plugins in your WordPress dashboard and review the active plugins, particularly those performing similar tasks.
The safest way to investigate is on a staging website, where plugins can be deactivated and tested without affecting visitors. Disable one suspected plugin, check whether the problem disappears, then reactivate it and continue testing until you identify the cause.
If you cannot use a staging website, consider the WordPress troubleshooting tools available through the official Health Check plugin. Avoid deactivating essential plugins on a live business website without a backup and a clear recovery plan.
What Is a WordPress Plugin Conflict?
A WordPress plugin conflict happens when software components don’t work together as expected. This might involve two plugins attempting to control the same feature, a plugin interfering with your theme, or an extension using code that isn’t compatible with your current WordPress environment.
For example, imagine your cleaning company’s website uses one plugin to optimise page loading and another to perform similar optimisation tasks. Both might try to modify the same stylesheets or JavaScript files. Depending on their settings, this could result in missing design elements, broken animations or pages that look different to visitors.
Conflicts don’t always involve two plugins. A single plugin may become incompatible with a WordPress update, a theme change or a newer PHP version. PHP is the programming language used to run WordPress, and compatibility with the server’s PHP version is an important consideration.
It’s also worth understanding that a plugin being active doesn’t automatically mean it’s working correctly. Some problems only become visible when visitors complete a particular action, such as submitting a form, booking an appointment or proceeding through an online checkout.
What Are the Common Signs of Conflicting WordPress Plugins?
Plugin conflicts can affect different parts of a website, so there isn’t one warning sign that confirms a conflict. However, certain problems are worth investigating, particularly when they appear shortly after installing or updating software.
Your Website Layout Suddenly Changes
Headings may use different fonts, images might disappear, menus could become misaligned or large white spaces may appear between sections. These problems can occur when a plugin interferes with the files responsible for displaying the website’s design.
If the website looks correct while you’re logged in but broken when you’re logged out, caching or optimisation settings are worth checking. Some caching systems deliver different versions of pages to administrators and ordinary visitors.
Your Contact Forms Stop Working
A contact form may stop submitting messages, display an error or fail to deliver emails. Plugin conflicts are one possible cause, especially if security or optimisation settings interfere with the form’s scripts or requests.
However, email delivery problems can also come from server settings, incorrect email configuration or problems with the website’s mail service. Don’t assume a plugin conflict is responsible until those possibilities have been considered.
Your WordPress Dashboard Becomes Unresponsive
You may find that buttons in the dashboard stop responding, editing screens fail to load or a page builder becomes stuck. These symptoms can sometimes be caused by JavaScript errors or incompatible software.
If the dashboard becomes inaccessible altogether, the investigation may require help from your hosting company or someone familiar with WordPress recovery procedures.
Your Website Becomes Noticeably Slower
Some plugins perform demanding tasks or duplicate work already handled by another plugin. For example, multiple optimisation tools may process the same files, while other plugins may run expensive database queries or background tasks.
Slow loading isn’t proof of a conflict, but a sudden change after installing software is worth investigating. Hosting performance, image sizes and server resources should also be considered.
Your Website Displays Errors
Errors such as a blank screen, a critical error message or a failed update can sometimes involve plugin code. WordPress may send an automated recovery email when certain fatal errors occur, which can help identify the affected component.
If you receive a WordPress recovery email, keep it and review the details. It may provide useful evidence, although the plugin mentioned in an error isn’t always the original cause of the problem.
Why Do WordPress Plugins Conflict With Each Other?
WordPress plugins are created by different developers. Each plugin has its own purpose, settings and code. Although WordPress provides standards to help developers build compatible software, not every combination of plugins, themes and hosting environments can be tested in advance.
Problems may arise when two plugins modify the same website feature, load incompatible scripts or use settings that interfere with each other. A plugin may also rely on an older version of a library or behave differently after another component is updated.
Conflicts are particularly worth considering when a website contains several plugins that perform overlapping tasks. That doesn’t mean every overlapping plugin combination will fail, but unnecessary duplication can make a website more complicated to maintain and troubleshoot.
The official WordPress plugin management documentation explains how plugins can be activated, deactivated and managed through the dashboard.
How to Identify Conflicting WordPress Plugins: Step-by-Step
Step 1: Identify Exactly What Has Stopped Working
Before touching any plugins, write down the problem. Does the homepage look wrong? Has a contact form stopped working? Are visitors unable to complete a purchase? Is the problem limited to mobile phones?
Try to reproduce the issue and note which page or action triggers it. A clear description helps you test whether a change has actually fixed the problem.
Step 2: Check for Recent Changes
Think about when the problem started. Were any plugins installed, updated or reconfigured? Did WordPress update automatically? Was the theme changed, or did your hosting company update PHP?
If you know the problem began immediately after a particular change, that gives you a sensible starting point. However, timing alone doesn’t prove that the most recently updated plugin is responsible.
Step 3: Review Your Installed Plugins
Log in to WordPress and go to Plugins > Installed Plugins. Review the active plugins and identify any that perform similar tasks.
Pay particular attention to caching, optimisation, security, image processing, SEO, contact forms and page builders. These categories can affect important parts of the website, although plugins in any category can potentially cause problems.
Don’t assume that having a large number of plugins automatically means the website is broken. Quality, compatibility, configuration and maintenance matter more than a simple plugin count.
Step 4: Create a Complete Website Backup
Before making changes, ensure you have a recent backup containing both the website files and database. Check that the backup can be restored and that you understand the recovery process.
This is particularly important for ecommerce websites, booking systems and membership sites, where restoring an older database could overwrite recent customer activity.
Step 5: Use a Staging Website
A staging website is a separate copy of your live website used for testing. Many hosting providers offer staging tools, although availability depends on your hosting package.
On staging, you can deactivate plugins, change settings and test updates without immediately affecting customers. This is generally the safest environment for investigating a suspected conflict.
Make sure the staging site doesn’t send real customer emails, process live payments or create duplicate bookings during testing. These features may need to be disabled or placed into test mode.
Step 6: Deactivate Suspected Plugins One at a Time
Start with the plugins most closely related to the problem. If the website’s layout is broken, investigate recently changed optimisation or page builder plugins before unrelated tools.
- Record the current plugin settings and active status.
- Deactivate one suspected plugin on the staging website.
- Clear the relevant cache if needed.
- Repeat the action that originally caused the problem.
- Record whether the issue remains or disappears.
- Reactivate the plugin before testing another suspected plugin, unless your testing plan requires a different combination.
Testing one change at a time helps you understand which component affects the problem. However, some conflicts only occur when two particular plugins are active together, so further testing may be needed.
Step 7: Test the Suspected Plugin Combination
If disabling one plugin makes the problem disappear, you have identified a useful clue, not necessarily a complete diagnosis. The plugin might be faulty, incorrectly configured or incompatible with another component.
On staging, reactivate the suspected plugin and confirm that the problem returns. Then test whether the issue occurs when another relevant plugin is disabled. This can help establish whether the problem involves a particular combination rather than one plugin working incorrectly on its own.
Step 8: Check the Website After Every Change
Don’t limit testing to the WordPress dashboard. Open the public website while logged out and check the affected pages on desktop and mobile.
If your website accepts enquiries, test the contact form. If you run an online shop, check the basket and checkout using safe test procedures. If you provide appointments, make sure the booking process still works.
A plugin change that makes the homepage look normal but breaks the contact form isn’t a successful repair.
Step 9: Record Your Findings Before Applying a Fix
Keep a simple record of the plugins tested, their versions, the changes made and the results. This is especially helpful if you need to contact a plugin developer or hosting provider.
Once you’ve identified the likely conflict, choose a suitable solution and test it on staging before applying it to the live website.
How Can I Use WordPress Health Check to Find Plugin Conflicts?
WordPress has a Site Health feature under Tools > Site Health, which provides information about your website’s configuration and certain technical issues. However, the standard Site Health screen doesn’t automatically identify every plugin conflict.
The official Health Check & Troubleshooting plugin provides an additional troubleshooting mode. When available and working correctly, this allows an administrator to test the website with plugins disabled for their own session while ordinary visitors continue seeing the normal website.
This can be useful when you don’t have a staging environment. However, it isn’t completely risk-free. Actions performed during troubleshooting may still affect real website data, and background tasks or server-side plugin behaviour may not be isolated in the same way as the administrator’s viewing session.
For business-critical websites, particularly those handling payments, bookings or customer records, staging remains the preferred option.
Basic Health Check Troubleshooting Process
- Make sure a complete backup is available.
- Install the official Health Check & Troubleshooting plugin if appropriate.
- Open Tools > Site Health.
- Find the Troubleshooting section or tab added by the plugin.
- Enable troubleshooting mode for your administrator session.
- Check whether the original problem still occurs.
- Enable relevant plugins individually and repeat the test.
- Exit troubleshooting mode when finished.
If the problem disappears in troubleshooting mode and returns when a particular plugin is enabled, you’ve found a useful lead. Continue investigating before permanently removing or replacing anything.
Which Types of WordPress Plugins Are Most Likely to Conflict?
There isn’t a reliable rule that one plugin category is always more troublesome than another. However, plugins that modify the same parts of a website deserve particular attention because their settings can overlap.
Caching and Performance Plugins
These plugins may manage page caching, stylesheet optimisation, JavaScript loading and other performance features. If several tools attempt similar changes, the combined configuration may cause unexpected behaviour.
Security Plugins
Security plugins can restrict requests, protect login pages and filter suspicious activity. Occasionally, a security rule may interfere with a legitimate plugin feature, such as a form submission or connection to an external service.
Page Builders and Design Plugins
Page builders, theme extensions and design plugins can all affect the appearance of a website. Compatibility problems may result in missing sections, broken layouts or editing tools that stop responding.
Image Optimisation Plugins
Image optimisation tools may resize, compress or change the way images are delivered. If several tools modify the same images or loading behaviour, unexpected display problems can occur.
Contact Form and Email Plugins
Form plugins and email delivery tools often work together, but configuration problems can prevent messages from reaching the intended destination. The issue may involve a plugin conflict, an incorrect setting or a separate mail server problem.
SEO Plugins
Using multiple SEO plugins with overlapping functions can lead to duplicate metadata, conflicting settings or uncertainty about which tool controls particular features. That doesn’t necessarily break the website, but it can create unnecessary complexity.
Can Two WordPress Caching Plugins Cause Website Problems?
Yes. Running multiple full-page caching or overlapping optimisation systems can cause problems when their settings interfere with each other. For example, one plugin may create cached pages while another changes the stylesheets or JavaScript files those pages depend on.
Visitors might then receive an outdated page with newer design files, or a combination of files that doesn’t display correctly. This can sometimes produce missing fonts, broken menus, unexpected white spaces or animations that fail to work.
However, not every combination of performance tools is incompatible. A page cache, image optimisation service and content delivery network can work together when properly configured. The important distinction is whether their functions overlap or conflict.
If you suspect a caching conflict, identify every active caching layer, including WordPress plugins, hosting-level caching and any content delivery network. Review their settings before removing anything.
Don’t assume that clearing the cache permanently fixes the problem. If the issue returns after the cache is rebuilt, the underlying configuration may still be incorrect.
What If a Plugin Conflict Started After an Update?
WordPress plugins need updating for security, compatibility and improvements. Most updates work without problems, but occasionally an update can introduce an issue or reveal a conflict that wasn’t previously visible.
If the problem started after an update, check which plugin versions changed and whether the developer has published compatibility information. Look for reported problems in the plugin’s support forum or official documentation.
A previous plugin version may help with diagnosis, but rolling back software can introduce security risks or compatibility problems. Don’t downgrade plugins casually, especially on a live business website.
If the update affected an important feature, ask the plugin developer or your website provider for guidance. Where possible, test any proposed fix on staging before applying it to the live site.
What Should I Do Once I’ve Identified the Conflicting Plugin?
Finding the likely cause is only the first part of the job. The next step is choosing a solution that restores the website without removing features your business depends on.
Check for an Available Update
The plugin developer may already have released a fix. Check the current version, compatibility information and release notes before making changes.
Review the Plugin Settings
Sometimes the problem is caused by a particular option rather than the plugin itself. For example, disabling one JavaScript optimisation setting may restore a broken menu while allowing the plugin’s other features to continue working.
Contact the Plugin Developer
If you can reproduce the issue, provide the developer with the plugin versions, WordPress version, PHP version and a description of the problem. Screenshots and relevant error messages can also help.
Consider Replacing an Unnecessary Plugin
If two plugins duplicate the same function, you may be able to simplify the setup by keeping the one that best meets your needs. However, check what each plugin controls before removing it.
Test the Final Configuration
After applying a fix, check the public website, contact forms, mobile layout and any other important functions. If the website processes payments or bookings, use appropriate test procedures to confirm those systems still work.
Don’t consider the problem resolved simply because the original error message has disappeared. The website needs to function correctly as a whole.
WordPress Plugin Conflict Troubleshooting Table
| Problem | Possible cause | What to investigate |
|---|---|---|
| Homepage looks broken when logged out | Caching or stylesheet optimisation conflict | Public-page cache and performance settings |
| Contact form stops sending | Plugin interference or email configuration | Form plugin, security rules and mail delivery |
| Website becomes slow after an update | Resource-heavy plugin or overlapping tasks | Recent changes and performance activity |
| Page builder won’t load | JavaScript or compatibility problem | Page builder extensions and recent updates |
| Images disappear | Image delivery or optimisation issue | Image plugins, file paths and loading errors |
| Critical error appears | PHP error or incompatible component | Recovery email and technical error logs |
| Checkout stops working | Plugin, theme or payment integration problem | Safe staging tests and payment gateway logs |
| Problem disappears when a plugin is disabled | Suspected plugin involvement | Reproduce the issue and test combinations |
These symptoms are clues rather than proof. A problem that looks like a plugin conflict can sometimes be caused by hosting restrictions, missing files, incorrect settings or a separate WordPress issue.
Expert Insight From Daren Ward
Having worked with business websites since 2004, one thing I would always advise is not to judge a WordPress website simply by how it looks when you’re logged in. A website can appear perfectly normal in the administrator’s account while ordinary visitors are seeing something completely different.
I’ve encountered WordPress websites where several performance tools were installed, including plugins carrying out overlapping caching and optimisation tasks. When investigating this type of setup, I wouldn’t immediately assume that one particular plugin was faulty. I would first establish which tools were active, what each one was doing and whether their settings were interfering with each other.
I would also pay attention to anything left behind from previous development work. A website can accumulate plugins that are no longer needed, tools that duplicate existing features and settings that nobody has reviewed for years. That makes it much harder to identify the real cause when something stops working.
My advice is to avoid the temptation to deactivate everything and hope for the best. Work through the problem carefully, preferably on staging, and test the public website after each change. For a business website, the goal isn’t simply to remove an error. It’s to make sure the website is reliable, easy to use and still capable of generating enquiries and sales.
Warning: Don’t Deactivate All Plugins on a Live Business Website
Deactivating plugins can interrupt important website functions. An online shop may lose payment or checkout features, a booking system may stop accepting appointments, and a contact form may become unavailable. Security and backup services may also be affected.
Before troubleshooting, create a complete backup and confirm that it can be restored. Use a staging website whenever possible. If you must investigate on a live website, understand the risks, choose a suitable maintenance period and have a recovery plan.
Never delete a plugin simply because disabling it appears to fix a problem. Some plugins store settings or data that may be affected by removal. Identify what the plugin does and whether it is still required before deciding to replace or uninstall it.
Action Checklist: Identify WordPress Plugin Conflicts
- Write down exactly what has stopped working.
- Check whether the problem affects visitors, administrators or both.
- Review recently installed, updated or reconfigured plugins.
- Look for plugins with overlapping functions.
- Confirm that a complete, restorable backup is available.
- Use a staging website for troubleshooting wherever possible.
- Deactivate suspected plugins individually and test the results.
- Check whether the problem returns when a suspected plugin is reactivated.
- Test combinations of plugins when necessary.
- Consider Health Check troubleshooting mode if staging isn’t available.
- Review relevant error messages and plugin developer guidance.
- Test contact forms, menus, mobile layouts and other important functions.
- Record the final changes and monitor the website afterwards.
Frequently Asked Questions About Conflicting WordPress Plugins
1. How do I know if two WordPress plugins are conflicting?
A possible sign is that a website problem disappears when one plugin is deactivated and returns when it is reactivated. However, that doesn’t automatically prove two plugins are conflicting. The issue may involve the plugin itself, its settings, the theme or server configuration. Testing different combinations on staging can help identify the relationship.
2. Can I identify plugin conflicts without deactivating plugins on my live website?
Yes. A staging website allows you to test changes separately from your live website. The official Health Check & Troubleshooting plugin also provides a troubleshooting mode that can help administrators investigate without changing the normal plugin experience for visitors. However, staging remains preferable for websites with important transactions or customer data.
3. Can two caching plugins cause WordPress problems?
Yes. Two caching or optimisation tools may interfere when they attempt to control the same files or caching behaviour. This can sometimes lead to outdated pages, broken styling or missing features. However, different performance tools can also work together when correctly configured, so the settings and overlapping functions matter more than simply having two plugins installed.
4. Why did my WordPress website break after updating a plugin?
The update may have introduced a compatibility problem, changed a setting or revealed an existing conflict. Check which plugin was updated, review its release notes and compare the problem with any reported issues. Don’t immediately downgrade or delete the plugin without checking the consequences and ensuring a suitable backup is available.
5. Will deactivating a WordPress plugin delete its settings?
Many plugins retain their settings when deactivated, but behaviour varies between plugins. Deactivation and deletion are different actions, and some plugins provide options for removing stored data during uninstallation. Always check the plugin’s documentation before removing it, especially if it manages bookings, orders, customer information or important website settings.
6. How many WordPress plugins are too many?
There isn’t a fixed number that automatically makes a WordPress website unreliable. A website with many well-maintained plugins can work properly, while a website with only a few poorly configured plugins can experience serious problems. Focus on quality, compatibility, security, performance and whether each plugin provides a feature your business actually needs.
7. Can a plugin conflict cause the WordPress white screen of death?
Yes. A plugin-related PHP error can sometimes prevent WordPress from displaying a page correctly. However, a blank screen can also result from theme problems, server errors or other technical issues. Check for WordPress recovery emails and relevant error logs before deciding which component is responsible.
8. Can plugin conflicts make my website look different when I’m logged out?
Yes. Caching and optimisation settings can sometimes affect the public version of a website differently from the administrator’s view. If the website looks correct while logged in but broken when logged out, compare the same pages in a private browser window and investigate the active caching and styling systems.
9. Can WordPress security plugins interfere with contact forms?
They can. Some security rules may block requests that a contact form needs to submit information. However, form failures can also involve email delivery settings, JavaScript errors or server configuration. Check the form’s error messages and relevant security logs before changing protection settings.
10. Should I delete a plugin that is causing a conflict?
Not automatically. The problem may be resolved through an update, configuration change or compatibility fix. If the plugin is no longer needed or duplicates another tool, removal may be sensible, but first check what it controls and whether deleting it could affect website data or important features.
11. Can changing the PHP version cause plugin conflicts?
Yes. A plugin may use code that isn’t compatible with a newer PHP version, particularly if it hasn’t been maintained. Before changing PHP, check compatibility with WordPress, your theme and important plugins. Take a complete backup and test the change on staging where possible.
12. What should I do if I cannot access WordPress because of a plugin conflict?
If the dashboard is inaccessible, check whether WordPress has sent a recovery mode email. If that doesn’t help, contact your hosting company or website provider. Technical recovery may involve disabling a plugin through the hosting file manager or another server-level method, but these actions should be handled carefully to avoid further problems.
Summary: Finding WordPress Plugin Conflicts Without Making Things Worse
WordPress plugin conflicts can cause anything from minor layout problems to serious failures involving contact forms, booking systems and online payments. However, not every website problem is caused by a plugin, so it’s important to investigate rather than make assumptions.
Start by identifying the symptoms, reviewing recent changes and checking for overlapping plugins. Use staging to test suspected components, change one thing at a time and confirm whether the problem can be reproduced. Once you’ve identified the likely cause, choose a suitable fix and test the complete website before considering the job finished.
A well-maintained WordPress website doesn’t need dozens of unnecessary plugins performing the same tasks. It needs the right tools, correctly configured, regularly updated and checked to make sure customers can use the website without problems.
Getting Help With WordPress Plugin Conflicts
If your website is experiencing plugin conflicts, broken layouts or unexplained technical problems, our WordPress maintenance service is one option for getting help with website stability, updates and troubleshooting. You can also explore A to Z Website Solutions for further information about website support and development.
Key Takeaways
- Plugin conflicts can involve two plugins, a theme, WordPress itself or the server environment.
- Broken layouts, failed forms and dashboard errors are possible warning signs, not proof of a conflict.
- Review recent updates and plugins with overlapping functions.
- Always create a restorable backup before significant troubleshooting.
- Staging is generally the safest place to test suspected conflicts.
- Deactivate suspected plugins methodically and reproduce the original problem.
- Health Check troubleshooting mode can help investigate certain problems without changing the normal visitor experience.
- Finding the likely cause is only the beginning; the final website must be tested thoroughly.
Found This Helpful? Share It
If you found this article useful, please share it with other business owners who might find it helpful too.
A quick share on LinkedIn, Facebook or your favourite social platform could help someone else find the advice they need.