Rewrites links to static files to your own CDN network.

wmark

Replaces the blog URL by another for all files under <code>wp-content</code> and <code>wp-includes</code>. 
That way static content can be handled by a CDN by origin pull. (The origin is your blog address.)
You could upload your static files to S3, CloudFront or just any site, too. 
For S3/Cloudfront, see <a href="http://mark.ossdl.de/2009/09/how-to-copy-your-wordpress-files-to-cloudfront-efficiently/" title="how to copy your WordPress files to CloudFront efficiently" rel="nofollow ugc">this script</a> 
to help you with uploading/synchronizing your blog files.
This <code>lite</code> version of the plugin works like the regular version but is not supported. 
You can get the regular version at <a href="https://github.com/wmark/CDN-Linker" title="CDN Linker at Github" rel="nofollow ugc">Github</a>, which:
<ul>
<li>Is free of charge, open source and without any ads.</li>
<li>Supported. Here is <a href="https://github.com/wmark/CDN-Linker/issues" title="bug tracker" rel="nofollow ugc">the bug tracker</a> if you encounter any issues.</li>
<li>Has more and advanced features.</li>
<li>Is updated more frequently. See <a href="https://github.com/wmark/CDN-Linker/downloads" title="Downloads page" rel="nofollow ugc">Downloads</a>.</li>
<li>Quality assurance.</li>
</ul>

CDN Linker lite

Recommended to use with W3TC with good origin pull CDN. W3TC infamously gives errors with the CDN part. Use the GitHub version by Author.



Good to use with W3TC

I've established blog from a year. When I tried this plugin, it didn't automatically converted my link to CDN path.
I think KeyCDN enabler is better..



Alternatives to CDN Linker lite

Top alternatives