• Resolved nirajnagar

    (@nirajnagar)


    Hello Team,

    I recently switched from Litespeed to your plugin. I found it better then Litespeed for my website. But I face the same issue which is not with Litespeed but all other plugins, AirLift or yours.

    This issue is intermittent, not on all products. it removes all the items from header. May be a conflict with theme but it is there.

    To get the header items back, i have to remove all the cache, first de-activate the plugin and to use cache, I have to re-activate the plugin.

    I am sharing the picture of both the headers, blank and normal for your kind review.

    live product url

    https://www.rbhomoeoshop.com/product/p3-allergy-drops-30ml/

    Screenshot without header items
    Screenshot by Lightshot

    Screenshot with header items

    Screenshot by Lightshot

    You are requested to please review this issue and suggest a solution.

    Regards,
    Niraj

Viewing 1 replies (of 1 total)
  • Plugin Support Poonam Namdev

    (@poonam9)

    Hi @nirajnagar,

    After reviewing the response headers from your product page, I noticed something worth investigating further. Even though you’ve switched away from the LiteSpeed Cache plugin, the response headers still show:

    X-Turbo-Charged-By: LiteSpeed

    This suggests that LiteSpeed may still be active at the server level.

    Could you clarify: did you only deactivate the LiteSpeed Cache plugin, or has LiteSpeed caching been fully disabled at the server/hosting level as well?

    If the server-level LiteSpeed cache is still running, it could be capturing your page at a moment before your header elements fully load (since they appear to be rendered dynamically via JavaScript), and then serving that incomplete snapshot to visitors — which would explain why the issue is intermittent and appears across multiple caching plugins.

    Please check with your hosting provider to confirm whether server-level LiteSpeed caching is active, and if so, try disabling it to see if the header issue persists. That would help us narrow down whether this is a server cache conflict or something else entirely.

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.