Are there alternative plugins to P3 (Performance Profiler Plugin)? • WordPress Help

Unless GoDaddy relives it one of these days, the reality is that currently the famous P3 plugin a great way to measure the performance of our WordPress, is dead and buried without updates or support.

And it's a shame, because it was a great way to analyze which plugins and processes consumed more resources our installation .

So, in the absence of someone reviving it, we will see possible alternatives to this useful plugin, to be able to analyze the performance of WordPress .

UsageDD allows to monitor the use of resources of your WordPress installation by using a small box at the bottom of each page of your site.

This box shows the MySQL queries memory used by the code on the page ina, what version of PHP you use, the total load time and even the TTFB .

You can use the data to show you if you have loaded too many plugins, the topic overloads too much or if something goes wrong. The best thing is that the plugin practically does not consume any resources.

You only have to load your site with one configuration or another and compare the use of resources, yes, on your own.

In addition to SEO and security checks, this plugin does optimization and performance checks of your website .

  • Detects plugins and issues with security and / or performance issues
  • Performs load speed checks of your site, showing a performance indicator
  • It gives you recommendations to improve the load results of your site.

Interesting plugin, especially for developers that shows a lots of tabs with valuable information:

  • PHP
  • Memory usage
  • Load time
  • System and server
  • WordPress version and language
  • Definitions of constants, cookies, FTP and SSH [19659011] Tables user and usermeta
  • Requests made by WordPress, with values ​​of each request and detailed information
  • Information of requests made by each plugin and topic
  • Information of all requests made from the wp-content folder
  • Conditional tags and their values ​​
  • Profiles and capabilities
  • HTML inspector of the quality of the generated code, showing the console errors.
  • Functions and information of each cron process
  • Contents of the cache
  • Hooks and filters
  • All about permalinks and rewrites
  • Functions, and their contents of arrays to hooks and filters
  • All constants, classes, shortcodes, transients, post meta data
  • Data of $ _ POST ; $ _ GET and follow-up debug
  • Hooks and executions of WooCommerce.
  • and much more …

For my part it is a clear winner in terms of information displayed, really impressive .

Another winner, for the amount of information offered from a single menu in which you access all the information, enormously detailed, of everything that analyzes.

  • Petitions to the Database
  • Hooks
  • Topic
  • PHP Errors
  • Requests
  • Rewrite Rules
  • Scripts and Styles
  • Languages ​​
  • HTTP Requests
  • Profile Capability Checks [19659011] Redirects
  • AJAX Requests
  • REST API
  • Environment Information
  • … and much more

Which one is better?

If I have to get wet I'll tell you that none of the 2 first size, they are too simple .

On the other hand, the information offered by both Debug Objects and Query Monitor is very technical, not understandable to the average user .

But if I have to choose of course between these last two, I prefer Query Monitor which analyzes many more aspects of your installation, in more detail, and gives very valuable information for both the developer and the webmaster.

Well analyzed, it is really useful information to improve the performance and improve the WPO of any web .

Loading …

That may also help you: