Why your Webflow site is slow, and how to fix it
To speed up a Webflow site, you don't need a caching plugin or a better host: Webflow already provides the CDN, SSL and code minification. Performance comes down to five levers you control: images (format, size, lazy loading), interactions and animations, fonts, custom code and third-party scripts, and a handful of publishing settings that are switched off by default. Measure your Core Web Vitals on real visitors first, then fix things in that order.
Webflow has a strong reputation for performance, and it is partly deserved: the generated code is clean and the infrastructure is managed for you. Yet many Webflow sites still post disappointing mobile PageSpeed scores. The culprit is almost always the same mix: a multi-megabyte background image in the hero, scroll animations on every section, three font families and a growing stack of marketing scripts.
This guide is for startups, marketing teams and store owners who run their marketing site, CMS or Webflow Ecommerce store on Webflow. It shows where to look, which settings to turn on and which fixes deliver the biggest gains.
Why Webflow site speed matters
Speed has a direct commercial impact. The Milliseconds Make Millions study (Deloitte for Google), covering 37 European and US brand sites, found that a 0.1-second improvement in mobile speed was associated with an 8.4% increase in conversions for retail sites.
For SEO, Google states in its Core Web Vitals documentation that these metrics are used by its ranking systems. They won't replace relevant content, but a slow site starts at a disadvantage, especially on paid landing pages and product pages.
LCP ≤ 2.5 s
When the largest visible element renders: usually the hero image or main product photo.
INP ≤ 200 ms
Responsiveness to taps and clicks: mobile menu, tabs, add to cart, forms.
CLS ≤ 0.1
Visual stability: no content jumping around as fonts and widgets load.
These thresholds are defined by Google on web.dev and assessed at the 75th percentile of real page loads.
What Webflow already optimizes for you
Unlike WordPress, there is no server to tune and no caching plugin to pick. Webflow explains on its engineering blog that sites hosted since April 21, 2025 use its Cloudflare-based CDN, which serves more than 98% of static assets from the network edge. CMS pages are generated statically and new images are lazy-loaded by default.
The takeaway: on Webflow, just like on Shopify (see our guide on how to speed up a Shopify store), performance problems come from what you build on top of the platform, not from the hosting.
Step 1: Measure with real-user data
Start with PageSpeed Insights on your key templates: homepage, a service or landing page, a CMS article template and, if you sell online, a category page and a product page. Read the real-user section (from Chrome's CrUX data) first, then use the Lighthouse diagnostics to identify the LCP element and the heaviest scripts.
In Google Search Console, the Core Web Vitals report groups failing URLs by similarity. On a Webflow site, those groups usually map to a Collection template: if every item built on the same template fails, fix the template once instead of chasing individual pages.
Step 2: Turn on the right publishing settings
Several performance options are off by default. You'll find them under Site settings > Publishing > Advanced publishing options, as described in Webflow's help center.
| Setting | What it does | Watch out for |
|---|---|---|
| Minify HTML, CSS, JS | Reduces the size of generated files | No real downside: enable it on every site |
| Asynchronously load JavaScript | Loads JavaScript in parallel with page rendering | Requires a paid plan; custom code that relies on Webflow's JavaScript may break |
| Per page CSS | Serves a shared global CSS file plus a page-specific one instead of one large stylesheet | Can break custom CSS or shared Library elements: test before publishing |
For async loading, Webflow recommends adding defer to external custom scripts and wrapping inline JavaScript in a window load event handler. Enable these options on staging first, test forms, navigation and sliders, then publish.
Step 3: Fix LCP with your images
On most Webflow sites, the LCP element is the hero image or a product's main photo. Three fixes cover the majority of cases.
Convert images to WebP or AVIF
The built-in image conversion tool in the Assets panel converts existing JPEG and PNG files to AVIF or WebP, including every image in a CMS Collection. Note that originals are replaced, so back them up first. For Open Graph images, choose WebP, as AVIF is poorly supported by social platforms.
Never lazy-load the hero image
Webflow sets new images to lazy load by default. That's great below the fold but counterproductive for the main image. In the image settings, switch loading to Eager for the hero, the logo and the main product photo.
Replace background images with image elements
As Webflow points out, lazy loading and responsive images don't apply to CSS background images, so a background-image hero ships at full size to every phone. Replace it with an Image element using object-fit: cover: same look, with srcset and responsive variants.
One catch for catalog imports: images added via CSV import or the API don't automatically get responsive variants, according to Webflow's integrations documentation. If your products were imported, check the actual weight of the images being served. Our guide to product image optimization covers formats, dimensions and target file sizes.
Step 4: Keep interactions and animations under control
Interactions are Webflow's signature feature, and one of the most common reasons for a poor INP. Since summer 2025, Webflow offers Interactions with GSAP alongside Classic Interactions. According to Webflow's help center, each version loads its own resources; from best to worst expected performance: GSAP only, Classic only, then both combined.
- Pick one engine: on an existing site, migrate to GSAP gradually rather than running both long-term.
- Scope interactions to pages: Webflow added page scoping in 2025, so an interaction only loads on the pages that use it.
- Remove unused interactions, which often come bundled with templates.
- Go lighter on mobile: disable parallax and complex scroll animations on small screens, and use CSS transitions for simple hover effects.
- Respect reduced motion: Interactions with GSAP support prefers-reduced-motion, which also helps accessibility.
Step 5: Fonts, custom code and third-party scripts
Fonts
Stick to two families and only the weights you actually use. Webflow lets you set font-display: swap, but only for custom fonts, not for fonts added through the Google Fonts or Adobe Fonts integrations, as the fonts documentation explains. Upload your fonts as WOFF2 and, if a custom font shares its name with a Google Font, rename it so it isn't still loaded from Google's servers.
Custom code and marketing scripts
Code added in site settings or Embed blocks runs alongside Webflow's own JavaScript. Take inventory: tag manager, ad pixels, live chat, heatmaps, cookie banner, review widgets. Remove tags from finished campaigns, add defer to non-critical scripts, and load chat widgets or embedded videos on first interaction rather than on page load. Reserve space for injected widgets to avoid layout shifts.
Step 6: CMS, Collections and Webflow Ecommerce
Collection pages and CMS lists can get heavy fast: a grid of 100 posts or products loads 100 images and just as many elements. Enable pagination on Collection Lists, cap the number of items shown and avoid stacking several nested lists on one page.
For a Webflow Ecommerce store, focus on the product page: main image set to Eager, gallery lazy-loaded, a responsive variant selector and a cart free of unnecessary scripts. The platform's constraints are covered in our guide to Webflow Ecommerce features, limitations and pricing.
Which fixes should you prioritize?
| Symptom | Likely cause | Priority fix | Effort |
|---|---|---|---|
| Slow LCP on the homepage | Background-image hero or lazy-loaded main image | Image element set to Eager, converted to WebP or AVIF | Low |
| High INP on mobile | Scroll interactions, Classic and GSAP both loaded, third-party scripts | One engine, page scoping, deferred scripts | Medium |
| CLS on text | Google Fonts without swap, injected widgets | Custom WOFF2 fonts with swap, reserved space | Low |
| Heavy CMS pages | Unpaginated lists, imported images without variants | Pagination, converting Collection assets | Medium |
| Render-blocking code | Publishing options left off | Minification, async JavaScript, per page CSS | Low to medium |
Example: a SaaS startup site before a paid campaign
Illustrative scenario: a SaaS startup runs its marketing site on Webflow and is about to launch a Google Ads campaign. PageSpeed Insights shows a mobile LCP above 4 seconds on the landing page and an INP in the orange.
- The audit uncovers a 2.8 MB PNG background image in the hero and 14 scroll interactions inherited from the template.
- The hero is rebuilt as an Image element set to Eager and converted to AVIF; the Open Graph image is switched to WebP.
- Unused interactions are deleted, parallax effects are disabled on mobile and the site moves fully to Interactions with GSAP.
- The heading font, previously loaded from Google Fonts, is uploaded as WOFF2 with
font-display: swap. - Minification, async JavaScript and per page CSS are enabled after testing on staging, and the team tracks real-user data over the next 28 days.
Speed work pairs naturally with search optimization: our Webflow SEO guide covers meta tags, sitemaps, redirects and structured data.
Webflow speed checklist
- Core Web Vitals measured per template in PageSpeed Insights and Search Console.
- HTML, CSS and JS minification enabled.
- Async JavaScript and per page CSS tested, then enabled.
- Images converted to WebP or AVIF, Open Graph images in WebP.
- LCP image set to Eager, no background image for the hero.
- One interactions engine, page scoping and lighter effects on mobile.
- Two font families maximum, WOFF2 with swap.
- Third-party scripts audited, deferred or loaded on interaction.
- Collection Lists paginated, imported images checked.
Conclusion: a fast Webflow site is built, not bought
Webflow gives you a fast foundation, but every background image, animation and script you add can erode it. Measure with real users, switch on the publishing settings, fix the LCP image and keep interactions and scripts disciplined, and most Webflow sites can pass Core Web Vitals without a full redesign. Every tenth of a second you save benefits user experience, rankings and conversion rate alike.
Is your Webflow site or store too slow?
Agence Web Tunis designs, optimizes and redesigns Webflow, WordPress, WooCommerce and Shopify sites for businesses in Europe and North Africa: Core Web Vitals audits, interaction and script clean-up, image and CMS optimization. See how we speed up slow websites and explore our SEO services, or simply send us your site's URL.