Profile your website with Code Profiler and Freesoul Deactivate Plugins

If you want to measure the performance of your plugins and themes you can now use Code Profiler, the amazing plugin provided by Jerome Bruandet.

You will find a free version available on the official WordPress repository.

I invite you to read the plugin description for more information about the tool.

Code Profiler is the best alternative for P3 (Plugin Performance Profiler). P3 was not so bad to profile the performance of the active plugins, but it’s been abandoned for a long time. Now, we finally have a very good alternative. Many users were waiting for a tool like P3 that was updated and maintained. Now you can use Code Profiler.

I love it because it’s very light and you can also keep it active on a live site. Its consumption is practically zero. It works only when you start the profiling process.

Thanks to Code Profiler, you can see the contribution of each plugin and the theme in terms of execution time.

The PRO version has many other features such as scripts performance profiling.

Already FDP can give you some information about the execution time of the page, but you should deactivate one plugin after the other to have an idea of the contribution of each plugin.

Code Profiler makes it a lot easier. You can measure the contribution of plugins and themes in the same test.

Normally, during the profiling FDP will load the plugins that you set in the FDP settings.

From version, FDP will give you the possibility to select the plugins that you want to be active during the profiling.

You will find the submenu item Code Profiler under the gear icon in the FDP settings page.

Clicking on Code Profiler you will go to a settings page where for the profiling process, you can decide between loading the plugins according to the usual FDP settings or according to specific settings especially for the profiling.

By clicking on Code Profiler you will go to the settings page of the Code Profiler plugin, where you can set up all the options provided by the plugin.

In our example, the plugins that run during the profiling are those ones selected in the previous screen.