DirigoDev - 11:21 pm on Mar 22, 2013 (gmt 0)
Iíve not seen any real movement in SEO on pages that were not further optimized. That said, most everything was built better than before. We saw 5% more traffic in the first 60 days. Rankings did not shift strictly due to RWD. All of our pages got 301 redirected from an old architecture to new with a little more emphasis on the file naming and anchor text. The RWD allowed us to shut down our m. site and run from a single code-base (way better for us). We tuned our calls to action and are getting more leads. The redesign included parallelization, minification, open graph tags, css versioning, a smaller image set for smaller devices, smaller videos at different bitrates (adaptive by bandwidth and device), a 50% increase in speed... We could have done all of this on a non-RWD site but wanted to serve mobile users better. We're totally onboard with Mobile First (designing for touch). The RWD retool was a good excuse to break it all down and redeploy best practices. Weíre seeing better mobile use and users like the solution. Conversion is up by 8%.
Five out of 16 of our competitors moved to RWD between 11/2012 and 3/2013. I expect another five to move by December.
We feel good to be with the pack that is leading. I think that consumers can tell the difference between old and new. Jpeg-heavy designs are out; CSS3 and Font-Familyís are in. Less fluff, more value. Swipe it, tap it, and lastly, click it. Tablets and phones use swiping and other touch-centric navigation elements, and it is hip to use new intuitive app-centric features on the web. In the end, the folks that donít move will be marginalized. Our mobile usage continues to increase.
We even deployed some HTML5ís onpop state stuff that allows a change in the browser url without reloading the page. Simple, but extremely powerful. This saves precious http requests and initial document ready event handling. We're seeing performance gains of 40% with this technique alone. If coded properly, the onpop state feature will allow developers to ajax in content while still having search engine friendly page URLs that are shareable and wonít break the web browsing paradigm.
I'm eager to build something for Glass. Will be be discussing the GlassFirst approach next year?