Webflow Performance Issues: Common Problems and How to Fix Them

Webflow sites can be fast. Really fast. But I keep seeing the same performance issues over and over again, and they're almost never Webflow's fault.

After fixing dozens of slow sites, I've noticed patterns. The same mistakes. The same quick fixes that everyone tries but don't actually work. And the same real solutions that actually move the needle.

Here's what I see breaking performance in real Webflow projects, with actual numbers.

‍

The Cookie Consent Script Problem

This is the big one. Cookie consent scripts are killing PageSpeed scores more than anything else.

Real example:

A client site dropped from 92 to 58 on mobile PageSpeed after adding Cookiebot. The script alone was 247KB, bigger than their entire homepage HTML.

Cookiebot's script blocks rendering for 1.2-1.8 seconds on a 3G connection. OneTrust is similar at around 280KB. CookieYes is lighter at ~60KB but still render-blocking.

Why it matters:

That's your entire LCP budget gone before your site even starts loading.

What actually works:

Defer the script so it doesn't block render. Use lighter alternatives (Cookie Consent by Finsweet). Or accept that EU compliance has a performance cost and optimize everything else harder.

What doesn't work:

Just accepting "cookie scripts are slow." The difference between a 280KB script and a 15KB custom solution is massive.

‍

Google Tag Manager Gone Wild

GTM containers I've audited average 8-12 tags. The worst I've seen had 23 tags firing on every page load.

Each tag adds weight. Facebook Pixel alone is ~45KB. LinkedIn Insight Tag is another 35KB. Google Analytics (GA4) is about 50KB. Add five marketing tools and you're easily over 200KB of JavaScript that blocks interactivity.

Real impact:

A site with 15 tags had a Total Blocking Time of 890ms. After removing unnecessary tags and deferring non-critical ones, we got it down to 210ms. That's a 76% improvement.

What actually works:

Audit ruthlessly. Most B2B sites don't need Facebook Pixel on every page. Use GTM's triggers to fire tags only where needed. Defer anything that isn't critical for the first 3 seconds.

‍

CSS and Webflow's Generated Files

Webflow generates one CSS file per site. On a typical marketing site, that's 80-150KB. On complex sites with lots of components, I've seen 300KB+.

Here's what matters:

Browsers can handle large CSS files fine if they're cacheable. The problem is when that CSS blocks rendering and you're loading 300KB of styles for a page that only uses 40KB worth.

Real numbers:

A 200-page site I worked on had a 340KB CSS file. After splitting templates and cleaning unused styles, we got it down to 180KB without changing the design. First Contentful Paint improved by 0.4 seconds.

What actually works:

Keep your class structure clean. Remove unused components. Split large sites into different templates so each page loads only what it needs.

Perfection kills progress, but you have to care of data. Fix what's possible. Speed Insights of petrbilek.com site as example.

‍

Images Kill Performance More Than You Think

Webflow has responsive images and lazy loading built in. But I still see sites uploading 4MB PNGs for hero sections.

Real example:

A hero image was 3.2MB. After converting to WebP and compressing, it was 180KB. That's 94% smaller with no visible quality loss. LCP improved from 4.1s to 1.8s.

The data:

Images account for 60-70% of total page weight on most sites I audit. Optimize them and you'll see the biggest performance gains.

What actually works:

Compress before uploading. Use WebP. Don't upload images wider than their container. For hero images on desktop, 1920px wide is plenty.

‍

Layout Shifts (CLS) Are Sneaky

Your site loads fast but PageSpeed Insights shows a CLS score of 0.25 (poor is anything over 0.1).

Common causes:

Cookie banners that push content down (adds 0.15-0.25 to CLS), images without dimensions (0.05-0.10 per image), web fonts loading late and reflowing text (0.05-0.15).

Real fix I've done:

Reserved 60px of space for a cookie banner, set explicit dimensions on all images, and preloaded fonts. CLS dropped from 0.28 to 0.04.

What actually works:

Set width and height on every image. Preload critical fonts. Reserve space for anything that loads dynamically. Test on real devices, not just desktop Chrome.

‍

The Webflow Answered

I recently got a detailed response from Webflow support about CSS performance, and it's worth sharing because it clarifies what's actually in your control.

Their main point:

The primary factor affecting performance is the size of your site and pages, number of DOM elements, assets, styles, interactions, and scripts. A simple page with minimal classes will always load faster than a heavily styled page with lots of assets.Their official recommendations:

• Compress images in Assets and CMS panels
• Limit background videos
• Clean up unused styles and interactions
• Replace background image styles with inline images positioned via object-fit
• Limit linked elements
• Update or remove problematic third-party integrations
• Remove unnecessary transitions/transforms

They also mentioned enabling asynchronous JavaScript loading (new feature, not default) and the recent Per-page JS and CSS updates, which can help but need testing with custom code.

Pingdom as alternative to Google Lighthouse

What I found interesting:

Webflow support acknowledged that PageSpeed and Lighthouse throttle both bandwidth and CPU beyond what most modern devices offer. They recommend testing with multiple tools. When I tested my sites on Pingdomthey got A grades, despite lower PageSpeed scores.

The takeaway:

Performance tools are useful but not the full picture. Real-world performance often differs from lab tests.

Third-Party Scripts Are Usually the Problem

If I had to pick one thing that slows down Webflow sites more than anything else, it's third-party scripts.Live chat widgets. Analytics. Marketing pixels. Social media embeds. Help desk tools. Every single one adds weight.

Webflow itself is fast. What you add to it often isn't.

What actually works:

Load third-party scripts asynchronously or defer them. Use facades for heavy embeds (like YouTube videos). Only load scripts on pages where they're actually needed.

What Doesn't Actually Matter

Here's what I've learned doesn't impact performance as much as people think:

Webflow's hosting:

It's already fast. You won't see big gains moving to Cloudflare or another CDN unless you're doing something very specific.

The number of CMS items:

I've worked on sites with 200+ pages and they're fine. CMS isn't the bottleneck.

Interactions and animations:

Unless you've built something completely absurd, interactions don't slow things down. Modern browsers handle CSS animations and GSAP well.

What to Actually Focus On

If your Webflow site is slow, start here:

1. Check your third-party scripts. Remove or defer anything you don't absolutely need.
2. Audit your cookie consent setup. Is it blocking render? Can you defer it?
3. Compress your images. Every time.
4. Look at what's in GTM. Do you really need all those tags?
5. Test layout shift. Fix images and fonts first.

Performance optimization isn't about doing one big thing. It's about not doing the ten small things that break speed.

Webflow gives you a fast foundation. Don't ruin it with bad scripts and unoptimized assets.