Critical Path CSS

  • Resolved jroland01

    (@jroland01)


    7 years, 5 months ago

    Hi –

    It is mentioned that the plugin has support for Critical Path CSS with CSS Async via LoadCSS. But I am unable to find that setting. Can you please help ?

    Thanks a lot in advance !
    Regards.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Raul P.

    (@alignak)

    Hi,

    We added this feature a few versions back, but it has been since then removed and it’s now under development for the future.

    Basically, I removed the CSS async option, because async doesn’t preserve the order of the css files, and most people end up with more than 1 css file generated.

    Async would make sense, only if you have a single, merged CSS optimized file per page (plus the critical path css), else css that was originally defined later can end up loading earlier and be overwritten by another async css file (it’s random, you cannot predict which loads first).

    I’m still looking into this for the future, but if you’re doing critical path optimization, you could “collect all css and then do uncss with gulp / grunt instead of looking for the critical path”. That however, not so easy for a non developer.

    Thread Starter jroland01

    (@jroland01)

    Hi Raul –

    Thanks for this clear answer.
    Good idea, I will try uncss.
    And thanks again for this great plugin.

    Regards.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Critical Path CSS’ is closed to new replies.