What's Your Mobile Page Speed? It's Now Becoming an Official Google Ranking Factor
- Thread starter Ryan Everson
- Start date
- Feb 11, 2015
- 2,492
- 765
- First Name
- Alex
- Feb 11, 2015
- 2,492
- 765
- First Name
- Alex
@Jeff Kershner @reverson you guys bring up an interesting point. Have any of the web platform providers thought about implementing the ability to use AMP within their inventory systems? Obviously, these have been used for blogs (articles) more so, but why not? AMP shows an e-commerce ability (in our world VDP lead conversions).https://www.ampproject.org/case-studies/e-commerce/
I can't find any instance of automotive / car inventory + AMP mentioned via a query.
Might find something for other forms of inventory here: https://cdn.ampproject.org/experiments.html / https://www.ampproject.org/learn/who-uses-amp/publishers/.
Last edited:
Our team here at Dealer Venom is currently planning on developing AMP VDPs. Project team is targeted to finish our first round of AMP capabilities mid-Q2. We feel AMPs will have a great impact on the mobile e-commerce landscape in the near future, and with Google changing their SEO algorithms like underwear, having the ability to implement this could prove to be useful..
Also, regarding the page load speeds - I also agree with what Jason mentioned - don't chase 100%!
(Not sure if this post is in violation of rules? I dont want it to come off as promo!)
Last edited:
We're working on them as well.
I'm really excited about it, but it's a whole different beast for sure.
For the most part, dealers are going to have to choose between AMP or having control over their mobile site in the CMS.
- Apr 29, 2011
- 505
- 262
- Awards
- 7
- First Name
- Chris
I felt the same, but then I saw the speed.
The way these pages are built, they’re incredibly quick to use. It’s a really cool concept that has a lot of potential and a lot of potential drawbacks.
- Apr 29, 2011
- 505
- 262
- Awards
- 7
- First Name
- Chris
Major potential drawbacks. They're forcing a technology on an industry that's already rejected it, and have the balls to say it's "user-first". No, it's Google first. So now the solution is to issue vague threats in order to increase adoption rates. I can't wait for the anti-trust suit to be filed.
If you want to make your site fast, build a light weight front-end and use caching and prefetching. Check out https://changelog.com it's built with Turbolinks (uses PJAX and caching) and Phoenix (renders Rails views a lot faster). AMP forces people to either re-platform or built and maintain a secondary application.
Worse, Google is dictating to everyone else what makes a great web browsing experience and using their monopoly on search to force that on developers, which is evident in this thread.
Last edited:
I don't disagree with any of your points, except that AMP really is a good user experience.
It's fast, consistent, primarily ad-free, etc.
Changelog.com is great, but master Google says it's too slow
It's fast, consistent, primarily ad-free, etc.
Changelog.com is great, but master Google says it's too slow
Has anyone else heard that Google Pagespeed Insights doesn't actually measure the phsyical speed of your website, but more the technical speed ? Not really sure if this is true, or makes sense. For example, GTmetrix goes into more detail about when the site is fully loaded.
