# Marquee logs "No marquee instances found" on every page without a marquee

**URL:** <https://forum.finsweet.com/t/marquee-logs-no-marquee-instances-found-on-every-page-without-a-marquee/7568>\
**Category:** Finsweet Components\
**Created:** [September 29, 2026, 12:33pm UTC](https://forum.finsweet.com/t/marquee-logs-no-marquee-instances-found-on-every-page-without-a-marquee/7568 "2026-09-29T12:33:20Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![alexandreburgundcont](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.finsweet.com/alexandreburgundcont/32/5997_2.png) [@alexandreburgundcont](https://forum.finsweet.com/u/alexandreburgundcont)\
**Post date:** [September 29, 2026, 12:33pm UTC](https://forum.finsweet.com/t/marquee-logs-no-marquee-instances-found-on-every-page-without-a-marquee/7568/1 "2026-09-29T12:33:20Z")

</div>

Hi Finsweet team,

We use Finsweet Components (Marquee, Number Count and Slider) on a Webflow site. The components work well where we use them. However, the Marquee module logs an error in the browser console on every page that does not contain a marquee:

[marquee] - “No marquee instances found on the page when initializing Marquee component” - {}  
Source: chunk-2PJ4KWGC.js:9:556

What we observed:

- The app loads finsweetcomponentsconfig-1.0.16.js in the of every page (type=“module”, finsweet=“components”). It declares fs-components-installed=“numbercount,marquee,slider”, then loads @finsweet/fs-components@2.
- On pages with a marquee (e.g. our EPK page), everything works.
- On pages without a marquee (e.g. our blog listing), the Marquee module still initializes and logs the error above. It happens once per page load, with no visible impact for visitors.
- The script is injected by the Finsweet Components app, not by our own custom code, so we cannot scope it per page on our side.

Our questions:

1. Is this expected behavior? When no instance is present, a silent exit or an info-level log would seem more appropriate than an error.
2. Is there a setting in the app to load a component only on the pages where it is used?

We would rather not modify how the app loads its scripts, so a fix or a setting on your side would be ideal.

Thanks for your help!

---

<div class="post-metadata">

**Author:** ![Support-Finn](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.finsweet.com/support-finn/32/5169_2.png) [@Support-Finn](https://forum.finsweet.com/u/Support-Finn)\
**Post date:** [September 29, 2026, 6:31pm UTC](https://forum.finsweet.com/t/marquee-logs-no-marquee-instances-found-on-every-page-without-a-marquee/7568/2 "2026-09-29T18:31:29Z")

</div>

Hey @alexandreburgundcont!

What you’re seeing is actually expected behavior. The Finsweet Components app loads its configuration script globally across your entire site via the `finsweetcomponentsconfig` script in your `<head>`. When the page loads, it initializes every component listed in `fs-components-installed` — in your case: `numbercount,marquee,slider`.

On pages where a marquee exists, everything works as intended. On pages without one, the Marquee module runs its initialization routine, doesn’t find any valid instances (elements with `fs-marquee-element="marquee"` and `fs-marquee-instance` attributes), and logs that message. Same goes for Slider and Number Count on pages where those components aren’t present.

To answer your questions directly:

1. Yes, this is expected. Since there’s no marquee on those pages, the message is purely informational and has zero functional impact on your site or visitors.

2. There’s no documented option in the Components app to scope component loading on a per-page basis. The current architecture loads the script globally, and each component checks for its instances at runtime.

Your point about using a silent exit or info-level log instead of something that reads like an error is solid feedback 💪 We’ll flag it for the team — the log level is something that could potentially be adjusted in a future update.

If the console message is causing concern for client handoffs or monitoring tools, feel free to share your staging URL so we can verify the exact setup. But nothing here is broken — it’s just the script being thorough about checking for instances.