Should I include jQuery from Google JSAPI or a CDN?

Including jQuery: Google JSAPI vs. CDN

One common practice is to include jQuery from Google's JSAPI (JavaScript Application Programming Interface) using the following syntax:

<code class="html"><script src="https://www.google.com/jsapi"></script>
<script>
google.load('jquery', '1.3.1');
</script></code>

However, this method can sometimes result in slow load times due to the time it takes to establish an SSL connection with Google.

Another option is to include jQuery directly from a Content Delivery Network (CDN), such as Google's own CDN:

<code class="html"><script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.3/jquery.min.js"></script></code>

By default, jQuery will be served over HTTP, but you can also remove the "http:" portion of the URL to ensure the script can be loaded over both HTTP and HTTPS:

<code class="html"><script src="//ajax.googleapis.com/ajax/libs/jquery/1.4.3/jquery.min.js"></script></code>

This method is recommended because Google's CDN is widely distributed and has proven to provide fast and reliable delivery of jQuery. Additionally, if users have already visited other sites that use Google's CDN, the jQuery script may already be cached locally, reducing load times even further.

If you prefer to serve jQuery from your own server, you can download the library from jQuery's website and host it locally. However, this method may require additional bandwidth usage on your server and doesn't provide the same caching benefits as using a CDN.

The above is the detailed content of Should I include jQuery from Google JSAPI or a CDN?. For more information, please follow other related articles on the PHP Chinese website!