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.

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=...

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.

Interesting. Can I bug you to file this on https://groups.google.com/forum/#!forum/pagespeed-insights-d...? We should investigate what's going on there.

Thanks for caring about a grumpy (non-paying) customer. I'll file it.

I see similar svg issues are posted already: https://groups.google.com/forum/#!searchin/pagespeed-insight...

Also, the error message is a bummer. "An error occurred while fetching or analyzing the page". If you told me some parser state in the error, at least I could feed that back to you guys, even though it'd confuse a great many web developers.

Yep, good feedback. Will route it to the team :)

Here's the google groups thread I just started:

https://groups.google.com/forum/#!topic/pagespeed-insights-d...

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?

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.

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?

I believe that refers to the median of all analyzed pages, not the median page on that domain.

I pointed the tool at a Tumblr blog, and I see: "PSI estimates this page requires 6 additional round trips to load render blocking resources and 1.3 MB to fully render. The median page requires 4 round trips and 2.7 MB. Fewer round trips and bytes results in faster pages."

(Edit: pwinnski was faster than me)

I think 2.7MB is the size of the average web page on the Web on mobile (3.4M on desktop). Which is quite scary. (Edit: though this may refer to pages that are being developed and tested in Page Speed, see the other comment).

I wrote a whole (private, small) website with pictures (photos and images) and styles that includes a maze using JavaScript in 0.6 MB total. I didn't spend too much time in optimizing this.

I cheated a bit: links in this website point to anchors in the same HTML file. This does mean that without this trick, one page would be even lighter.

I would find it hard to write a 3MB webpage without doing it on purpose. Something is wrong with Web development. Stop wasting resources!

Ripppp I just put up a new site and Google is saying that it took 6 round trips and 4.1mb to fully render.... http://www.themindsetapp.com . It's just a wordpress site atm, any tips to reduce it?