When you look at the <style|script>
tags in your head, you will notice the id
attribute there. Example:
id='bootstrap-css'
This – in most cases – was added by a function hooked to wp_enqueue_scripts
, wp_enqueue_styles
or wp_register_scripts
or wp_register_styles
hook. In the worst case it was hooked to either the wp_head
or the wp_print_scripts
hook.
In the process of backtracing those calls that add the <script|style>
tags, you should be able to see what is attached by using something like the following from within a small plugin or your functions.php
in a theme or child theme:
// See if those scripts/styles were added using the Dependency API
// Search the output for the `id` you can see rendered in the DOM
printf(
'<pre>%s</pre>',
var_export( $GLOBALS['wp_scripts']->registered, TRUE )
);
If you can find the script/style in above output, then you know that the asset was properly registered (and therefore is available for optimization or other handling with plugins using the WordPress API).
In case that was true, you can then search the assets up:
foreach( [
'wp_enqueue_scripts',
'wp_print_scripts',
'wp_head',
] as $action )
printf(
'<h1><code>%1$s</code></h1><pre>%1$s</pre>',
var_export( $GLOBALS['wp_filters'][ $action ], TRUE )
);
You will get printed three “blocks” of information. Each will contain an array of callbacks that are attached to the specific hook in the array. You can then search those up using a cross file search over your themes and plugins to find the origin of your assets. Then unregister the actions you want to get rid of.