codetelemetrylab

<p>CodeTelemetryLab Admin Performance Inspector is a developer-focused performance profiling plugin built exclusively for the WordPress admin area. It instruments the WordPress request lifecycle in real time and presents all profiling data inside a clean, dedicated dashboard under Tools <span aria-hidden="true" class="wp-exclude-emoji">→</span> Admin Performance Inspector.</p>
<p>No configuration needed. Activate the plugin and instantly see what is slowing down your WordPress backend.</p>
<h4>What It Profiles</h4>
<p><strong>Admin Page Execution Time</strong><br />
Measures total request time from plugins_loaded to shutdown using microtime(true). Displays the precise execution time in milliseconds on the overview panel.</p>
<p><strong>Plugin Load Performance</strong><br />
Tracks the execution time of every active plugin using a lightweight MU-plugin drop-in. Displays a sortable table of all plugins with their individual load times and flags slow-loading plugins automatically.</p>
<p><strong>Database Query Profiling</strong><br />
Captures every SQL query executed during the admin request using WordPress’s native SAVEQUERIES constant. Displays total query count, slow query count, cumulative query time, and a full query list with origin file and line number. Slow queries (default threshold: 100ms) are visually flagged.</p>
<p><strong>Hook Execution Profiling</strong><br />
Times key WordPress hooks including init, admin_init, admin_menu, current_screen, and wp_loaded. Shows execution time and registered callback count for each hook.</p>
<p><strong>Memory Usage Monitoring</strong><br />
Displays current memory usage, peak memory usage, and percentage of PHP memory limit consumed — with a visual progress bar.</p>
<h4>Who Is This For?</h4>
<ul>
<li>WordPress developers diagnosing slow admin dashboards</li>
<li>Site administrators troubleshooting plugin conflicts</li>
<li>DevOps engineers benchmarking admin performance</li>
<li>Agencies auditing client site backends</li>
</ul>
<h4>Key Features</h4>
<ul>
<li>Zero configuration — activate and start profiling immediately</li>
<li>Single unified dashboard under Tools menu</li>
<li>Per-plugin load time table with slow plugin detection</li>
<li>Full SQL query list with execution time and origin</li>
<li>Configurable slow query threshold (default 100ms)</li>
<li>Hook timing table for monitored WordPress core hooks</li>
<li>Memory usage progress bar showing usage vs PHP limit</li>
<li>All output sanitized and escaped — security-first design</li>
<li>Access restricted to manage_options capability only</li>
<li>Fully translatable with .pot file included</li>
<li>Follows WordPress Coding Standards throughout</li>
<li>GPLv2 licensed — fully open source</li>
</ul>
<h4>Privacy</h4>
<p>CodeTelemetryLab Admin Performance Inspector does not collect, transmit, or store any data outside your WordPress installation. All profiling data is captured in memory during the current request only and displayed solely within your admin dashboard. No external API calls are made.</p>
<h3>Support</h3>
<p>For support, please use the WordPress.org support<br />
forum for this plugin.<br />
For enquiries, visit https://codetelemetrylab.vercel.app</p>
<h3>Credits</h3>
<p>Developed and maintained by CodeTelemetryLab.<br />
Plugin architecture based on the WordPress Plugin Boilerplate.</p>


CodeTelemetryLab Admin Performance Inspector

Profile your WordPress admin performance. Identify slow plugins, database queries, hook execution times, and memory usage from one clean dashboard.

Viktor Szépe

<h4>Only for development!</h4>
<h4>Now with OPcache memory consumption support</h4>
<p>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.</p>
<p><em>What’s running</em> lists all files parsed and executed by the PHP engine. It can be used for plugin or theme refactoring.</p>
<h4>Now you can highlight your own plugin and theme</h4>
<p>Provide a part of its path in wp-config.php:</p>
<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>
<p>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>.</p>
<p>You can find some documentaion here what makes a WordPress plugin efficient: https://github.com/szepeviktor/WPHW</p>
<p>Development of this plugin goes on on <a href="https://github.com/szepeviktor/whats-running" rel="nofollow ugc">GitHub</a>.</p>


What's running

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

CodeTelemetryLab Admin Performance Inspector vs What's running