Elementor global css and page/post specific css not deferred

Ah, I didn’t receive a mail notif. about your post @createandcode, sorry for the delayed response.

Interesting question, I’ll have a look!

frank

Can’t reproduce I’m afraid;
1. by default the elementor CSS was aggregated
2. when adding elementor to AO’s CSS optimization exclusion list, the CSS was -obviously- excluded but did come with rel="preload"

so somewhat of a mystery why this would work that way for you to be honest :-/

frank

@optimizingmatters – strange!
I’ve re-created it again on one of our servers so you can see it in action.
https://themedemo.commercegurus.com/elemtest/elementor-4/

When you tested it you may not have done enough ‘stuff’ on the page for Elementor to create the page specific css.

Colm

very strange; I can see it not being deferred on your test-site but can’t reproduce. have you reached out to the elementor-guys to hear if they’re doing something (integrating with AO’s API maybe)?

I fixed some logic in the GitHub repo that might apply here as well, can you download the Github AO zipfile and install it (disable the current one)?

frank

Hey @optimizingmatters

I installed the github beta – still the same…

https://themedemo.commercegurus.com/elemtest/elementor-4/

Would the fact this is a multisite instance make any difference?

still the same…

bummer :-/

Would the fact this is a multisite instance make any difference?

only if the sites would be on different URL’s, which is not the case here?

so have you reached out to the elementor-guys to hear if they’re doing something (integrating with AO’s API maybe)?

@optimizingmatters – nope not yet – I’ll do so and see what they have to say. Thanks for your efforts on this thus far. (Oh and the multisite instance are all on the same url).