Why is cached version different then non-cached

Hello @dusanvr

I have seen Divi theme with LiteSpeed cache and there were no BIG(or unsolvable) issues.
When you are logged in LSC will not do any changes to site.
When visiting anonymous(and LSC active) will send you a cached version of the page.

If switching the header fixes the problem, this means that the problem comes from the content.
I would try LSC different settings and see which one is best fitting your site. Remember to clear cache after each setting saved.

Tim

But what bugs me…

1. When I disable LSC plugin, page is shown properly. No content error. Header as expected and designed.
2. When I purge all and enable LSC plugin, header is not visible on anonymous visit (for desktop or mobile).
3. If I switch back header (to previous version), both (LSC or non LSC) versions are ok.

What I see is some caching of the previous header content, which had disabled content for one or other version (mobile or desktop).

But most of all, it cannot be content issue if it works with LSC plugin disabled? Is there anything LSC plugin would precache and no purge on Purge all? Some css file somehwere? Or what am I missing?

@dusanvr
Any cache plugin is modifying the content in a way to make it faster to load
I don’t want to go into details, which plugin does a good job or not.
I myself have optimized MANY sites with DIVI + LSC and I did not had trouble configurating the plugin and I had no errors.
Depends on what you have installed: plugins and what content you added.
You can play with LSC settings and see what helps and what does not help.

You can always check “uncached” version by adding ?LSCWP_CTRL=before_optm to the end of your URL.

I have seen two kind of problems — if “HTML minify” option is ON, page is sometime minified to nothing. Yes, to an empty page. So, keep this one off.

But most common issue is when you have UCSS on. UCSS is VERY powerful, but a bit of pain to set up correctly. You will have to compare cached and uncached version of the page, see what CSS is missing and add those selectors to the list of CSS selectors to be always present. Takes time, but worth the effort

After a looooooong forth-and-back through various scenarios, seems like the Cache Mobile setting caused the issue.

Though this is more of a bug than a specific site issue. Obviously something remains cached in this workflow I’ve had.