Hosting images on multiple domains

[eventurerob]

I'm taking the following from http://developer.yahoo.com/performance/rules.html

"Splitting components allows you to maximize parallel downloads. Make sure you're using not more than 2-4 domains because of the DNS lookup penalty. For example, you can host your HTML and dynamic content on www.example.org and split static components between static1.example.org and static2.example.org"

What I want to do is load page images (it's an eCommerce site) from multiple sub domains to reduce load times.

I'm assuming that this is perfectly OK to do - I cannot think of any reason that this wouldn't be a good tactic to go with.

Does anyone know of (or can think of) a reason why taking this approach could be in any way detrimental.

Cheers mozzers.

[eventurerob]

Thanks Guys

I've got some developers to help me with the tech side so they'll be using the servers etc that they're used too.

Just wanted to check I wasn't dropping a massively obvious clanger on the SEO side.

Cheers for your help.

Alex.

[blu42media]

Are you trying to rank your images in Google image search?  If so, make sure the full path for each component stays the same.

As for general SEO, you're right on track.  The performance boost from the parallel loading will be one more step to help you rank!

[goodlegaladvice]

its really cheap to use a cdn like amazon rather than do it yourself

[Highland]

I like how Amazon's CloudFront does this. It uses a CNAME to route it to the closest download site. I would do the same. Use something like Round Robin to split your downloads up. Or use a cloud based host to do it for you.

As far as SEO goes, it shouldn't matter. Google will do its own DNS and caching.