The main function of a CDN for a developer is not to be concerned about network traffic and to be able to guarantee visitors always availability of files. For the user is to get from a second domain (parallel upload) the files, from a place that would probably be closer physically decreasing the latency (connection time, DNS resolution and download).
If your visitors are geographically close to you, or are unique to a locality (country, country or continent region) there is NOT much need for a CDN, because for users it won’t make so much difference. In this case, I recommend that you create a subdomain or even another domain (ai is your strategy) to serve these files. So you can serve in parallel and from a "cookieless domain".
Ideally, you can get your pages to make as few requests as possible (both for the same domain and several: CDN, subdomains, etc.), so you can increase the page load speed.
Try merging into just a . css or . js (you can develop in separate files, but when it comes to publishing together, or use tools that do this) all the code that will be used by a certain area of your site. Compact (remove unnecessary spaces, indentations, comments, use gzip compression) and cache these files (set the files to be cached by the user for as long as possible, and if you update the data in the files, then change the URL that the user searches for, forcing a new download, updated).
If you are going to provide customization and are using scripting libraries, do not provide a CDN library and its customization to part of your server (or your own CDN). Put it all together in one and make it available to your users. Initially you will increase your server traffic a little, but you will decrease user requests and have control over the caching of these files altogether.
For custom libraries, you can use Amazon AWS. It’s almost free. http://aws.amazon.com/pt/
– user622