| Developer | wpcoretools |
|---|---|
| Update Time | April 6, 2026, 6:11 a.m. |
| PHP Version: | 7.4 + |
| WordPress Version: | 7.0 |
| Copyright: | GPLv2 or later |
| Copyright URL: | Copyright Information |
/wp-content/plugins/speedix/Minimal impact when configured properly. Use "Safe Mode" preset (10% sampling, 2ms threshold) for production sites. The plugin includes overload protection that automatically pauses profiling if overhead exceeds safe limits.
No. Speedix uses read-only profiling with built-in safety limits. If overhead gets too high, it automatically pauses for 1 hour. You can also disable at any time from Settings.
Debugging plugins show detailed info about the current request. Speedix takes a different approach - it aggregates performance data over time to identify persistent slow spots and trends across many page loads.
Check these in order:
Enable "Identify plugin sources" in Settings. Without this, hooks are captured but not attributed to specific plugins.
Appears when callbacks can't be traced to source files. Common causes: anonymous closures, dynamically generated functions, or code outside plugin/theme directories.
Yes, especially in Safe Mode. Sample rate ensures only 10-25% of requests are profiled, and overload protection prevents performance impact.
Default: 24 hours. Configurable from 1 hour to 7 days. Data is automatically cleaned up via WordPress cron.
The profiler measures uncached PHP execution. Cached pages bypass PHP entirely and won't appear in profiles - this is expected behavior since cached pages are already optimized.
Yes. Each site maintains its own profiling data. Network admins can access the dashboard on any site.