VIII. Plugin Impact (Paid)
Question: Which plugin is slowing down my site?
Runtime impact analysis for WordPress plugins. No more disable-test-enable cycles — see exactly which plugin causes warnings, fatals, slow hooks, and memory pressure.
This is the dashboard that sells Logystera. Screenshot it for the homepage.
Row 1 — Plugin KPIs
| Panel | Type |
|---|---|
| Plugins Installed | stat |
| Plugins Updated (24h) | stat |
| Plugins Causing Warnings | stat |
| Plugins Causing Fatals | stat |
Row 2 — Error Sources
| Panel | Type |
|---|---|
| Top Warning Sources by Plugin | bar_chart |
| Top Fatal Sources by Plugin | bar_chart |
Row 3 — Hook Performance
| Panel | Type |
|---|---|
| Hook Overhead Trend | line_chart |
| Slow Hooks by Plugin | bar_chart |
Row 4 — Change Impact
| Panel | Type |
|---|---|
| Plugin Updates Timeline | line_chart |
| Error Rate After Update | line_chart |
Why this matters
Typical WordPress debugging:
1. Site is slow
2. Disable plugin A → test → still slow
3. Enable plugin A, disable plugin B → test
4. Repeat 20 times
5. Give up
Logystera approach:
1. Open Plugin Impact dashboard
2. See: elementor-pro → 847 warnings, 12ms hook overhead
3. Done
Metrics used
| Metric | What it provides |
|---|---|
wp_php_warnings_total |
Warning count by source_type + slug |
wp_php_fatals_total |
Fatal errors by source |
wp_hook_timing_ms |
Hook execution time by hook name |
wp_hook_timing_count |
Hook call frequency |
wp_request_peak_memory_mb |
Memory per request (correlate with plugin activity) |
wp_state_changes_total |
Plugin install/update/delete events |