Exclude omgf-preload from being captured by LS Cache?

  • Resolved DaanvandenBergh

    (@daanvandenbergh)


    2 years, 3 months ago

    Hi!

    I’m the developer of OMGF, and I was wondering if there’s a way to exclude certain <link rel="preload" ... /> elements from being processed by LS Cache?

    OMGF offers its own way to preload font files, and I’ve seen it happen a few times that LS Cache removes these preload elements, causing font styles to jump around while loading.

    So, I’m wondering if there’s a compatibility fix or workaround I can offer these users?

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support qtwrk

    (@qtwrk)

    Hi,

    when you say from being processed by LS Cache?

    Could you please be more specific what kind of process it has done ?

    best regards,

    Thread Starter DaanvandenBergh

    (@daanvandenbergh)

    Well, they are removed entirely ?? When LS Cache is disabled, they reappear.

    Plugin Support qtwrk

    (@qtwrk)

    Hi,

    okay , I will try to reproduce and test a bit first

    do you have any way quick guide for how to setup/reproduce the issue ?

    Best regards,

    Thread Starter DaanvandenBergh

    (@daanvandenbergh)

    I’m not sure which options need to be enabled in LS Cache, but I’d suggest enabling all CSS and HTML related optimization settings.

    Using any theme using Google Fonts (e.g. TwentySixteen), install OMGF, run Save & Optimize, and check a couple of font styles to preload (Load Early).

    Then, load the frontend, and there should be no preloads present. Disable LS Cache, and you should be able to see them.

    Plugin Support qtwrk

    (@qtwrk)

    I set up a test site it seems works ok on me

    could you please go to site in question , LiteSpeed Cache -> Toolbox -> Import/Export -> export the setting and then send to support at litespeedtech.com with reference link to this topic ?

    that way , I can apply the setting to be exact same as this site and to reproduce the issue.

    Thread Starter DaanvandenBergh

    (@daanvandenbergh)

    When copying the site to a staging environment the issue disappeared — even with LS Cache enabled. It might be related to QUIC.cloud or a server level caching mechanism. For now, I’ll mark this as resolved. If I’m certain the issue is related to LS Cache, I’ll get back to you, but for now, there’s a big chance it’s not.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Exclude omgf-preload from being captured by LS Cache?’ is closed to new replies.