I’m not sure if you are aware… but your review makes no sense.
You have installed a plugin that does precisely what you’re complaining it did and you haven’t even bother to check the settings or read the faqs on how to configure it.
It doesn’t parse some CSS such as extra spaces for readability
Note: That’s what the plugin is supposed to do, to strip all extra whitespace so it’s minified and thus, provide you with a faster / smaller site. Did you install the plugin without knowing what it does?
It breaks Fontawesome
Note: Yes it does, by default it removes all fontawesome files from your site and adds our own in async mode in the footer. You can however select the option that says “Disable Font Awesome optimization” on the plugin settings page.
You could have seen the settings page as well as the plugin description and help page, before giving a bad review.
You might think it’s broken because you didn’t bother reading the instruction AND didn’t use the support forum to ask any questions, You may not understand what it does, but the plugin is doing exactly what it’s meant to do.
Surprisingly, while you didn’t bother reading or asking questions, your first and only review on this site was to leave a bad review on this plugin.
I might be wrong, but makes me think that this review is paid by a competitor plugin.
I apologize if that’s not the case, but if you need help setting up the plugin, feel free to ask on the support forum. Support is free and for anyone.
-
This reply was modified 2 months, 3 weeks ago by Raul Peixoto.
It doesn’t just merely remove spaces. It was mangling the URLs.
I did try the setting related to Fontawesome. It breaks Fontawesome either way.
Moderator
Jan Dembowski
(@jdembowski)
Brute Squad and Volunteer Moderator
I’ve removed the tags modlook and sock puppet. Please do no re-add them.
*Reads*
This really would be handled in a support topic.
https://wordpress.org/support/plugin/fast-velocity-minify/#new-post
It doesn’t just merely remove spaces. It was mangling the URLs.
I did try the setting related to Fontawesome. It breaks Fontawesome either way.
Url’s inside css are also supposed to rewritten to absolute paths… if they are mangled to some random chars, then it could be that your css files have a non utf-8 encoding.
This usually only happens if you modify your theme (or someone did it for you) and save it with the wrong encoding… so the plugin can only read and process what’s “normal”, meaning utf-8 content. If you have a customized font-awesome file, that could be on the same situation.
Using the font awesome optimization setting will load the latest font awesome properly, however if the other css files are having “mangled” urls, there’s a big possibility that the references to font-awesome are also mangled.
The correct way to fix it, is to make sure your theme files are utf-8 encoded, which is the standard in all commercial themes and most free themes. There’s also the BOM mark in UTF-8 and other things: https://www.w3.org/International/questions/qa-css-charset
The plugin works properly with thousands of other sites (as you can verify looking at the installs and 5 star reviews) but it cannot work if there’s bad encoding or some problem on your theme (not saying there is).
If you really want things to be fixed, you should just open a support topic.
Posting a bad review just because “you’re not happy” or don’t understand how it works, won’t make any improvement. A support topic however, would have make it easier to solve this and have you benefit of a better site speed.
If you however, already tried another plugin that solves your issues then no need to worry about this one.
Thanks for your time.
Hi, just to let you know we have a new CSS processing logic and new features that could have sorted this out on v1.4.5. Kindly take a look if you have some time and would like to test it again.
