Cloaking quesation

[tomchu]

On this page  - /design-templates/invitation-cards-come-celebrate-708.aspx  the image file location in the source code is src="/design-templates/come-celebrate-708.jpg". But in a browser > right click > save the image, the image file name/location is different "http://www.psprint.com/psp/r//708/708.jpg-001.jpg?1308862042145"

Does it consider cloaking and does this impact to SEO in any ways?

Thanks

Tom

---

[RyanKent]

Cloaking is defined as providing different content to users then to search engine crawlers. That is not what is happening here. Users and search engines see the same picture.

The source of the image is irrelevant. Many sites use content delivery networks to deliver images. If you are viewing the page from California, then perhaps a server in San Jose, CA will deliver your image. Meanwhile if you view that same page in Texas, then perhaps a Dallas, TX server will deliver the same content. The delivered files COULD have different names or paths, but the actual content delivered should be the same.

No, this is not cloaking and does not impact SEO directly.

As oznappies points out, there may be other issues with the page which cause it to load very slowly and not perform well, and those issues can impact SEO.

[oznappies]

The image name is different as it is late loaded by a javascript async call to fetch the image. Images are not considered as cloaking and async loads are a common practice. Since the load only seems to load an image and not text content Google would be unlikely to penalise you. But, all that javascript (19 modules) and the 36sec pageload time could cause you a performance penelty as Google introduces this new metric (they are trialing in their beta).

I would suggest you run the site through gtmetrix.com to sort out the performance issues.