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.

Per Søderlind

Juliette Reinders Folmer

<p>We all know that when we’re add a script or style to WordPress, we should use <code>wp_enqueue_script( $handle, $src, $deps, $ver, $in_footer )</code> and <code>wp_enqueue_style( $handle, $src, $deps, $ver, $media )</code> as in:</p>
<pre><code>function themeslug_enqueue_style() {
    wp_enqueue_style( 'core', 'style.css', array('twentytwelve-style') );
}

function themeslug_enqueue_script() {
    wp_enqueue_script( 'my-js', 'filename.js', array('jquery') );
}

add_action( 'wp_enqueue_scripts', 'themeslug_enqueue_style' );
add_action( 'wp_enqueue_scripts', 'themeslug_enqueue_script' )
</code></pre>
<p>$deps (dependencies), the handle name and an optional parameter, lets you control when/where your script or style should be added. If $deps is <code>array('jquery')</code>, your script will be loaded after jquery is loaded.</p>
<p>The problem is, which one exists and in which order are they loaded ?</p>
<p>Debug Bar List Script & Style Dependencies, an add-on to <a href="https://wordpress.org/plugins/debug-bar/" rel="ugc">Debug Bar</a>, will list the dependencies.</p>
<h4>Use</h4>
<p>To view the loaded scripts and styles</p>
<ul>
<li>Front-end: Go to the front-end, and on the admin bar choose Debug and view Script & Style Dependencies</li>
<li>Back-end: Go to the back-end, on the admin bar choose Debug and view Script & Style Dependencies</li>
</ul>
<p>Note, the front-end and back-end loads different scripts and styles. Also, different pages on the front-end and back-end can load different scripts and styles.</p>


Debug Bar List Script & Style Dependencies

Style very useful (even if it has not been updated since two years) ! Thanks !



useful !

Debug Bar List Script & Style Dependencies is an add-on to WordPress Debug Bar

Script Report vs Debug Bar List Script & Style Dependencies