I’m building a Webflow site with Wized and Supabase, and I’ve implemented client-side caching using Wized local/session variables so product data is not refetched once visited. The caching works correctly, network requests are avoided, and data renders instantly after Wized logic runs. However, the issue I’m facing is with back navigation UX. When a user goes from a listing page to a product page and then navigates back, the page reloads instead of being restored from browser bfcache, causing a brief flash of the initial loader or default UI before Wized runtime initializes and reads cached variables. On pure Webflow sites or even WordPress sites, back navigation feels instant with no loader or re-render, which seems to be due to full bfcache restoration. My question is whether this behavior is fundamentally unavoidable in Webflow + Wized due to client-side hydration and runtime initialization, or if there are specific Wized patterns, settings, or JS practices that can preserve bfcache compatibility and prevent the loader flash entirely on back navigation.
That back navigation loader flash can definitely be frustrating! This happens because when you navigate back, there’s a brief delay while Wized initializes and reads your cached variables from storage. During this gap, users see the default loader state before your actual content appears.
While we can’t completely eliminate this (it’s a natural limitation with client-side frameworks like Wized in Webflow), we can help minimize its impact:
- Use the
wized-cloakattribute on elements that shouldn’t flash during loading - Design your loaders to closely match your content layout (skeleton screens work well here)
- Consider smoother transitions between loader and content states
A simpler approach might be to focus on making your loader less jarring visually - sometimes a subtle fade effect or matching the layout closely can make the flash less noticeable to users 
If you need more advanced customization for this specific issue, @elvisben can help with custom code solutions that might better detect cache status and minimize those visible transitions.