How can I address JavaScript-related issues with my Webflow site to improve its speed, particularly in regards to unused JavaScript, execution time, and minimizing main-thread work, considering that I have no experience with JS or custom code? I have already tried minifying HTML, CSS, and JS, as well as cleaning up unused classes, but these tweaks resulted in a slightly worse performance score.

JavaScript-related performance issues on your Webflow site—like unused JS, long execution time, and main-thread blocking—often result from third-party integrations and built-in Webflow scripts. Since you’re not using custom code or JS, the root issues are typically embedded components or scripts added via Webflow functionality.

1. Audit Third-Party Integrations

• Check for third-party embeds or plugins (e.g., Google Maps, YouTube, chat widgets, analytics).
• These additions load external JS files that can significantly affect site speed.
• Remove or defer non-essential embeds if they aren't critical to your user experience.

2. Use Webflow’s Built-in Features Instead of Custom Embeds

• Replace embedded external tools (like YouTube iframes or complex forms) with Webflow-native elements when possible.
• For example, use Webflow video components instead of iframe code, which reduces JS load.

3. Defer or Lazy Load Scripts

• In Project Settings > Custom Code, check for code snippets added under Header or Footer.
• If you need to keep any tracking or embed codes (e.g., Google Analytics), place them in the Footer to defer execution until after the page loads.
• Use loading="lazy" for all images and videos where supported. Webflow applies this to images by default, but double-check for manual embeds.

4. Minimize Webflow Interactions and Animations

• Complex Webflow interactions use JavaScript under the hood, contributing to main-thread blocking.
• Audit your site for intensive animations (like scroll-triggered animations or page load interactions).
• Simplify or remove unnecessary animations, particularly those activated on page load or scroll.

5. Limit Usage of Lottie Animations

• Lottie files are JS-driven and can increase scripting time.
• If you're using Lotties, ensure they're optimized (lower frame rates, smaller file size) and only trigger when in view.

6. Reduce Number of Pages Loading Scripts

• Webflow often loads scripts globally, even if only used on one page.
• Go through your components (such as sliders or tabs) and consider:
• Removing unused components.
• Consolidating features to fewer pages or rethinking UX to reduce JS dependencies.

7. Analyze with Lighthouse in Incognito Mode

• Run a Lighthouse audit in Chrome Incognito to avoid extensions skewing results.
• Pay close attention to:
• “Reduce unused JavaScript” and click to view which files are largest.
• If many are from webflow.js or analytics sources, that confirms third-party/script bloat.

Summary

To reduce JavaScript bloat in Webflow without coding experience, remove third-party embeds, minimize Webflow interactions, and defer script execution in Footer settings. Focus on replacing scripted content with native Webflow features where possible and audit your site structure to remove components that trigger unnecessary scripts.