• About Us
  • Blog
  • Basket
  • Account
  • Sign In
  •  

Blog

Published on Monday, June 17, 2013

Debunking Google’s Responsive Web Design "Preference"

Last week Google announced their plans to push websites into offering great mobile web experiences. With this announcement came some controversy over Google’s preferred method of mobilisation. According to the Responsive Web Design (RWD) community, not an actual endorsement for the design technique itself.

A single URL does make it easier for Google’s link algorithms to work, however no penalty will be given for not using this method. Shared HTML within RWD also means that the processing required by Google’s crawler is minimised, increasing its efficiency. This means less of a technical overhead for Google, so selfishly would prefer this method. Google themselves don’t employ RWD in their mobile website, but instead favour a separate, highly optimised mobile experience.

In reality Google recommend the configuration which is best for your users, which is why Apple, Facebook, Twitter and LinkedIn have chose not to adopt RWD in their mobile websites. The topic of which approach is best is still heavily debated in the web development community; however we are starting to see a large emphasis on mobile performance instead of just aesthetic design.

In short; relevant content, a great user experience and fast loading times are now becoming primary concerns, rather than just how good a website looks on a mobile device .

Comments (0)

Author: Joe Davine

Categories: Opinion

Tags: Google , SEO , RWD

Joe Davine
Joe Davine>

Joe Davine

Marketing Executive for 51Degrees.mobi

Other posts by Joe Davine
Contact author

Name:
Email:
Subject:
Message:
x

Tags

.NET 4G 51Degrees 5G Acer Adform Adtech Advertising Afilias Alcatel Amazon AMP Analysis Analytics Android Apache API Apple Asian Market ASP.NET Asus Blackberry Browser C C# Centro Chrome Cloud CMS CPU CSS3 Data Data Blog Data File Daydream Design Detection Developers Device Device Data Device Detection Device Intelligence Device Models Device property DeviceAtlas Disney dmexco DotNetNuke Download ebay Ericsson Event Facebook Firefox Foundation Framework Galaxy git repositories Google Google Analytics Google Daydream GPU GSMA Guess HAProxy Hash Trie HTC HTML5 HTTP HTTP Headers Huawei Infinix Ingeniux Internet usage iOS iOS 13 ipad iPadOS iPhone iPhone 11 Java Javascript Kentico LG Liferay LTE m.dot Memory Memory leak Meta Data Microsoft Mobile Mobile Analysis Mobile Analytics Mobile Devices Mobile Marketing Mixer Motorola Mozilla MWC MWC 2017 MWC16 Native Apps NET New Release News Nexus NFC NGINX Nokia OnePlus 5 Opera Operating System Oppo Optimisation OS Patent Performance PHP Press Release Price Band programmatic Publishers Python Redirection Research Responsive Images Responsive web design RESS Review RTB RWD Safari Samsung Scala ScientiaMobile SEO Server Server-side optimisation Seznam.cz Sitecore Smart TV Smartphone Smartwatches Sony Swedish Beers Tablet Tencent Testing Tips Tutorial Umbraco Update User Agent User-Agent Valgrind Varnish Varnish Cache Video Vodafone VoLTE Web Web Apps Web content management Webtrekk White Paper Widgets WiFi Windows WURFL Xiaomi Xperia ZTE