About the Plugin Profiler
SitePulse has a Plugin Profiler (also called Hook Analysis) that measures how every active plugin affects your WordPress site performance. It does not scan for plugin conflicts or duplicate classes. Instead, it hooks into every WordPress action and filter on every page load and records how long each plugin spends executing callbacks.
How It Works
The Plugin Profiler wraps every do_action() and apply_filters() call with timing instrumentation. For each hook it records:
- Which plugin registered each callback
- How long each callback took to execute
- The total time spent on each hook
- The cumulative impact on page generation time
The data is collected on every page load and displayed in the Plugin Profiler view within the SitePulse dashboard. You can see exactly which plugins are contributing to slow page loads and which hooks they are spending time on.
How to Use the Plugin Profiler
Navigate to the SitePulse dashboard and open the Plugin Profiler. You will see a list of all active plugins sorted by total execution time. Click on any plugin to expand the view and see which hooks it registers callbacks on and how long each callback takes.
This information helps you identify plugins that are slowing down your site without guessing. If one plugin consistently accounts for a large fraction of page generation time, consider replacing it with a lighter alternative or using the Per-Page Plugin Disabler to limit it to only the pages where it is needed.
What the Plugin Profiler Does Not Do
The Plugin Profiler does not detect plugin conflicts, scan for duplicate PHP class names, or compare plugin versions against known issues. It is a performance measurement tool, not a conflict detection tool. For plugin conflict troubleshooting, deactivate plugins one at a time while monitoring site behavior.