Viewing 6 replies - 16 through 21 (of 21 total)
  • Thread Starter freddyee

    (@freddyee)

    yeah, that issue is solved when setting OFF “load async CSS”, but it kinda affects the speed.

    Is there a way to have that option ON but without having that issue with the fonts ?

    Plugin Support qtwrk

    (@qtwrk)

    Hi,

    it’s basically a tradeoff you need choose , speed or UX

    I wish there is a way to make it both happen , but unfortunately no.

    Best regards,

    Thread Starter freddyee

    (@freddyee)

    I see.

    Why doesn’t “Critical CSS” solve that problem ?

    Plugin Support qtwrk

    (@qtwrk)

    you got it reverse

    the issue is exactly brought in by CCSS

    when you have CCSS , HTML renders immediately WITHOUT font being loaded , that’s why you see that “X” mark , that is place holder for an icon from a font file that has not being loaded yet

    Thread Starter freddyee

    (@freddyee)

    ohh I thought that when we have Generate Critical CSS ON, there wouldn’t have been that kind of issues. I read that on this link.

    https://docs.litespeedtech.com/lscache/lscwp/pageopt/#load-css-asynchronously

    Once the Critical CSS has been generated, it will be loaded first, and then the rest of the CSS will be loaded asynchronously with the HTML. The page will no longer load without formatting.

    Plugin Support qtwrk

    (@qtwrk)

    it’s Critical “CSS” , not Critical “Font” : )

    and technically speaking , the page is loaded with format, but font file just takes longer to load

    • This reply was modified 4 years ago by qtwrk.
Viewing 6 replies - 16 through 21 (of 21 total)
  • The topic ‘mobile display problem’ is closed to new replies.