Hacker News Reader

> How to Be Fast, Like Google

>> Make Less Requests

From 130 requests, that's an odd takeaway.

I don't think you read the article. Devtools shows 130 requests because it considers inline data URIs to be a request--instead, there are lots of inlined images. so the page looks mostly complete with only the original document request.

I did read the article that's I picked to sentences from there. I did not pick up from the article that chrome counts inline data as requests and I did not know that earlier.

I find that even more odd that inline data is counted as requests.

edit: stand corrected, thanks for pointing out

> Important: It’s worth noting that each one of these Base64 encoded images is counted as a “request” in the Network tab of Chrome developer tools. This explains why there are so many images “requested” but the page is so fast. The browser never goes over the network to get them!

I paused at that as well, maybe it makes sense to think of it as a "request for additional execution" where it happens to be to Base64decode the data URI or pull the image from a remote server.

Clearly the article means "make fewer render blocking requests."

Reply on news.ycombinator.com