Hi Greg,

Thank you for reaching out.

I checked your site, and there are JavaScript errors in the browser console that seem to be related to an external third-party script:

Failed to load resource: net::ERR_BLOCKED_BY_RESPONSE.NotSameOriginUnderstand this error
locations/:991 Uncaught ReferenceError: addRuWidget is not defined
    at locations/:991:10
(anonymous) @ locations/:991Understand this error
js:1  Failed to load resource: net::ERR_BLOCKED_BY_RESPONSE.NotSameOrigin

These errors appear to come from a ReviewSup / GetReviewSup widget or integration, not from LayerSlider itself. The request is being blocked by the remote server with a 403 Forbidden response, most likely because of a cross-origin/security restriction, incorrect domain authorization, or a configuration issue on that service’s side.

When a third-party JavaScript file fails or throws an error during page load, it can sometimes interfere with other scripts on the page as well, including LayerSlider initialization.

I would recommend the following:

1. Temporarily disable the ReviewSup / GetReviewSup widget, plugin, or injected script and check whether LayerSlider appears again.
2. If that fixes the issue, please contact ReviewSup / GetReviewSup support and ask them to check why their script is returning a 403 Forbidden / NotSameOrigin response on your domain.
3. Also please make sure there are no security headers, CDN rules, firewall settings, or optimization plugins blocking third-party scripts.

At this point, the visible errors suggest that the issue is most likely caused by this external script or its server-side configuration, rather than LayerSlider directly.

Thank you for the feedback.