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.
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.
The problem is that Google took this in such and embrace-and-extend direction that seems to benefit them and give them a lot more power than they had before. And I already think Google is way too powerful.
Their solution annoys me and creeps me out more than the problem did. By a large factor. I don't like them being so deeply involved at this kind of level. If they are going to do something, I can't think of something I would like for them to do other than just tuning the penalty.