wpaluchmits

MITS Profiler is a tool by <a href="https://mits.pl" rel="nofollow ugc">MITS</a> — a WordPress and WooCommerce agency based in Poland. It adds a diagnostic bar to any page by appending <code>?mits_prof=1</code> to the URL. It captures timing data from the moment PHP starts and presents it in a dark-themed panel at the bottom of the page — visible only to logged-in administrators.
Tabs included:
<ul>
<li>Timeline — absolute and relative timing between WordPress lifecycle hooks (plugins_loaded → init → wp_head → wp_footer)</li>
<li>Hooks — top 50 slowest action/filter hooks with total time and call count</li>
<li>Options — most-queried WordPress options + full autoload audit with sizes</li>
<li>Plugins — loaded PHP file sizes per plugin (proxy for load time)</li>
<li>Assets — all enqueued scripts and styles, external ones highlighted</li>
<li>HTTP — outgoing wp_remote_* requests with response time and status</li>
<li>SQL — all database queries with slow-query highlighting (requires SAVEQUERIES)</li>
<li>PHP — PHP version, OPcache status and hit rate, memory and execution limits</li>
</ul>
Key features:
<ul>
<li>Zero HTTP loopback — works behind Cloudflare, reverse proxies and strict firewall rules</li>
<li>No external dependencies or requests</li>
<li>Admin-only: the panel and all data are never shown to guests</li>
<li>Export to JSON or CSV for offline analysis</li>
<li>Works on front-end pages, WooCommerce pages, and WP Admin</li>
</ul>
SQL query logging requires adding the following to <code>wp-config.php</code>:
<pre><code>define('SAVEQUERIES', true);
</code></pre>

MITS Profiler

Lightweight WordPress performance profiler. No HTTP loopback requests — works behind Cloudflare and any proxy.

Viktor Szépe

<h4>Only for development!</h4>
<h4>Now with OPcache memory consumption support</h4>
This plugin dumps the colorized filenames and memory consumptions or file sizes after the normal WordPress HTML output, after the closing html tag. This generates invalid HTML but gives you an overview of loaded plugins and the current theme.
What’s running lists all files parsed and executed by the PHP engine. It can be used for plugin or theme refactoring.
<h4>Now you can highlight your own plugin and theme</h4>
Provide a part of its path in wp-config.php:
<pre><code>define( 'WHATS_RUNNING_HIGHLIGHT', 'wp-content/plugins/my-plugin' ); </code></pre>
<h4>Color codes</h4>
<ul>
<li>your code is highlighted with YELLOW background</li>
<li>plugin files are in BLUE</li>
<li>themes files are in ORANGE</li>
<li>files in the wp-includes directory are in GREEN</li>
<li>files in the wp-admin directory are in GREY</li>
<li>all other files are in RED</li>
<li>VIOLET bar after the filename represents the file size ( 0.5 kB/px )</li>
<li>DARK MAGENTA bar after the filename represents the OPcache memory consumption ( 1 kB/px )</li>
</ul>
<h4>Links</h4>
You can watch <a href="https://core.trac.wordpress.org/ticket/28364" rel="nofollow ugc">WP core bug #28364</a> to get more information about <a href="https://github.com/szepeviktor/WPHW/blob/master/wp-entry-points.md" rel="nofollow ugc">WordPress entry points</a>.
You can find some documentaion here what makes a WordPress plugin efficient: https://github.com/szepeviktor/WPHW
Development of this plugin goes on on <a href="https://github.com/szepeviktor/whats-running" rel="nofollow ugc">GitHub</a>.

What's running

Lists WordPress require() calls mainly for plugin code refactoring.

MITS Profiler vs What's running