Este plugin no se ha probado con las últimas 3 versiones mayores de WordPress. Puede que ya no tenga soporte ni lo mantenga nadie, o puede que tenga problemas de compatibilidad cuando se usa con las versiones más recientes de WordPress.

Plugin Profiler

Descripción

Basic profiler for WordPress Plugins. Benchmarks any given plugin by testing response times with and without the plugin activated.

Plugin Profiler is on GitHub.

Bug reports (and pull requests) are welcomed on the Plugin Profiler GitHub repository.

Please note that GitHub is not a support forum.

Profiling a plugin

This plugin measures response times of any URL on your website in the following ways.

  • No plugins activated
  • Only the selected plugin(s) activated
  • All but the selected plugin(s) activated
  • All plugins activated

It then plots the response times in a chart and calculates the average response time time difference.

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.
Please note that this way of benchmarking leaves a lot of factors out – like additional HTTP requests caused by a plugin, etc..

Installing Plugin Profiler

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 so it’s loaded early.

Have a look at the installation instructions for details.

More information

Capturas

Instalación

Installing Plugin Profiler

  1. In your WordPress admin panel, go to Plugins > New Plugin, search for Plugin Profiler and click «Install now«
  2. Alternatively, download the plugin and upload the contents of plugin-profiler.zip to your plugins directory, which usually is /wp-content/plugins/.
  3. Create the file /wp-content/mu-plugins/profiler.php with the following contents.

    <?php

    if( ! defined( ‘ABSPATH’ ) ) {
    exit;
    }

    // load the plugin profiler plugin early
    require_once WP_PLUGIN_DIR . ‘/plugin-profiler/plugin-profiler.php’;

  4. Go to Tools > Plugin Profiler, set some configurations for the profile to run and have a look!

FAQ

I think I found a bug. What now?

Please report it on GitHub issues if it’s not in the list of known issues.

I have another question

Please open a topic on the WordPress.org plugin support forums.

Reseñas

15 de diciembre de 2017
The plugin is currently working, and showing the load time of all plugins, no plugins, all but one plugin you specify, and that one plugin only. Pretty good for showing clients how much their plugins are slowing down their site. I like this plugin better than the p3 profiler. WARNING: Copying and pasting the profiler.php file from the installation instructions will cause a white screen of death. You need to replace the quotes with normal quotes.
6 de febrero de 2017
I inherited an existing website with this plugin installed. I tried it 6 months ago but it was rating everything too good to be true, maybe because the code hasn't been updated for a while. Anyway, I'm not here to critise. I just want to say that when you delete the plugin, remember to delete the profiler.php file in the mu-plugins folder, otherwise you'll get a white screen of death 🙂
Leer todas las 3 reseñas

Colaboradores y desarrolladores

«Plugin Profiler» es un software de código abierto. Las siguientes personas han colaborado con este plugin.

Colaboradores

Traduce «Plugin Profiler» a tu idioma.

¿Interesado en el desarrollo?

Revisa el código , echa un vistazo al repositorio SVN o suscríbete al registro de desarrollo por RSS.

Registro de cambios

1.1.2 – February 20, 2015

Fixes

  • JavaScript error for servers requiring case-sensitive file URL’s.

1.1.1 – February 5, 2015

Improvements

  • Now marking request errors & deviating requests in result details
  • Better signature validating

Additions

  • Added results table showing all request details

1.1 – January 28, 2015

Improvements

  • Profiler now runs client-side.
  • Results are shown in a bar chart, which updates live. (needs IE9+)
  • Profiling can be paused & resumed.
  • Improved reliability of benchmark results.

1.0 – January 26, 2015

Initial release