Hi, You are understanding what the plugin does, wrong.
The plugin purpose is to merge css and js into groups.
Those groups can happen to be 1 file, or more (it’s explained on the faqs).
For your site:
https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%2Fomniaaerospace.com%2F
You have 1 header and 1 footer js file + the google translate script.
You have 2 header css files + the google translate css.
The JS part… your plugins or theme (all together) enqueue js files both in the header and in the footer, therefore you must have at least 1 file in the header and another one on the footer.
The CSS part… one file is for the common CSS files that got merged together into one, and the second file is for the mobile css only files that got merged into another file (mobile cannot be merged into normal files).
If you look into the logs on the status page, it tells you which file names were merged into each file.
As for the google translate file, those are not on your domain name, so they are not merged together. The plugin doesn’t merge external files for compatibility reasons… but you could manually code on the functions.php theme file, to dequeue those files and enqueue a local version of those. That way, FVM can capture them.
As for having JS files on the footer and header, each theme author or plugin author decides where they want to enqueue the files. You cannot easily move the JS files to the header, but you could move them to the footer (through your theme functions.php file coding)… however, doing that is not recommended if you don’t understand what each file does exactly.
If you move a JS file to the footer, nothing that depends on it during the page load can work. For example, you may have the jQuery in the header and have a script do something with jQuery. If you were to move it to the footer, that code would not work.
For JS files, you can prevent the render blocking message on pagespeed insights by enabling the Enable JS deferring for pagespeed insights.
You cannot yet defer CSS with FVM, because that’s an advanced feature for developers.
If you defer CSS / move the css to footer, without properly adding the complete critical path css (via coding on the functions.php theme file), you will get other errors on pagespeed insights and a FOUC effect when loading the page.
You can eliminate the render blocking message for CSS if you enable the Inline CSS for the header and footer, however note, if your CSS is too big, other messages will show up, such as “prioritize visible content”.
As for HTML minification, you are using the alternative minification system, which only strips excess line breaks and space and it’s meant to be used only, if the other one doesn’t work.
I must add, that while FVM makes things a bit easier for anyone to try the different options and get a better score, speed optimization is something that should be done by someone that understand what these options do and mean.
Looking at your settings, those would be the last things I would select.
For example, why would you select the option to disable google fonts merging, or why would you use the alternative html minification?
You should probably unselect everything, and select only:
Inline google fonts
remove the print styles
enable defer of js for pagespeed
You can also try the Inline header and footer css options and see if there are any other errors on pagespeed, or if your score is better or worse.
A final note:
The Poor score, is due to the “Reduce server response time” which can only be bypassed with a faster server, or some cache plugin.
Basically, your server is slow and it needs several seconds to start outputting anything to the users.
FVM only optimizes how that output looks (html, css, js), once it starts.
