It’s awesome that there are tens of thousands of plugins made by different developers, all created with the intention of serving different purposes. That said, there is nothing that guarantees that what one developer has created won’t conflict with something else on your site.
Have you encountered an unexpected issue with Swift Performance? Our plugin uses best practices to ensure compatibility on as many WordPress sites as possible. Nevertheless, we cannot guarantee 100% compatibility with all plugins and themes. The only thing we can promise is that we do our utmost to resolve any possible conflict.
In this tutorial, we’ll walk through how to locate and troubleshoot theme or plugin conflicts.
We highly recommend using the Health Check & Troubleshooting plugin as it allows you to run a conflict check without affecting normal visitors to your site. However, if you cannot install plugins, please use the guide below.
By following the steps below, you should be able to determine if the issue is the result of code from another plugin.
Test for Theme Conflicts
To test for a theme conflict:
- Activate a default theme, such as the TwentySeventeen or TwentyNineteen, or any default theme made by WordPress team.
- Check to see if the issue still occurs.
If the issue doesn`t occur after having activated the default “Twenty…” theme, your theme is causing a conflict with Swift Performance. Please contact our Support Team.
If the issue continues to occur, you should then test for plugin conflicts (below)
Test for Plugin Conflicts
To test for a plugin conflict:
- Deactivate ALL plugins.
- Activate Swift Performance.
- Check to see if the issue occurs.
If the issue does not occur, one (or more) of your plugins is causing a conflict with Swift Performance. To determine which plugin(s) is causing the conflict, follow these steps:
- Activate each plugin one by one.
- Check to see if the issue occurs after each plugin is activated.
What if Issue happens With No Plugins & Default Theme
As much as we’d love to help, the issue is not caused by our plugin. This may be a WordPress issue, a conflict with your specific setup or something related to your server or webhost. Opening a topic in the WordPress support forums may help point you in the right direction.