Basic profiler for WordPress Plugins. Benchmarks any given plugin by testing response times with and without the plugin activated.<\/p>\n\n
\nPlugin Profiler<\/strong> is on GitHub.<\/p>\n \n
Bug reports (and pull requests) are welcomed on the Plugin Profiler GitHub repository<\/a>.<\/p>\n \n
Please note that GitHub is not<\/em> a support forum.<\/p>\n<\/blockquote>\n\n
Profiling a plugin<\/h4>\n\n
This plugin measures response times of any URL on your website in the following ways.<\/p>\n\n
\n
- No plugins activated<\/li>\n
- Only the selected plugin(s) activated<\/li>\n
- All but the selected plugin(s) activated<\/li>\n
- All plugins activated<\/li>\n<\/ul>\n\n
It then plots the response times in a chart and calculates the average response time time difference.<\/p>\n\n
While this way of profiling a plugin is very low-tech it can be interesting to measure the impact of a plugin on your site's response time.\nPlease note that this way of benchmarking leaves a lot of factors out - like additional HTTP requests caused by a plugin, etc..<\/p>\n\n
Installing Plugin Profiler<\/h4>\n\n
Since this plugin needs to filter out which plugins are activated for the profiling requests, it needs to be installed as a must-use plugin<\/strong> so it's loaded early.<\/p>\n\n
Have a look at the installation instructions<\/a> for details.<\/p>\n\n
More information<\/strong><\/p>\n\n
\n
- Developers; follow or contribute to the Plugin Profiler plugin on GitHub<\/a><\/li>\n
- Other WordPress plugins<\/a> by Danny van Kooten<\/a><\/li>\n
- @DannyvanKooten<\/a> on Twitter<\/li>\n<\/ul>\n\n\n
Installing Plugin Profiler<\/h4>\n\n
\n
- In your WordPress admin panel, go to Plugins > New Plugin<\/em>, search for Plugin Profiler<\/strong> and click \"Install now<\/em>\"<\/li>\n
- Alternatively, download the plugin and upload the contents of
plugin-profiler.zip<\/code> to your plugins directory, which usually is\/wp-content\/plugins\/<\/code>.<\/li>\nCreate the file
\/wp-content\/mu-plugins\/profiler.php<\/code> with the following contents.<\/p>\n\n<?php<\/p>\n\n
if( ! defined( 'ABSPATH' ) ) {\n exit;\n}<\/p>\n\n
\/\/ load the plugin profiler plugin early\nrequire_once WP_PLUGIN_DIR . '\/plugin-profiler\/plugin-profiler.php';<\/p><\/li>\n
Go to Tools > Plugin Profiler<\/strong>, set some configurations for the profile to run and have a look!<\/p><\/li>\n<\/ol>\n\n\n
\n
- I think I found a bug. What now?<\/dt>\n
Please report it on GitHub issues<\/a> if it's not in the list of known issues.<\/p><\/dd>\n
- I have another question<\/dt>\n