- 摘要
- FDP allows you to **deactivate plugins on specific pages** for speed optimization
FDP allows you to **deactivate plugins on specific pages** for speed optimization, debugging and problem-solving.
It works for every page, blog posts, custom posts that are publicly queryable, archives and backend pages.
== Deactivate plugins on specific pages to improve the performance ==
With FDP you can **disable the entire plugins** where you don't need them. It will not only **clean up the assets** of third-party plugins, their PHP code will not run either. Hence, your pages will have **fewer HTTP requests and fewer database queries**.
You will **improve the TTFB (time to first byte) also when the page is not served by cache**.
Usually, the number of the needed plugin on a specific page is lower than the number of globally active plugins.
Why don't you keep the plugins active only on the pages where you need them?
Most of the plugins load their assets and query the database on all the pages, no matter if they do something useful. This causes many times a worsening of the performance.
With FDP no matter how many plugins you have, you can keep them active only where you need them.
== Deactivate plugins on specific pages to solve conflicts between plugins ==
With FDP you can preview the page loading specific plugins. This is very useful to detect which plugin is causing issues.
Look <a href="https://freesoul-deactivate-plugins.com/how-check-which-plugin-causes-issues/">How to check which plugin is causing issues in 1 minute</a> for more details.
If on a specific page you keep active only the plugins that you really need, most of the time the probability of having conflicts between plugins is lower.
Nulled Method:
此隐藏内容仅对以下用户组成员可见：Bronze Member
