Welcome to the Q&A Forum

Thanks for your response and share your advice.

Or... just don't bother! Make your original site mobile-friendly and dump the idea for a whole separate site. There really is no need, .mobi or otherwise. Plus, then you'll have to sites you have to get links for, when you could combine all those links into one site and get more bang for your buck.

Although I wasn't able to find a concrete answer for you, It seems the general consensus is that moving ViewState to the bottom of the page can ensure a larger portion of your relevant content gets indexed, as well as improve the user experience by slightly improving page load time. Here we're some of the more helpful discussions I found : Moving ViewState to Improve ASP.NET SEO Moving ViewState for Better SEO ASP.NET HttpModule for Moving ViewState to Bottom I have never heard of any of these guys and cannot vouch for their knowledge.  Sorry I could not be of more help, best of luck!

Thanks Adam for all your comments. I agree Google encourages the use of video and my concern is the load time of moving from 2 seconds to 11 seconds. This will be a good test!

What we're trying to do specifically is use a flash video as a product image, so the size increase will be significant. We're talking somewhere around 1.5 - 2mb on a page that is about 400kb before the video. So the increase is significant. This is why the concern, and why we were thinking perhaps having the flash video inside an iframe might overcome the speed issues. Google often talks about doing the best user experience and the SEO will follow, but the two seem conflicting, as we're trying to provide a better experience with the video, but the increase in page size, and therefore speed, will be significant. The rest of the page will load, including a fallback static image, so we're really trying to understand how to mitigate the page load speed impact of the video.