Google PageSpeed Insights Now Includes Real-World Speed Distributions (opens in new tab)

(developers.google.com)

19 pointscrisnoble8y ago14 comments

14 comments

6 comments · 2 top-level

ldiracdelta8y ago· 2 in thread

But you still can't have some inlined `data:image/*` SVG's on your page or you get "An error occurred while fetching or analyzing the page". Even though chrome renders the SVG just dandy.

igrigorik8y ago

Can you provide a specific URL or example where you're seeing this? I can't reproduce this: https://developers.google.com/speed/pagespeed/insights/?url=...

ldiracdelta8y ago

Didn't post before, because looks like link farming, but http://test.thirtytwomachine.com . If I remove the inline `data:image` files, pagespeed doesn't error out anymore. When I hit this problem, I found other people getting this exact behavior according to their online posts. Nuke the inline svg and pagespeed works again.

1 more reply

fludlight8y ago· 2 in thread

This says that the HN homepage is 2.7MB. Seems a bit high, but I’m on mobile so I can’t verify. Is that right?

igrigorik8y ago

I think you're misreading the copy: "PSI estimates this page requires 1 additional round trips to load render blocking resources and 0.0 MB to fully render. The median page requires 4 round trips and 2.7 MB. Fewer round trips and bytes results in faster pages."

The 2.7MB is a reference to the median.

fludlight8y ago

Just looked at a reasonably popular post with 116 comments using Chrome developer tools. Came in at 230KB of html and 4.5KB of css/js/images. This would qualify as way larger than the median page, since most pages are stories with <10 comments, user profiles, or individual comments.

How is google getting 2.7MB? Are they also fetching the third party URLs in discussion threads? Or maybe they mean median session?

2 more replies

j / k navigate · click thread line to collapse

14 comments

6 comments · 2 top-level

ldiracdelta8y ago· 2 in thread

But you still can't have some inlined `data:image/*` SVG's on your page or you get "An error occurred while fetching or analyzing the page". Even though chrome renders the SVG just dandy.

igrigorik8y ago

Can you provide a specific URL or example where you're seeing this? I can't reproduce this: https://developers.google.com/speed/pagespeed/insights/?url=...

ldiracdelta8y ago

Didn't post before, because looks like link farming, but http://test.thirtytwomachine.com . If I remove the inline `data:image` files, pagespeed doesn't error out anymore. When I hit this problem, I found other people getting this exact behavior according to their online posts. Nuke the inline svg and pagespeed works again.

1 more reply

fludlight8y ago· 2 in thread

This says that the HN homepage is 2.7MB. Seems a bit high, but I’m on mobile so I can’t verify. Is that right?

igrigorik8y ago

I think you're misreading the copy: "PSI estimates this page requires 1 additional round trips to load render blocking resources and 0.0 MB to fully render. The median page requires 4 round trips and 2.7 MB. Fewer round trips and bytes results in faster pages."

The 2.7MB is a reference to the median.

fludlight8y ago

Just looked at a reasonably popular post with 116 comments using Chrome developer tools. Came in at 230KB of html and 4.5KB of css/js/images. This would qualify as way larger than the median page, since most pages are stories with <10 comments, user profiles, or individual comments.

How is google getting 2.7MB? Are they also fetching the third party URLs in discussion threads? Or maybe they mean median session?

2 more replies

j / k navigate · click thread line to collapse