Hey guys,
could you build an option to minify the nicepage css file? Both google lighthouse and Seobility report a problem with it's size which affects SEO negatively.
It would be cool to just minify all css files that are being used by option.
Regards
Alex
Hello Alexander,
Thanks for contacting us!
Unfortunately, you cannot reduce the size of css file in Nicepage. But you can try using CSS Minifier/Compressor tools to minify the file. I cannot guarantee that everything will work properly. It depends on the tool you choose and their minification algorithm, but in general, you can try.
However, we have added your suggestions to our wish list.
...................................................
Sincerely,
George.
Nicepage Support Team
Please subscribe to our YouTube channel: http://youtube.com/nicepage?sub_confirmation=1
Follow us on Facebook: http://facebook.com/nicepageapp
Thanks! I'm sure there are many open source minify algorithms that you can build into your Software. It would be cool to minify the output with an option when exporting.
Thanks! I'm sure there are many open source minify algorithms that you can build into your Software. It would be cool to minify the output with an option when exporting.Hey Support Team,
I have been reading a few questions and answers here, and I think you guys need to understand the difference between minifying and tree shaking. People are asking for both.
Tree shaking is where unused lines are removed from a js or css file. This can result in breaking things because Nicepage uses some javascript to inject css classes into the DOM, and the tree shaking products can't see this.
But minifying is nothing like that. It's just a way to shorten code into something that computers can read just fine but not so much humans. All the code is still there, but it's just reformatted. So a variable named something like "strValueFromProcess1" in a javascript file might be renamed to something like "df" which of course is not intuitive to humans but the rendering computer just does not care. This example would reduce 20 bytes to 2 bytes, for every instance of that variable name. The key is that minifying is only applied after a versioned build of a css or js file is released. So the developers at Nicepage would never have to look at minified css or js. You could add a simple checkbox that allows customers to minify css and/or js, and they would get the benefits that we are all seeking. If they have problems with their site and need help, they can just uncheck those boxes so that the css and js can be human readable again, and then they/you can debug things as normal.
This question on the forum is asking for minification, not tree shaking. Your answer that says "I cannot guarantee that everything will work properly" and "depends on the tool you choose and their minificiation algorithm..." demonstrate that you are mixing up the two concepts. It should be extremely easy for Nicepage to select an industry standard minification tool that works with nicepage.js and nicepage.css, and allow customers to benefit from that. In fact, you could probably select any minification tool and it would do just fine with no problems at all.
I am here asking for minification. Can we get that?
Hey Support Team, I have been reading a few questions and answers here, and I think you guys need to understand the difference between minifying and tree shaking. People are asking for both. Tree shaking is where unused lines are removed from a js or css file. This can result in breaking things because Nicepage uses some javascript to inject css classes into the DOM, and the tree shaking products can't see this. But minifying is nothing like that. It's just a way to shorten code into something that computers can read just fine but not so much humans. All the code is still there, but it's just reformatted. So a variable named something like "strValueFromProcess1" in a javascript file might be renamed to something like "df" which of course is not intuitive to humans but the rendering computer just does not care. This example would reduce 20 bytes to 2 bytes, for every instance of that variable name. The key is that minifying is only applied after a versioned build of a css or js file is released. So the developers at Nicepage would never have to look at minified css or js. You could add a simple checkbox that allows customers to minify css and/or js, and they would get the benefits that we are all seeking. If they have problems with their site and need help, they can just uncheck those boxes so that the css and js can be human readable again, and then they/you can debug things as normal. This question on the forum is asking for minification, not tree shaking. Your answer that says "I cannot guarantee that everything will work properly" and "depends on the tool you choose and their minificiation algorithm..." demonstrate that you are mixing up the two concepts. It should be extremely easy for Nicepage to select an industry standard minification tool that works with nicepage.js and nicepage.css, and allow customers to benefit from that. In fact, you could probably select *any* minification tool and it would do just fine with no problems at all. I am here asking for minification. Can we get that?Hello
Thank you for providing such a detailed explanation and clarification regarding minification and tree shaking. I appreciate your input and understand your request for a minification feature in Nicepage.
We have added your suggestions to our wish list. Your advice and feedback are beneficial to our development.
...................................................
Sincerely,
George.
Nicepage Support Team
Please subscribe to our YouTube channel: http://youtube.com/nicepage?sub_confirmation=1
Follow us on Facebook: http://facebook.com/nicepageapp
