What changes are Webflow making to the custom code cleanup process?
TL;DR
- Webflow now scans and issues warnings about deprecated or risky custom code, and may exclude non-functional code to optimize site performance.
- It enforces stricter security by sandboxing or altering third-party scripts and offers validation tools to catch syntax errors and deprecated resources before publishing.
Webflow is updating how it handles unused or problematic custom code to improve site performance and security. Here’s what’s changing:
1. Automatic Clean-Up Warnings
- Webflow now scans custom code blocks (in Page Settings, Site Settings, and Embed elements) for deprecated or risky code patterns.
- Warnings appear in the Designer or Publish panel when suspicious or non-functional code is detected.
2. Performance Optimization
- Any custom code determined to be non-executing or invalid (e.g., empty
<script>tags) may be automatically excluded from published sites. - This reduces unnecessary code from loading on the live site, speeding up page loads.
3. Security Policy Updates
- Webflow is increasingly strict on inline JavaScript and third-party embeds, especially if they conflict with the site's CSP (Content Security Policy).
- Some embedded scripts may be sandboxed or altered to conform to best practices.
4. Deprecated Script Handling
- Webflow may flag or remove unused third-party integrations, particularly older or faulty embeds, when updating sites or transferring templates.
- Webflow will prompt you to manually review scripts that are no longer supported.
5. Custom Code Validation Tools
- A new interface encourages users to validate their custom code before publishing.
- Warnings include uncaught syntax errors, blocked content, or scripts hosted on deprecated CDNs.
Summary
Webflow is improving the custom code cleanup process by detecting and removing ineffective or unsafe code, issuing clear warnings, and enforcing modern performance and security standards for embeds and external scripts.