Marc Tönsing

<p>Removes jQuery from your frontend theme if no administrator is logged-in. jQuery will continue to work in you backend and when the admin toolbar is visible. Plugins which depend on jQuery will not be loaded either.</p>
<p>This plugin does nothing more but this:</p>
<pre><code>function init_without_jquery() {
    if (!is_admin() AND !is_admin_bar_showing()) {
        wp_deregister_script('jquery');
        wp_register_script('jquery', false);
    }
}

add_action('init', 'init_without_jquery');
</code></pre>


Remove jQuery from Theme

Removes jQuery from your frontend theme if no administrator is logged-in. jQuery will still be loaded and continue to work in you backend and when the …

Jason Penney

<p>A number of the javascript libraries distributed with WordPress are also<br />
hosted on Google’s <a href="http://code.google.com/apis/ajaxlibs/" rel="nofollow ugc">AJAX Libraries API</a>.<br />
This plugin allows your WordPress site to use the content distribution<br />
network side of Google’s AJAX Library API, rather than serving these files from your WordPress install directly.</p>
<p>This provides numerous potential performance benefits:</p>
<ul>
<li>increases the chance that a user already has these files cached</li>
<li>takes load off your server</li>
<li>uses compressed versions of the libraries (where available)</li>
<li>Google’s servers are set up to negotiate HTTP compression with the requesting browser</li>
</ul>
<p>For a more detailed look see Dave Ward’s <a href="https://web-beta.archive.org/web/20101216143500/encosia.com/2008/12/10/3-reasons-why-you-should-let-google-host-jquery-for-you/" rel="nofollow ugc">3 reasons why you should let<br />
Google host jQuery for<br />
you</a>.</p>
<h4>Supported Libraries and Components</h4>
<ul>
<li><a href="http://dojotoolkit.org/" rel="nofollow ugc">Dojo</a></li>
<li><a href="http://jquery.com/" rel="nofollow ugc">jQuery</a></li>
<li><a href="http://ui.jquery.com/" rel="nofollow ugc">jQuery UI</a></li>
<li><a href="http://mootools.net/" rel="nofollow ugc">MooTools</a></li>
<li><a href="http://www.prototypejs.org/" rel="nofollow ugc">Prototype</a></li>
<li><a href="http://script.aculo.us/" rel="nofollow ugc">script.aculo.us</a></li>
<li><a href="http://code.google.com/p/swfobject/" rel="nofollow ugc">swfobject</a></li>
</ul>
<h4>Links</h4>
<ul>
<li><a href="http://jasonpenney.net/wordpress-plugins/use-google-libraries/" rel="nofollow ugc">Use Google Libraries Home</a></li>
<li><a href="http://github.com/jpenney/use-google-libraries/issues" rel="nofollow ugc">Issue Tracker</a></li>
<li><a href="http://github.com/jpenney/use-google-libraries" rel="nofollow ugc">GitHub Repository</a></li>
<li><a href="https://wordpress.org/support/plugin/use-google-libraries" rel="ugc">Support Forum</a></li>
</ul>
<h3>Incompatible Plugins</h3>
<h4>Better WordPress Minify</h4>
<p>Better WordPress Minify version 1.2.2 does not yet support<br />
protocol-relative URLs, but <a href="https://wordpress.org/support/topic/conflict-with-use-google-libraries-152" rel="ugc">the next release is supposed to correct<br />
this</a>.</p>
<h4>Gravity Forms</h4>
<p>I’ve had reports of Gravity Forms breaking UGL, but I don’t have<br />
access to Gravity Forms, so I’m not sure what’s going on.  If you need<br />
Gravity Forms you might need to disable UGL, or it might be fine, I’m<br />
not really sure.</p>
<h4>WP-Minify</h4>
<p>WP-Minify doesn’t yet support protocol-relative URLs.  Add<br />
‘//ajax.googleapis.com/’ as a JS and CSS exclusion.</p>
<h3>Incompatible Themes</h3>
<h4>K2</h4>
<p>I’ve had scattered reports that UGL is stepping out of the way when<br />
using K2.</p>
<h3>A Request</h3>
<p>If you’re going to flag the plugin as “broken” in the WordPress Plugin<br />
Directory, please try and <a href="https://wordpress.org/tags/use-google-libraries?forum_id=10" rel="ugc">let me know <em>what</em> is<br />
broken</a>.<br />
I’m not a mind reader.</p>
<h3>Technical Details</h3>
<p><strong>Use Google Libraries</strong> uses the following hooks (each with a priority of 1000).</p>
<h4>wp_default_scripts</h4>
<p><strong>Use Google Libraries</strong> compares it’s list of supported scripts to those<br />
registered, and replaces the standard registrations <code>src</code> with ones that<br />
point to Google’s servers.  Other attributes (like dependencies) are left<br />
intact.</p>
<h4>script_loader_src</h4>
<p><strong>Use Google Libraries</strong> removes the <code>ver=x.y.z</code> query string from the URL<br />
used to load the requested library <em>if</em> it is going to load the library from<br />
    ajax.googleapis.com.  Otherwise the URL is left unaltered.  This both<br />
improves the chances of the given URL already being cached, and prevents<br />
<strong>script.aculo.us</strong> from including scripts multiple times.</p>
<p>If jQuery is enqued <strong>Use Google Libraries</strong> will inject a bit of<br />
javascript before the next enqueued script enabling jQuery’s <a href="http://docs.jquery.com/Core/jQuery.noConflict" rel="nofollow ugc">noConflict mode</a> as it would<br />
with the standard WordPress version.</p>
<h3>References</h3>
<p>Parts of this plugin (specificly, the dropping of the micro number,<br />
which has since been removed for better caching performance) were<br />
inspired by John Blackbourn’s<br />
<strong><a href="http://lud.icro.us/wordpress-plugin-google-ajax-libraries/" rel="nofollow ugc">Google AJAX Libraries</a></strong>,<br />
which has very similar goals to this plugin.</p>
<h3>Future Plans</h3>
<ul>
<li>add ability to disable protocol relative URLs</li>
<li>add ability to disable on frontend and/or admin</li>
</ul>


Use Google Libraries

you will be received 5/5 stars, once it's updated and functioning as used to be. thanks...

edit: thanks for updating :) 

please update it

Allows your site to use common javascript libraries from Google's AJAX Libraries CDN, rather than from WordPress's own copies.

Remove jQuery from Theme vs Use Google Libraries