A wooden fishing boat rests on deal in kent

Now we’re in real developer territory.

That warning:

“Added non-passive event listener to a scroll-blocking ‘touchstart’ event”

This is NOT an error.
It’s a Chrome performance warning.

What it means in simple terms:

When the browser sees events like touchstart or wheel, it pauses scrolling for a moment to check if your code might call event.preventDefault().

If the event listener is not marked as passive, the browser assumes it might block scrolling. So Chrome warns you.

In your stack trace:

• jquery.min.js
• jquery-migrate
• owl.js (Owl Carousel)
• script.js

This is coming from Owl Carousel + jQuery — not from your direct code.

Important:
Your site will NOT break because of this.
This does NOT hurt SEO.
This is only a performance advisory.

If the site scrolls smoothly → you can safely ignore it.

Now, if you want to fix it professionally:

If you were writing native JS, you’d do this:

element.addEventListener('touchstart', handler, { passive: true });

But jQuery’s .on() doesn’t natively support passive listeners. So if Owl Carousel is attaching events internally, you can’t easily modify that unless you:

1. Update to the latest Owl Carousel version
2. Replace Owl with a modern slider (like Swiper)
3. Remove jQuery Migrate if it’s not needed

Real engineering insight:

This warning usually appears in older libraries that were written before passive listeners became standard.

High-level thinking:

If you’re building long-term scalable products, reduce heavy legacy dependencies.
Modern, lightweight JS libraries = better performance + fewer console warnings.

So are you doing something wrong?
No.

Is it worth rebuilding everything for this?
Also no.

Fix it only if:

• You’re optimizing for Core Web Vitals
• Mobile performance is critical
• You’re building a premium SaaS product

Otherwise, ship the product. Optimize later.

Engineering is about impact, not perfection.