Caching and performance plugins can sometimes interfere with Snassi Page Transitions. If transitions feel inconsistent, outdated, delayed, or visually broken, the cause is often an optimization setting rather than the transition itself.

Why this happens

Snassi Page Transitions relies on frontend JavaScript and CSS loading at the right time. Some caching or optimization plugins try to improve performance by changing how files are delivered. That can affect transitions if they:

• delay or defer JavaScript too aggressively
• combine or minify files in a way that changes execution order
• remove or rewrite CSS that the transition overlay needs
• serve stale cached files after you change plugin settings
• cache pages differently for logged-in and logged-out visitors

In some cases, the plugin may work perfectly for admins while regular visitors still see broken or outdated behavior because they are being served cached frontend assets.

Common symptoms

If caching or optimization is the cause, you may notice things like:

• transitions do not trigger at all
• the overlay appears too late
• the old transition style still shows after you changed settings
• animations flicker, freeze, or disappear halfway through
• the plugin works in one browser session but not another
• transitions work while logged in, but fail when logged out
• mobile and desktop behave differently

How to fix it

Start with the simplest step: clear every cache involved.

That includes:

• your caching plugin cache
• server cache
• CDN cache
• browser cache

After clearing caches, test again in an incognito window while logged out.

If the issue remains, temporarily disable optimization features one by one to identify the conflict. The most common settings behind transition glitches are:

• JavaScript delay
• JavaScript defer
• JavaScript combine/minify
• CSS combine/minify
• remove unused CSS
• HTML optimization that changes inline scripts

If turning one of those off fixes the problem, keep it disabled for Snassi Page Transitions or add exclusions.

Recommended exclusions

If your optimization plugin supports exclusions, exclude the Snassi Page Transitions frontend assets from aggressive optimization.

Useful identifiers include:

• snassi-page-transitions-frontend
• /wp-content/plugins/snassi-page-transitions/assets/js/frontend.js
• /wp-content/plugins/snassi-page-transitions/assets/css/frontend.css

If your setup also delays localized or inline script data, make sure the transition config is not being delayed separately from the main script.

Check for stale settings

Snassi Page Transitions can request fresh runtime settings on the frontend, so if settings changes are not appearing, make sure your caching or security setup is not interfering with that request.

If needed, check that requests to:

• admin-ajax.php?action=snassi_page_transitions_runtime

are not blocked, cached incorrectly, or stripped by a performance or security layer.

Best practice

Caching plugins are not automatically incompatible with Snassi Page Transitions. Problems usually come from aggressive optimization settings, not from caching itself.

A good approach is:

1. Enable caching.
2. Test transitions.
3. Turn on optimization features gradually.
4. Exclude Snassi assets from any setting that causes visual or timing issues.

This gives you the performance benefits of caching without breaking the transition experience.

Final note

If transitions suddenly start glitching after installing or reconfiguring a performance plugin, treat caching and optimization as the first thing to check. In most cases, clearing caches and excluding the Snassi frontend assets resolves the issue quickly.