News for hackers. Stuff that matters.
Re:Google Seeks to Pacify Consumers with Faster Mobile Pages by stevenh on Wednesday February 24, 2016 @12:06PM (#11168261)
I'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 by devsquid on Wednesday February 24, 2016 @01:52PM (#11169137)
:) AMP isn't for you then. Honestly your site is probably better than AMP could ever be just inherent in the fact your site doesn't need a library enforcing rules, but thats not the point of AMP. AMP is for forcing news sites to do similar things to what I assume you have already done.

Imagine some web developer at Huge Mega News Corp (HMNC), he comes to his manager about the fact they have 5 analytics suites running and when the ads load they bounce the screen around. His manager reviews it and determines its not important because 1. People are still coming to the site 2. It isn't stopping people from coming to the site. Now the dev at HMNC can come to his manager and say hey what you want doesn't conform to AMP, we can't do that.

I have heard multiple times, AMP will not increase your ranking. Load times don't inherently increase your ranking over other content. But if your site has similar merits to another site, then load times among other things will effect who is ranked higher.

Re:Google Seeks to Pacify Consumers with Faster Mobile Pages by sliverstorm on Wednesday February 24, 2016 @12:33PM (#11168500)
He declined to comment about whether AMP pages would rank higher, though he said some of the signals Google uses for search include whether a page is mobile friendly and how rapidly it loads

Showing only results that use AMP would be a very coarse cudgel to enforce page speed. It is entirely within Google's ability to simply directly measure page speed, and to my eyes the more sensible course of action given the capability.

Re:Google Seeks to Pacify Consumers with Faster Mobile Pages by ska on Wednesday February 24, 2016 @12:36PM (#11168529)
You have to imagine someone there is already measuring this, if for no other reason that evaluating the effectiveness of their own approaches.
Re:Google Seeks to Pacify Consumers with Faster Mobile Pages by cromwellian on Wednesday February 24, 2016 @01:25PM (#11168946)
AMP does more than just minimize network requests or JS loading size, it structures the page so that browsers can render it faster as well. (that is, controlling for network download and JS parse time)
Re:Google Seeks to Pacify Consumers with Faster Mobile Pages by ck2 on Wednesday February 24, 2016 @12:43PM (#11168584)
You are inlining the script on the same html page?

Hope you are using chunked transfers so it will render sooner, pre-gzipped streams end up not being chunked in nginx.

Google has already said AMP is not used as a ranking signal (but mobile friendliness is).

Re:Google Seeks to Pacify Consumers with Faster Mobile Pages by Ded7xSEoPKYNsDd on Wednesday February 24, 2016 @05:10PM (#11170643)
I am confused. Are you referring to 'Transfer-Encoding: chunked'? That's obviously very useful for dynamically generated content. But what advantage does it have over a simple Content-Length header?