EMERGENCY🚨 Marquee Components not Loading on Homepage!

Description

Hi all, first time using Finsweet components here and running into a blocking issue on a client project.

I have two marquees set up on a homepage, and neither is displaying on the live site. Occasionally they flash/blink briefly before disappearing entirely, but they don’t render properly. This is completely breaking the homepage layout.

Video of what is happening

Required: Please provide a staging/production URL where we can see the issue

To clarify, this is PAID FOR and has an ACTIVE PLAN. The Marquee will not load on webflow.io OR on production. It’s just completely broken.

Hey @joel1, this looks like a bug.

The first time I loaded the page, the marquees loaded without issues. I’ve tried opening the page again in incognito, but it is now failing.

I’ll raise a report with the team so we can have a look and a fix ASAP.

Apologies for the inconvenience :folded_hands:

@Support-Luis thank you for the quick attention on this. Please dm or email me with anything you need to get this resolved as soon as possible.

Hey @Support-Luis, looking for an update here if you could. What’s the status and how quick of a turnaround time are we looking at?

Hey @joel1, it seems to be an issue with the initialization of the component.

The team is alerted, but due to the different timezones I am afraid we might have to wait a couple of hours before a fix is ready.

Apologies for the inconvenience :folded_hands:

Okay, well still hoping for a fix before the end of the day. Thank you.

@Support-Luis need an update here! We’re still broken!!

Hey @joel1,

We have identified that the issue is being caused by the images not being optimized.

We are currently exploring a solution for this. However, we want to avoid delaying initialization since that could negatively impact performance, so we are still evaluating the best approach.

In the meantime, could you try optimizing the images as much as possible? Compressing them and resizing them to the appropriate dimensions for the marquee should help reduce the issue.

If this resolves the problem on your end, it will also help confirm that the behavior is related to unoptimized images while we continue looking for a more robust solution.

@Support-Luis We can’t really optimize as these images are pulled in from an API. I would expect that your plugin would just work out of the box regardless of the image optimization.

@Support-Luis they’re also pulled in every 15 minutes or so and refreshed automatically… so yeah, not really an option in that process to change them

@Support-Luis I did just limit the list to 25 instead of 100, thinking that might help things. But it doesn’t look it like did.

@Support-Luis I actually was able to add image optimization into the API so the images on the second marquee are quite optimized now, and I limited it to 20 items, but the initialization still doesn’t appear to be working for me.

Are we sure it was the image optimization?

Oh wow @Support-Luis, it looks like the client is using humongous images for the logos that are supposed to be in one of these marquees. I will get those optimized as they are static, not dynamic. Hopefully that will clear everything up.

Okay @Support-Luis, I just optimized all the images being used in the Marquee and it still is not loading or initializing. So is that really the issue?

Hey @joel are the changes to the images live? I am still seeing the logos from the first marquee with huge file sizes and dimensions

@Support-Luis Yep, they’re live. This is the size that I am seeing.

Perfect, thanks for confirming.

It seems the change has not been reflected on my end, but I will alert the dev team so we can continue looking for a solution.

@Support-Luis

Maybe try a hard refresh? You may still be seeing cached images.

Either way, the issue still remains that the marquees are not initializing and we really need to get this solved as this is the client’s homepage after all. It was working before when we were testing it pre-launch.

Hey @Support-Luis what’s the timeline looking like on a fix here? We did what you requested by optimizing everything and we still are not getting results.

I need this fixed like yesterday.