Forum Moderators: Robert Charlton & goodroi
Would that have any downsides or advantages?
One I can think is not having the weight of images in your site, thus, faster loading.
Less bandwidth waste.
What about seo issues?
I'm no expert on server configuration but I bet you could probably route all requests to your images folder to a different server, behind the scenes. Google doesn't know what happens server-side.
[edited by: Robert_Charlton at 4:47 pm (utc) on July 3, 2009]
[edit reason] removed specifcs & delinked example domain [/edit]
Would that have any downsides or advantages?
I have a lot of images and it is important for me to have them ranked highly since I get tens of thousands of image search referrals every month.
Whilst it may seem to make sense to have one central repository for images (I used to do that however changed it after experimentation) the downside is that Google generally ranks images higher if the images are served from the same domain as the site since the image is, I reckon, perceived to be "owned" by that site.
The question you have to answer is how important are image searches for your site?
If it is not important then no problem, however If they are important/critical it would be best practice to put them on that domain and to ensure all tags and attributes closely identify each image accurately even down to naming the image exactly and not an hexadecimal number or strange shortened format.
BTW having a subdomain on a shared hosting account doesn't place the images exactly in same place (same server)? I find no reason to do that then.