Webflow Introduces Per Page CSS & JavaScript

Webflow has rolled out two powerful features — Per Page JavaScript (launched on February 18, 2025) and Per Page CSS — both designed to significantly boost site performance by loading only the code needed for each page.

These long-awaited updates tackle one of the biggest performance challenges: unnecessary CSS and JS bloating every page. Now, instead of loading the entire site’s CSS or JavaScript on every page, Webflow ensures each page only loads what it needs — nothing more.

Why This Matters

  • Faster Page Loads: Early data shows that Per Page CSS can reduce file sizes by 30–40%, while Per Page JS has already improved Lighthouse scores by over 12% on average.
  • Better User Experience: Faster load times mean smoother browsing, lower bounce rates, and better SEO.
  • Cleaner Code Management: Developers and designers benefit from more streamlined, modular styling and scripting — less clutter, easier debugging.
  • Ideal for Large Sites: These features are especially helpful for large-scale Webflow projects where every bit of performance counts.

Rollout & Access

Both features are being gradually rolled out and can be enabled in your site settings under Advanced publishing options. They’re disabled by default and must be manually activated by Workspace or Site admins.


:page_facing_up: Official Pages

These updates reflect Webflow’s continued commitment to empowering designers and developers with performance-focused, scalable tools. It’s a major leap forward for serious Webflow users.

Hi there,

Per Page CSS and Per Page JavaScript are optimization features that can help improve your site’s loading performance:

Per Page CSS splits your CSS into two files:

  • A shared file containing global styles
  • Individual page-specific files with styles unique to each page

Per Page JavaScript works similarly by creating separate JavaScript bundles for each page instead of loading all scripts site-wide.

Please note that while these features can improve page load times by reducing unnecessary code loading, they may cause styling and functionality issues if your site uses custom code or a shared Library.

Hopefully this helps! If you still need assistance, please reply here so somebody from the community can help.