That’s on the potential to-do list, in part because I’m a little iffy about the speed benefits vs latency trade-off when you do that, and I’m studying it more before I mess with it.
I’d also like to request this feature.
There’s some evidence that parallel HTTP requests to external domains can speed things up [1,2] particularly if browsers are already DNS prefetching a CDN domain (as many modern browsers do automatically [3], I believe?)
[1] http://programmers.stackexchange.com/q/88478/
[2] http://css-tricks.com/poll-results-cdn-or-local/
[3] https://developer.mozilla.org/en-US/docs/Web/HTTP/Controlling_DNS_prefetching
And, of course, THANK YOU for this plugin! It works just great.
Oh I agree, but I don’t know how dreamspeed gets ‘flagged’ as a CDN. Especially since you can customize domains.
I don’t know how dreamspeed gets ‘flagged’ as a CDN
Can you clarify? I’m not sure I understand. I mean, CDN is in the name, right?
http://www.dreamhost.com/cloud/cdn/
I mean by Google and Yahoo and all them.
Like if I use cdn.mydomain.com, yahoo’s YSlow will STILL tell me “Hey, this isn’t a CDN!”
OK I see, thanks for explaining.
Looks like you can add a custom CDN hostname to YSlow to enable accurate reporting.
http://yslow.org/faq/#faq_cdn
Google PageSpeed has some extensive docs on authorizing hostnames. This may help?
https://developers.google.com/speed/pagespeed/module/domains
Hi
Mika, have you been decided about inclusion of CSS/JS?
I am planning on it for next stage 🙂 Just taking my time, since it’s not as easy as images. Theme JS/CSS storage can be anywhere, so I have to do it carefully.
Thanks.
Just one suggestion: exclusion option, i.e. to exclude some files from cdn serving, e.g. font-awesome.min.css
I know for FontAwesome, it can break if served from some CDN. I’m not sure would that be case with dreamspeed, but anyway it would be good to have this option.
And you have isolated one of the many hurdles I face!
