Microthemer

Product details

Q: Questions about Oxygen

Hi there,
I use Oxygen Classic a lot. While I love the control, it has a couple of issues I battle with. I currently resolve these with a lot of fudging with the backend builder code and handling all CSS in stylesheets. For context, I'm obsessed with keeping my pages to under 50 kb/pageview.
I'm curious if Microthemer might resolve some of these issues:
* Oxygen's natural (comparatively minimal) bloat and unnecessary classes being loaded by default. It's possible to optimise and replace Oxygen.css, but not the part that ends up in universal.css. If your tool can replace that or at least create something optimisable, I'm sold.
* Oxygen defaults to big > small media queries. Looks Microthemer can reverse that?
On the other hand, what bloat might this add? Please be honest!
Also... Will Oxygen 6 be supported, at least once it is out of beta?

rose46May 6, 2025
Founder Team
Sebastian_Microthemer

Sebastian_Microthemer

May 6, 2025

A: Hey there,

Thanks for getting in touch. In answer to your questions.

- Microthemer doesn't remove CSS added by other tools like Oxygen. So it would not help with reducing the size of universal.css.
- Microthemer only adds the CSS styles you create with it, and some JavaScript if you apply event based animations like inView. You can see what it adds if you visit the frontend as a non-logged in user (as an admin there are extra JS files to make the editor work of course).
- Microthemer uses big to small media queries by default, although you can choose from various sets (e.g. mobile first). Whatever you choose, Microthemer would not alter the order of media queries in Oxygen.
- In terms of bloat, Microthemer is considerate. It will added CSS styles that you create with it - it doesn't replace CSS. So it is additive. But it adds CSS in the most performant way it can. It loads CSS asynchronously for below the fold content (context 1400 pixels from the top of the browser). And it loads (minimal) above the fold CSS as an inline style tag by default to reduce http lookups. And it minifies CSS for non-logged in users. You should be able to use it while keeping under your 50KB goal as the render blocking above fold CSS will be minimal.
- Microthemer will support Oxygen 6 at some point, but it may not be the exact moment it comes out of beta. I'm currently focusing on the AI assistant at the moment: https://themeover.com/wordpress-css-editing-with-ai/

I hope that helps. Let me know if you have any more questions.

Thanks!
Sebastian

Share
Helpful?
Log in to join the conversation
Posted: May 6, 2025

Thanks!
I think there's one other question, then - how do you manage universal vs. page-specific CSS? Page-specific CSS, right? And is it pre-minified in output files?
I like to also mess around with preloading and so on. The asynchronous splitting sounds good - as long as there's clarity over how it's done and the ability to tweak it one way or another (even if that means custom functions.)

Founder
Posted: May 6, 2025

These videos explain how Microthemer optimises CSS as standard and then how to customise things:

- https://themeover.com/automatic-page-speed-optimisation/
- https://themeover.com/load-wordpress-css-on-specific-pages/
- https://themeover.com/folders/

Draft CSS is not minified, published CSS is minified in the output files.

Do these videos cover what you're looking for?

Related questions
View product details