sapayth

<p>Script Report is a minimal and focused debugging tool for WordPress developers. It helps you audit and visualize JavaScript and CSS dependencies on any admin or frontend page.</p>
<p>When something loads out of order, loads twice, or slows down a page, Script Report helps you see exactly what is happening.</p>
<p>Use the Script Report link in the admin navbar on any page to open a complete breakdown of scripts and styles, their load order, dependencies, and origin.</p>
<h3>Why Use Script Report?</h3>
<p>Developers often ask:</p>
<p>Why is this script loading here<br />
Who enqueued this style<br />
Why is my dependency not working<br />
Is something loading twice<br />
What is affecting performance on this page</p>
<p>Script Report gives you clear answers instantly.</p>
<h3>What You Can Inspect</h3>
<h4>JavaScript</h4>
<p>View a complete breakdown of:</p>
<ul>
<li>Registered scripts</li>
<li>Enqueued scripts</li>
<li>Total required scripts</li>
<li>Load order</li>
<li>File size</li>
<li>Footer or header loading</li>
<li>Inline scripts</li>
<li>Enqueued by source</li>
<li>Required by dependencies</li>
</ul>
<h4>CSS</h4>
<p>Inspect styles with the same detailed structure:</p>
<ul>
<li>Registered styles</li>
<li>Enqueued styles</li>
<li>Total required styles</li>
<li>Load order</li>
<li>File size</li>
<li>Dependency relationships</li>
<li>Enqueued by source</li>
<li>Required by dependencies</li>
</ul>
<h4>Script Modules WordPress 6.5+</h4>
<p>Audit registered and enqueued script modules along with their dependency chains.</p>
<h3>Views</h3>
<p>Switch between two views:</p>
<p>List view<br />
Clean, structured overview of all scripts and styles.</p>
<p>Tree view<br />
Visual representation of dependency chains. Circular or missing dependencies are clearly flagged.</p>
<h3>Filtering</h3>
<p>Quickly filter by handle or source to narrow down large lists. Filtering works client side for fast inspection.</p>


Script Report

Debug and audit JavaScript and CSS loading in WordPress. Analyze dependencies, detect issues, and improve performance on any page.

Juliette Reinders Folmer

<p>Debug Bar Shortcodes adds a new panel to the <a href="https://wordpress.org/plugins/debug-bar/" rel="ugc">Debug Bar</a> that displays the registered shortcodes for the current request.</p>
<p>Additionally it will show you:</p>
<ul>
<li>Which function/method is called by the shortcode</li>
<li>Whether the shortcode is used on the current post/page/post type and how (only when on singular)</li>
<li>Any additional information available about the shortcode, such as a description, which parameters it takes, whether or not it is self-closing.<br />
<em>Want to control the additional information displayed about your own shortcodes ? You can! See the <a href="https://wordpress.org/plugins/debug-bar-shortcodes/faq/" rel="ugc">FAQ</a> for more info.</em></li>
<li>Find out all pages/posts/etc on which a shortcode is used</li>
</ul>
<p>This plugin is compatible with the <a href="https://wordpress.org/plugins/lrh-shortcode-list/" rel="ugc">LRH-Shortcode list</a> and the <a href="https://wordpress.org/plugins/shortcode-ui/" rel="ugc">Shortcake/Shortcode UI</a> plugins. Additional information about a shortcode provided to these plugins will be taken into account and made available through this plugin too.</p>
<h4>Why is it useful to have insight into the shortcodes ?</h4>
<p>There are a number of typical uses I can think of:</p>
<ul>
<li>
<p>If you are a <strong><em>blog author</em></strong>:</p>
<ul>
<li>to know which shortcodes you can use in your posts/pages.</li>
<li>if you switch plugins or remove a plugin, to know in which posts/pages you need to remove/replace old shortcodes</li>
</ul>
</li>
<li>
<p>If you are a <strong><em>web designer / web master</em></strong>:</p>
<ul>
<li>if you switch plugins or remove a plugin, to know in which posts/pages you need to remove/replace old shortcodes.</li>
<li>to know which shortcodes you can use in theme files.</li>
<li>to avoid name conflicts for website specific shortcodes.</li>
</ul>
</li>
<li>
<p>If you are a <strong><em>developer</em></strong>:</p>
<ul>
<li>to avoid name conflicts with shortcodes registered by other plugins/themes.</li>
<li>to check whether your shortcode registers properly and whether the conditionals are applied correctly.</li>
</ul>
</li>
</ul>
<h4>Important</h4>
<p>This plugin requires the <a href="https://wordpress.org/plugins/debug-bar/" rel="ugc">Debug Bar</a> plugin to be installed and activated.</p>
<h4>Credits</h4>
<ul>
<li>The additional information functionality is inspired by <a href="https://wordpress.org/plugins/lrh-shortcode-list/" rel="ugc">LRH-Shortcode list</a> and <a href="https://wordpress.org/plugins/shortcode-reference/" rel="ugc">Shortcode reference</a>.</li>
<li>The finding of shortcode uses throughout the site is inspired by <a href="https://wordpress.org/plugins/tr-all-shortcodes/" rel="ugc">TR All Shortcodes</a></li>
</ul>
<p>If you like this plugin, please <a href="https://wordpress.org/support/view/plugin-reviews/debug-bar-shortcodes" rel="ugc">rate and/or review</a> it. If you have ideas on how to make the plugin even better or if you have found any bugs, please report these in the <a href="https://wordpress.org/support/plugin/debug-bar-shortcodes" rel="ugc">Support Forum</a> or in the <a href="https://github.com/jrfnl/Debug-Bar-Shortcodes/issues" rel="nofollow ugc">GitHub repository</a>.</p>


Debug Bar Shortcodes

Works great

Debug Bar Shortcodes adds a new panel to the Debug Bar that displays the registered shortcodes for the current request.

Script Report vs Debug Bar Shortcodes