4 ms·
What also seems to be missing in Google's metric is that of Page Size. That is, by also having less bytes in the page, then less bandwidth is used. Since less
by cmroanirgo 9y ago
What also seems to be missing in Google's metric is that of Page Size.
That is, by also having less bytes in the page, then less bandwidth is used. Since less bandwidth is used, less energy is used.
Unfortunately, Google doesn't measure, nor seem to care about energy consumption, as GoogleBot only cares about response times. (Of course, there are energy concerns regarding that too...but it's only every about speed with google and punishes everyone else for not evangelising it)
Using Page Size as metric has important benefits that Page Speed deliberately undermines. It also resurrects the notion that using external cached css and js is a good thing.
Did you know that in order to get 10 urls (the thing that you and I actually want) from google, you need to download 500K? It seems ludicrous to me. Each search result is chock-full of css and js that doesn't change.
Thankfully HN is old-school and uses external files and good-ol' minimalism.
2c
- jakelazaroff 9y agoAren't page size and page speed (and energy consumption) correlated? If you request a 1mb page and a 1kb page from the same server, the 1kb one will load faster in basically all scenarios If you can test speed close to the requester geographically, it's possibly an even better indicator of energy usage because it also implies the data doesn't have to travel as far. Also, Google has no idea what external resources your browser has cached locally.
- yorwba 9y ago> Also, Google has no idea what external resources your browser has cached locally. I'm pretty sure they have enough data to figure that out.