the plugin has not optimized the code

Nah, it has done what is does by default ??
* aggregate all CSS & linked it in head
* aggregate all JS (except jquery.js) and load it with defer attribute at the bottom of the HTML

What you can do to improve;
* look into “inline & defer” (see AO FAQ for more info)
* try removing js/jquery/jquery.js from the JS optimization exclusion list (and test, because your theme/ plugins might need jquery available early)

hope this helps,
frank

I do not understand where is “inline and defer CSS”? In the advanced settings there is no such item.

Might be a mis-translation, it’s the 5th checkbox under “CSS Options”;

Hello! Please tell me how to postpone the download of this file?
https://prntscr.com/m9wypc

Well, “inline & defer css” will make the CSS non-render blocking (which it is now) by “preloading” the full CSS.

But when doing so you might still have that somewhat confusing “defer unused CSS”-warning;

When you’re using “inline & defer” (potentially with the automated critical CSS plugin) the critical CSS is inlined and the full CSS is technically not deferred but “preloaded” meaning it is loaded without it being render-blocking (which is a separate GPSI recommendation). AO uses Filamentgroup’s loadCSS for this purpose.

The advantage of using “preload” is that the page below the fold is styled as soon as possible without the CSS being render blocking. It to f it would be deferred (as AO used to do a couple of versions ago) the chance was bigger that the user scrolled down to a part of the page that was not styled yet. Given the fact that preloading the full CSS does not block rendering, there is little advantage to be found in deferring it instead and the disadvantage might be significant.

So, go with “inline & defer”, make sure you have no render-blocking JS and your “start to render time” will be immensely better ??