Issues with FOUC on assistly.group Site된

Sara M. · 2026-01-08T06:54:25.314Z

I'm having issues with FOUC on this site, which were not there before when we launched around a month ago. assistly.group (http://assistly.group) Any idea why it's an issue now? Did Webflow change something recently? Here's a read-only link. (https://preview.webflow.com/preview/assistly-staging?utm_medium=preview_link&utm_source=designer&utm_content=assistly-staging&preview=94a679dc3840f6c88d13c4f755c597b3&workflow=preview) Thank you very much

Issues with FOUC on assistly.group Site된 | Relume Community

14 comments

· Sorted by Oldest

Nabeel A.
·
·
Sara M. Webflow rolled out automatic FOUC prevention for GSAP / Interactions (IX3) a few weeks ago. It now hides elements until animations initialize, especially for from / fromTo animations. Your site didn’t show FOUC at launch because:
This behavior didn’t exist yet
Elements rendered immediately before animations ran
Now:
Webflow injects visibility: hidden
If animations are complex, overlap, or conflict with custom code, elements can still flash or appear late
Why you’re seeing it now:
You’re using Interactions with from or fromTo
Possibly combined with custom CSS/JS or complex targeting
Webflow’s auto-handling doesn’t always catch every case
Quick fixes:
Switch from/fromTo animations to to where possible
Remove any old manual FOUC hacks (opacity / visibility CSS)
Explicitly set initial styles in CSS for animated elements
Sara M.
·
·
Thank you Nabeel A.. They had rolled out the FOUC prevention before this site launched. Did they update it recently?
Nabeel A.
·
·
Sara M. Yes, webflow has updated how FOUC prevention works recently. Let's connect?
Sara M.
·
·
When did this happen?
Sara M.
·
·
And that means any sites using Webflow GSAP are having issues?
Nabeel A.
·
·
I think around mid-November 2025
Nabeel A.
·
·
No, not all Webflow GSAP sites are affected.
Sara M.
·
·
I think we launched mid-november so there shouldn't be an issue
Sara M.
·
·
we launched after they rolled out the FOUC feature.
Nabeel A.
·
·
The issue is not the initial rollout, but subsequent tweaks to the runtime behavior after rollout.
Sara M.
·
·
Really? That's upsetting. A big pull of Webflow is that you don't have to worry about updates.
Nabeel A.
·
·
You’re right and your frustration is justified.
Nabeel A.
·
·
Webflow didn’t break your site, but they did change the runtime behavior of a newer feature (GSAP interactions). That can surface edge cases even without republishing.
Sara M.
·
·
Is there an article somewhere that shows what I would need to change?

Nabeel A.
·
·
Sara M. Webflow rolled out automatic FOUC prevention for GSAP / Interactions (IX3) a few weeks ago. It now hides elements until animations initialize, especially for from / fromTo animations. Your site didn’t show FOUC at launch because:
This behavior didn’t exist yet
Elements rendered immediately before animations ran
Now:
Webflow injects visibility: hidden
If animations are complex, overlap, or conflict with custom code, elements can still flash or appear late
Why you’re seeing it now:
You’re using Interactions with from or fromTo
Possibly combined with custom CSS/JS or complex targeting
Webflow’s auto-handling doesn’t always catch every case
Quick fixes:
Switch from/fromTo animations to to where possible
Remove any old manual FOUC hacks (opacity / visibility CSS)
Explicitly set initial styles in CSS for animated elements
Sara M.
·
·
Thank you Nabeel A.. They had rolled out the FOUC prevention before this site launched. Did they update it recently?
Nabeel A.
·
·
Sara M. Yes, webflow has updated how FOUC prevention works recently. Let's connect?
Sara M.
·
·
When did this happen?
Sara M.
·
·
And that means any sites using Webflow GSAP are having issues?
Nabeel A.
·
·
I think around mid-November 2025
Nabeel A.
·
·
No, not all Webflow GSAP sites are affected.
Sara M.
·
·
I think we launched mid-november so there shouldn't be an issue
Sara M.
·
·
we launched after they rolled out the FOUC feature.
Nabeel A.
·
·
The issue is not the initial rollout, but subsequent tweaks to the runtime behavior after rollout.
Sara M.
·
·
Really? That's upsetting. A big pull of Webflow is that you don't have to worry about updates.
Nabeel A.
·
·
You’re right and your frustration is justified.
Nabeel A.
·
·
Webflow didn’t break your site, but they did change the runtime behavior of a newer feature (GSAP interactions). That can surface edge cases even without republishing.
Sara M.
·
·
Is there an article somewhere that shows what I would need to change?