ChrisBAshton

<p>The inline cache methodology emphasises fast first page loads. It acts on the basis that opening HTTP connections is slow, and that it is therefore faster for the resources to be inlined, but that we also want to cache those resources so they don’t have to be re-downloaded.</p>
<p>That’s what WP Inline Cacher does. It automatically renders your stylesheets inline on first page load, and caches them in the background. On subsequent page loads, the resources are no longer inlined – so your page weight is smaller – but are automatically retrieved from cache.</p>
<p>See https://github.com/ChrisBAshton/inline-cache for more details.</p>
<h3>Contact</h3>
<p>If you spot any issues, or want to know how to contribute, please visit https://github.com/ChrisBAshton/wp-inline-Cacher.</p>
<p>Please note that I have open-sourced this plugin to give back to the community, and do not have much spare time to answer support queries, but I’ll help where I can.</p>


WP Inline Cacher

Speed up your site for first-time visitors by inlining your resources.

Palasthotel

greatestview

<p><strong>CAUTION</strong>: This plugin is now deprecated! The successor plugin is <a href="https://wordpress.org/plugins/embed-javascript-file-content/" rel="ugc">Embed JavaScript File Content</a>. The new plugin is rebuild from scratch and more rock solid: It respects order and position of scripts and extra scripts added via <code>wp_add_inline_script</code> or <code>wp_localize_script</code> don’t get lost. Give it a try!</p>
<p>In some cases you cannot wait for a JavaScript file to load, even if it is placed early in the <code><head></code> section of your template. You can benefit from better performance, if you place the JavaScript code directly inside a <code><script></code> tag into the header. This is where this plugin comes in: It provides a filter <code>inline_javascript_in_head_handles</code>, which takes JavaScript handles, dequeues those scripts and echos their code content inline into the head section instead of linking them via a script tag.</p>
<p>Please beware that placing lots of JavaScript code inline in the <code><head></code> section can be critical! First you lose caching benefits and second the document size can increase easily. A general rule of thumb is that you should only consider JavaScript files for inline placement, which are critical and which have a file size lower than ~500 Bytes.</p>
<h4>Example</h4>
<pre><code>add_action( 'wp_enqueue_scripts', 'my_scripts' );
function my_scripts() {
    // Some critical script is enqueued
    wp_enqueue_script( 'js-detection', get_template_directory_uri() . '/js/js-detection.js' );
}

/**
 * Define JavaScript handles to be echoed inline in the html head section.
 */
add_filter( 'inline_javascript_in_head_handles', 'my_inline_javascript_in_head_handles', -20 );
function my_inline_javascript_in_head_handles( $handles ) {
    $scripts = [ 'js-detection' ];

    return array_merge( $handles, $scripts );
}
</code></pre>


Inline JavaScript in Head

Boosts performance of critical short JavaScripts by placing their content directly into the HTML head.

WP Inline Cacher vs Inline JavaScript in Head