Improve docs rendering performance by addressing PageSpeed Insights issues

[Valloric]

Results from PageSpeed.

The easy ones are setting up cache expiration times for the font & css files and minifying the CSS. Eliminating render-blocking JavaScript and CSS in above-the-fold content is a bit harder, but shouldn't be too much work for a static site.

[huonw]

For triage/future comparison purposes, the current state is:

Desktop

91 / 100

Consider Fixing:

• Eliminate render-blocking JavaScript and CSS in above-the-fold content
• Leverage browser caching
• Minify CSS

Mobile

58/100 User Experience

Should Fix:

• Use legible font sizes
• Size tap targets appropriately
• Configure the viewport

81/100 Speed

Should Fix:

• Eliminate render-blocking JavaScript and CSS in above-the-fold content

Consider Fixing:

• Leverage browser caching
• Minify CSS

cc #20961

[Valloric]

Note the "how to fix" links on the PageSpeed site for each issue; clicking on them will provide more information, like a list of all static resources on the page that have been detected as not currently using browser caching etc. That extra debug info is what I've personally found to be a goldmine from PageSpeed.

[steveklabnik]

re-tagging as infrastructure and rustbook, as those are the two things that would need changed for this.

[brson]

Do we have an in-tree way to minify CSS already? Hm, since this is part of rustbook, I guess the minifier needs to be in rustbook. Do these issues only apply to the book or to rustdoc as well?

If this is a rustbook issue maybe it's not even worth fixing. Just wait to convert everything to mdbook.

[steveklabnik]

I don't believe so.

On Jun 27, 2016, 18:08 -0400, Brian Andersonnotifications@github.com, wrote:

Do we have an in-tree way to minify CSS already?

—
You are receiving this because you commented.
Reply to this email directly,view it on GitHub(#20962 (comment)), ormute the thread(https://github.com/notifications/unsubscribe/AABsir1M39J39kBpIkWNlkP8urMS_4oTks5qQEnegaJpZM4DQ7HC).