Web Performance Profiling: Google.com
requestmetrics.com
Web Performance Profiling: Google.com
1–10 of 87 posts
Re: Web Performance Profiling: Google.com
#2I mean... is it? It feels a _lot_ slower than it used to, especially on slower devices.
Possibly that 700kB of random crap is implicated :)
Re: Web Performance Profiling: Google.com
#3I mean... is it? It feels a _lot_ slower than it used to, especially on slower devices. Possibly that 700kB of random crap is implicated :)
Classic HN. Snarky, condescending and nothing of substance. Reminds me why I visit HN less and less lately.
Re: Web Performance Profiling: Google.com
#4> How to Be Fast, Like Google
>> Make Less Requests
From 130 requests, that's an odd takeaway.
Re: Web Performance Profiling: Google.com
#5> 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.
Re: Web Performance Profiling: Google.com
#6> 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
Re: Web Performance Profiling: Google.com
#7It feels fast because most other sites are insanely slow.
Just build a normal HTML+CSS+JS site with serverside rendering, route the assets through a CDN and voila! your site will be just as "fast" as Google.
Re: Web Performance Profiling: Google.com
#8Earlier quoted context omitted.
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!
Re: Web Performance Profiling: Google.com
#9Honestly, Google is one of the modern marvels, even when I read the article and understand _why_ Google is so fast, I still cannot comprehend it.
To people over 30 years ago, this is a literal example of magic.
Re: Web Performance Profiling: Google.com
#10> How to Be Fast, Like Google >> Make Less Requests From 130 requests, that's an odd takeaway.
Clearly the article means "make fewer render blocking requests."