[igrigorik]

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.

[fludlight]

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?

[pwinnski]

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

[jraph]

(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!