Conditions
- Server:
Apache on a shared hosting server.
WordPress 4.6.1-ja / Theme: Twenty Twelve
PHP: PHP-5.2.14 (it’s too old!!) / MySQL-5.5.21 - Plugins:
Here’s the list of activated plugins.
- IP Location Block:
Version: 0.3.0.0 and later.
Settings: ip-location-block-settings.json
The Validation timing shoule be set as “init” action hook. If you set it as “mu-plugins” (ip-location-block-mu.php), P3 would fail to measure the performance of this plugin because Must-use plugins would be into the race condition. 
Results
P3 (Plugin Performance Profiler) can investigate WordPress plugins’ performance by measuring their impact on your site’s load time.
This awesome tool has two mode to measure the performance. One is “Auto scan” which will access to both admin area and public facing pages under the confition of logged in as an admin. On the other hand, “Manual scan” mode can make it possible to freely access. So in this report, “Manual scan” had performed only by accessing front-end pages.
The following results were measured with a private window.
- Use case 1: – “Auto scan” (admin area + public facing pages)
- Use case 2: – “Manual scan” (only public facing pages)
