Google Seeks to Pacify Consumers with Faster Mobile Pages
1–10 of 50 posts
Re: Google Seeks to Pacify Consumers with Faster Mobile Pages
#2To use AMP you need to load JavaScript from the AMP CDN, which is operated by Google. From " rel="nofollow">https://github.com/ampproject/amphtml/blob/master/spec/amp-h...:
> The AMP runtime is loaded via the mandatory " rel="nofollow">https://cdn.ampproject.org/v0.js"> tag in the AMP document .
So you are handing over the security of your site and your user's privacy to Google.
Re: Google Seeks to Pacify Consumers with Faster Mobile Pages
#3To use AMP you need to load JavaScript from the AMP CDN, which is operated by Google. From " rel="nofollow">https://github.com/ampproject/amphtml/blob/master/spec/amp-h... : > The AMP runtime is loaded via the mandatory " rel="nofollow">https://cdn.ampproject.org/v0.js"> tag in the AMP document . So you are handing over the security of your site and your user's privacy to Google.
you can also host it yourself. See github downloads.
Re: Google Seeks to Pacify Consumers with Faster Mobile Pages
#4Make up your mind Bloomberg:
Google said [...] it will put websites built with its Accelerated Mobile Pages [...] in the Top Stories section of a search results page
VERSUS
AMP isn’t “a signal we use in ranking” pages, Besbris said. He declined to comment about whether AMP pages would rank higher
Re: Google Seeks to Pacify Consumers with Faster Mobile Pages
#5Ha, for a second I thought they were going to do something about the ad saturation.
uBlock and NoScript on Firefox for Android pacify this consumer just fine.
Re: Google Seeks to Pacify Consumers with Faster Mobile Pages
#6You know what already makes pages load lightning fast?
Ad blocking.
Re: Google Seeks to Pacify Consumers with Faster Mobile Pages
#7I've already gone to great lengths to optimize my mobile site. I am fully confident that AMP cannot possibly make my site any faster. Every page on my site loads via a single HTTP request that transfers 10k of gzipped JS and HTML all at once. Loading an additional script with an extra request for another JS file is completely against my mobile design principles.
Should people like me start using AMP anyway to stay relevant in Google search rankings?
Re: Google Seeks to Pacify Consumers with Faster Mobile Pages
#8Not kicking me to a full screen ad for their gmail app every time I log in to gmail would be a nice start.
Re: Google Seeks to Pacify Consumers with Faster Mobile Pages
#9You know what already makes pages load lightning fast? Ad blocking.
One of AMP's goals seems to be ensuring that websites aren't noticeably slower just because they have ads on them.
Re: Google Seeks to Pacify Consumers with Faster Mobile Pages
#10Content alone loads faster than loading content plus ads.
Making one DNS request is faster than making several, including ones for domains related to advertising.
There are the speed gains that Google can offer and then there are ones that are under the user's control, which Google will never offer, unless they change their business model.
Not requesting ads makes my user experience faster.
Experiment: Disable Javascript for Google searches and what happens? Do the ads still load?