devmarvs

<p>Block Weight Inspector adds a sidebar panel in the block editor that maps blocks in the current post/page to the CSS and JS assets they register. It estimates local asset sizes, highlights top offenders, and exports a JSON report. It can also generate a suggested conditional-loading snippet to help you dequeue assets when a block is not present.<br />
It also adds a Tools -> Block Weight Inspector screen for auditing existing posts without opening the editor.<br />
Note: The inspector preserves block comment delimiters when analyzing content so <code>parse_blocks()</code> remains accurate after sanitization.</p>
<p>Key features:</p>
<ul>
<li>Block -> asset mapping using registered block metadata.</li>
<li>Estimated size for local assets.</li>
<li>Top offenders summary and full asset list.</li>
<li>JSON export for sharing or auditing.</li>
<li>Suggested conditional-loading rules (review before use).</li>
</ul>


Block Weight Inspector

See which blocks load which CSS/JS assets on a page and estimate their weight.

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.

Block Weight Inspector vs What's running