Description
Performance
I ran a Google Speed Test on your User Guide and it scored
- Mobile - 86%
- Desktop - 98%
Why it matters
Google has indicated site speed (and as a result, page speed) is one of the signals used by its algorithm to rank pages. And research has shown that Google might be specifically measuring time to first byte as when it considers page speed. In addition, a slow page speed means that search engines can crawl fewer pages using their allocated crawl budget, and this could negatively affect your indexation.
Page speed is also important to user experience. Pages with a longer load time tend to have higher bounce rates and lower average time on page. Longer load times have also been shown to negatively affect conversions.
Possible Solution
Three slowest loading assets
| URL | Size | Potential Savings |
|---|---|---|
| …css/font-awesome.css(rust-lang-nursery.github.io) | 8 KB | 780 ms |
| /css?family=…(fonts.googleapis.com) | 2 KB | 780 ms |
| /css?family=Source+Code+Pro:500(fonts.googleapis.com) | 1 KB | 780 ms |
loading local fonts should remove the fonts.googleapis.com and option to using only the necessary amount of FontAwesome assets.
Other Optimizations
- Async load CSS and Javascript
- Minimize CSS, HTML, and Javascript
- Determine and remove unused CSS