If Snassi Page Transitions is not working as expected, there are a few important things to check before contacting support. Many issues are caused by settings conflicts, caching, or theme and plugin compatibility, and these can often be identified quickly with a simple review.

Start with the basics

First, confirm that page transitions are actually enabled in the plugin settings. It sounds obvious, but this is one of the easiest things to miss when testing multiple configurations.

Then check whether the issue happens on all pages or only on specific ones. For example, the problem may only appear on WooCommerce pages, checkout flows, landing pages built with a page builder, or pages with unusual scripts.

It also helps to test while logged out in an incognito window. Some issues only affect regular visitors and not logged-in admins.

Check the transition settings

Before contacting support, review the key settings inside Snassi Page Transitions:

• confirm that transitions are enabled
• check which transition type is selected
• verify that the duration and delay settings are reasonable
• see whether WooCommerce disabling is turned on
• confirm whether the issue started after changing a transition style or timing setting

If the transition appears too fast, too slow, or broken visually, the cause may simply be a timing configuration that no longer fits the chosen effect.

Clear caching and optimization layers

Caching and optimization plugins are one of the most common reasons for transition issues.

Before contacting support, clear:

• plugin cache
• server cache
• CDN cache
• browser cache

If you use a performance plugin, temporarily disable features such as:

• JavaScript delay
• JavaScript defer
• file minification or combination
• remove unused CSS

Then test again. If the issue disappears, the problem is likely an optimization conflict rather than a bug in Snassi Page Transitions.

Test for plugin conflicts

Temporarily check whether another plugin is interfering with frontend behavior.

The most common conflict areas are:

• caching plugins
• optimization plugins
• script loaders
• animation plugins
• page builder add-ons
• WooCommerce-related customizations

If possible, disable unrelated plugins one at a time and test after each change. This can quickly reveal whether the issue is caused by a compatibility conflict.

Check theme and page builder compatibility

Snassi Page Transitions is designed to be theme-agnostic, but some themes or builders may add custom wrappers, AJAX navigation, or frontend scripts that affect how transitions behave.

Before contacting support, test:

• whether the issue happens only on one theme
• whether it only happens on builder-created pages
• whether it affects only certain templates or layouts

If the problem only appears with one theme or builder setup, that is useful information for support.

Look for page-specific or route-specific issues

Not every issue is site-wide. Try to identify whether the problem happens only on:

• product pages
• cart or checkout pages
• account pages
• pages with popup scripts
• pages with forms or special embeds

This matters because some pages have extra scripts or sensitive behaviors that may change how transitions should work.

Check browser and device behavior

Test the issue in more than one environment if possible.

Useful checks include:

• desktop vs mobile
• Chrome vs another browser
• logged-in vs logged-out
• normal window vs incognito window

If the issue only happens in one browser or on one device type, include that when contacting support.

Gather useful details before reaching out

If you still need support after checking the items above, try to collect the following information first:

• plugin version
• WordPress version
• active theme
• active caching or optimization plugins
• whether WooCommerce is installed
• which transition type is selected
• the exact pages where the issue happens
• whether the issue affects logged-in users, logged-out users, or both
• what you already tested

It is also helpful to describe the issue clearly. For example:

• “The transition does not start at all.”
• “The overlay appears but never finishes.”
• “The effect works while logged in, but not when logged out.”
• “The issue started after enabling a caching plugin.”

Final note

Checking these items before contacting support makes troubleshooting much faster. In many cases, the issue turns out to be a cache, optimization, or compatibility setting that can be resolved without deeper debugging. If support is still needed, sending the results of these checks will make it much easier to identify the cause.