Hi @raven02,
Thanks for the kind words, glad the plugin’s working well.
On caching: in most setups you don’t need to exclude UAE’s footer template. The footer is rendered as part of the page HTML, so when a caching plugin caches the page, the footer comes along with it and gets served fast like the rest of the page.
Where caching tends to get in the way is right after editing the template. If you make changes and don’t see them reflected on the live site, clear the page cache and the browser cache, and if your caching plugin caches CSS and JS separately, clear those too. That usually sorts it.
The one situation where you’d actually want to exclude the footer from full page caching is if it has dynamic content that should change per visitor, like a login state indicator or a personalised greeting. In that case full page caching would serve a stale version, and you’d want to look at fragment caching or excluding that specific element depending on what your caching plugin supports.
Honestly though, the bigger thing to watch out for isn’t the page caching itself, it’s the optimisation features most caching plugins ship with. Things like JS deferring, JS/CSS minification, JS/CSS combine, critical CSS, and HTML minification can sometimes break Elementor and UAE widgets, especially anything interactive like accordions, popups, animations, or anything that depends on a specific script load order. If you ever see a widget acting up after enabling caching, try turning those optimisation features off one at a time to find the culprit. Most caching plugins let you exclude specific scripts or stylesheets from being deferred or combined, which is usually the cleanest fix once you’ve spotted the problem one.
For a typical site, caching the page is fine. Just keep an eye on the optimisation toggles, and clear the cache after editing the template.
Best regards,
Dhruv – BSF Support Team
