Optimization Of Google Site

More recently, clients have become increasingly interested in optimizing the Google Pagespeed Insights site. I mean, they come into this service, they hit their website address, and they get about that:

What does this indicator affect and who needs it? The official position of the google is that: “Your websites have to work fast, and then we will rank them a little higher, perhaps”. Anyway, the websites have to work fast. If even the google doesn't rank the site above, your website's behavioral factors will probably improve if the site blends faster.

Today, I decided to optimize the downloading of our website and achieved this:

It would be possible, of course, to get lost with the optimization of the pictures and win a few more, but I don't think it's worth it, especially since the Google itself says, "If the page has scored more than 85 points, it's uploading fast, that's 95/100, that's more than enough, especially since we have a small social network and not a small corporate site.

Next, I want to talk about what the main points were and how they were addressed.

First of all, let's bring a full log of mistakes that googles complained about.

I mean, he didn't like the most scruples in the hat.
Shortly, I moved them all to the basement, but there's a very interesting point here: there's a spicy record of styles.css, and I've rolled it to the bottom of the page, and I've still received this warning.

I've been very relieved because he asked me to take it from the top of the page. Question: below?)

In the end, I made it easier: in the hat, I wrote it in my head.

I mean, I made this SSS-Fail enclused, I put it in the variable, I replaced him with the relative URLs to the absolutes, and how it put it on the page itself. That's the way the google is. Whereas in the final version, the difference between such an approach and simply the reference to CSS is quite serious (-7% if by reference):

The second thing he's complaining about is the absence of server headlines expired.

Without an indication of the duration of the file, the browser is contacting the web server each time for this file.

In nginx, it's treated like:
In the directive server {
location ~* /.(woff)cs)js)png)jpg)jpeg)tgz)rar)bz2)doc)xls)exe)pdf)ppt)tar)wav)bmp)rtf)$
access_log off;
expires 30d;
♪

Here's an example of server headings in the absence of this information in FireBug.