Hi @Lucian_Dinu,
Thank you for your message and clarification about the @mixin use.
Please allow me to expose the issue again: Imagine you start a website from scratch or from an already made template, you play around with the components (presets), you add, you test, you don’t like, you remove, then add other components, and you keep doing this until you’re happy with your design. Now you are ready to publish. What is happening is that you are also publishing all the presets that have served as tests (those which you have decided to discard) - let’s call them draft presets -, along with those you have kept. And this is the issue I wanted to point out.
It would be great to not publish the draft presets and only ship the used ones. The best way to do so, is to implement a presets cleaner, that is triggered just before publishing. Until implementing this cleaner, the workaround would be to clean them manually (but it is risky, as @Andre said in this post). In this case, it would be better to have a tutorial that helps us to do so, until the implementation of the cleaner.
In my humble opinion, having presets cleaner is a must. Using tools like SiteJet are created to ship website rapidly and not waste our time in cleaning code (and here is where I refer to “clean code”).
In your screenshot, you referred to preset CSS code, but of course the same applies to the JavaScript code that comes with the presets (if any).
The goal is to only ship what we use.
And regarding your comment:
⇒ Even if when we only ship what we use, there will be still some hints (“Reduce unused JavaScript” or “Reduce unused CSS”), but it will be reduced compared to shipping with draft presets.
And it is normal to have these hints, as you said (which is common, as not all JS or CSS code are executed on page load), but just keep them reduced to the maximum.
Hope this clarifies my point, and thank you again for your reply.
Please point me to the SEO features that you mentioned, so I can upvote them.