News for hackers. Stuff that matters.

A comment on Kill Google AMP before it kills the web. Parent comment

Re:Kill Google AMP before it kills the web by belorn on Saturday May 20, 2017 @07:03PM (#14384836)
If you increase the penalty you also increase the artifacts from measuring the speed. Should it measure first byte, content above the screen size (and which size then), or fully loaded site. What about lazy load which neither method represent when a site is usable, but rather at what point javascript takes over the responsibility to load the site.

A small penalty devalues gaming the way google measure the speed.

[ Parent | on HN ]
Re:Kill Google AMP before it kills the web by codedokode on Sunday May 21, 2017 @04:24AM (#14386312)
This penalty also can have negative consequences on image quality on websites.

I had to worsen JPEG image quality to get good score for a website in Google's PageSpeed tools [1] because our management believes it affects search rankings.

That tool is awful. I would never follow Google's recommendations on my own site. The compressed versions of images it suggests one should use have visible artifacts.

[1] https://developers.google.com/speed/pagespeed/insights/

[ Parent | on HN ]