Hi! How to force your inline css to store in a css file instead?
Hi!
I purchased your Brizy Pro LTD today. I love it so much, but I'm not too fond of the inline CSS on the HTML file. I like the HTML code to be clean. How can I force these inline to a CSS file instead?
I used to use Autoptimize Plugin to work on other site builders. But, this plugin is unable to aggregate the inline CSS of Brizy.
Refer to the screenshot. This is the inline CSS I am talking about.
This is the dashboard of Autoptimize Plugin.

Autoptimize used to work for all the websites I created with other site builders (Elementor & Divi). But, it does not work on Brizy.
Any help?
-
Hi,
Thank you for your message and for your feedback regarding Brizy! We are happy to hear that you like Brizy and use it with pleasure.
I checked the message and the screenshots from your post. Checking the first screenshot, I can't say that it is an inline CSS because the Inline CSS is the CSS code added inside and for a single element (<p>, <span>, <img>, <a> etc.). See here the reference. The CSS you show in the first screenshot is the global CSS styles added for the Brizy page because as you can notice it is added at the head of the page.
Let us know if we can help you with something else.
Best regards,
Sandra0 -
I know it is Global CSS. But, I'm not too fond of this type of Global CSS to be an inline style. I want it to be inside a CSS file just like other site builders do. Any solution? Other page builders not doing this way as this would hugely increase the size of the HTML file.
0 -
Hi,
I discussed with one of our developers about this structure of the CSS and he said that in Brizy, the entire CSS is generated dynamically for each page. This structure is an advantage (+ inc) for Google Speed something like a minimal critical path. Also, this is great for optimization reason because it is provided in a Dynamic way. Therefore, it isn't any reason to worry about the size of the HTML file and the optimization.
Best regards,
Sandra0
Please sign in to leave a comment.
Comments
3 comments