-
-
Notifications
You must be signed in to change notification settings - Fork 580
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
avoid mobilegeddon #816
Comments
I guess the website design could become more responsive via CSS3 media tags, so where content is in 2 or 3 column style they could simply become single column, also little buttons could become bigger and some graphics could be avoided altogether. An additional stylesheet could be loaded if the website figures out the client is mobile based, will look into it and figure out all the possibilities and implementation details. |
Some pretty good mobile optimization tips http://www.sitepoint.com/10-ways-make-website-mobile-friendly |
This website mobile approach design seems to be the standard (most efficient), need to study / implement https://www.whatsapp.com https://www.google.com/webmasters/tools/mobile-friendly/?url=https%3A%2F%2Fwww.whatsapp.com%2F |
This might provide some useful tips https://support.google.com/webmasters/answer/35769 |
Issue #818 is related to this. Recently optimized the media images, trimming about a total of 4 megabytes, providing smaller images for mobiles could trim even more. The downscaled versions could eventually be done automatically using grunt, gulp or bower. |
Google search ranking will drop for websites that are not mobile friendly.
http://blog.webflow.com/avoid-mobilegeddon-with-responsive-design
Despite my efforts and good performance of the website on such devices, Google is still not happy.
--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/11912243-avoid-mobilegeddon?utm_campaign=plugin&utm_content=tracker%2F260151&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F260151&utm_medium=issues&utm_source=github).Will need to tweak the homepage and some of the elements some more...
The text was updated successfully, but these errors were encountered: