Broken nested elements after page cache priming

  • Resolved T4ng

    (@schwipps)


    2 years, 3 months ago

    We often face missing CSS issues after cache warming, specifically on nested elements of pages. In other words, when I inspect the HTML of a page properly loaded, and the same when it’s broken, the only difference I can notice it that it basically misses its dediacted inline CSS (These are Elementor templates).

    For example, we insert Elementor templates with shortcodes, including elements that might take a bit longer to load (large image, for example).

    Long story short, I feel like these templates could take a bit too much time to load, so that the page would get cached a bit too early. Before the whole content of these nested elements were fully loaded.

    Is this possible with W3 Total Cache?
    How could we inspect, solve this point?

    Thanks

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    2 years, 3 months ago

    Hello @schwipps

    Thank you for reaching out and I am happy to help!

    What you may want to try is to switch the page caching method to Disk: Basic or memory based caching like Redis or Memcached, and enable the Late caching: option in Performance>General settings>Advanced section.

    It would be great if you could share the website URL and also let me know if the suggestion helps!

    Thanks!

    Thread Starter T4ng

    (@schwipps)

    2 years, 3 months ago

    Hi, thanks for your suggestion.

    We already use Redis. However, we didn’t use the late caching option so But I just activated it to give it atry.

    Unfortunately, it doesn’t help. I faced the exact same issue after applying the setting, and clearing all caches.

    To check if the issue was gone, I went to a page where the issue often occurs. It wasn’t preload/warmed yet, so I had it served from the origin. And the issue occured: missing expected CSS for that same nested section.

    I guess this means the issue occurs before the Redis. Howvever, it’s still related to W3 Total Cache since it never occurs when it’s disabled.

    Any other ideas to troubleshoot this?

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    2 years, 3 months ago

    Hello @schwipps

    Can you please check the embed method in Elementor -> Settings -> Advanced -> CSS Print Method

    Let me know if it set on internal or external.

    Thanks!

    Thread Starter T4ng

    (@schwipps)

    2 years, 3 months ago

    We use the Internal Embedding, for a while now, since the other method used to be problematic.

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    2 years, 3 months ago

    Hello @schwipps

    Thank you for your feedback.
    Can you please perform one more test? Exclude the problematic page from the cache in Performance>Page Cache>Advanced>”Never Cache following Pages” and let me know if this helps at all.

    Thanks!

    Thread Starter T4ng

    (@schwipps)

    2 years, 3 months ago

    Hi Marko.

    Thanks for the tip, but it would be very difficult to troubleshoot.

    By the way, after testing it for 2 days, I had to untick the late caching option you suggested, since I noticed that pages weren’t remaining in cache more than a few minutes, instead of 12 hours.

    I don’t know how this option is meant to work, but it definitely doesn’t fit our environment.

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘Broken nested elements after page cache priming’ is closed to new replies.