Insights · Nov 13, 2026 · 4 min read · FAQ

Webflow site speed: fix images, scripts, interactions and CMS lists

Background images, site-wide scripts, leftover interactions and long CMS lists are what usually slow a Webflow page. The setting or habit that fixes each one.

WEBFLOW SPEEDFixes for slow Webflow pages SELLWRIGHT

When a Webflow page loads slowly, hosting is rarely the reason. Webflow's own performance guide says most problems on a published site come from what is on the page, and each cause has a setting or habit that fixes it. Fonts, video and general animation have their own Insights; this one covers what is specific to Webflow.

How do you find what is slowing a Webflow page?

Test the published page on its real domain, not the Designer or a preview link. PageSpeed Insights gives a Lighthouse lab result, for finding causes, and field data from real Chrome users over the previous 28 days. You can also run Lighthouse in Chrome DevTools in an incognito window, so extensions don't distort it, and take the median of two or three runs.

Then open Site settings, Site usage. The dashboard puts a warning next to assets worth fixing:

  • Images over 2,000 pixels on either side, or not yet in WebP or AVIF.
  • GIFs over 1 MB, which it suggests replacing with video.
  • JavaScript or CSS bundles over 250 KB.

Which images does Webflow handle, and which are left to you?

Webflow handles image elements and leaves the rest to you. For uploads through the Assets panel or a CMS image field, it creates smaller variants and adds srcset and sizes, so phones get smaller files. Background images, images in rich text, and images added by CSV import or the API get no variants.

  • Use an image element for the hero. web.dev also lists a CSS background image as a reason the browser finds the main image late.
  • Where a background image is right, upload it at display size and add smaller variants at the tablet and phone breakpoints.
  • Convert JPG and PNG files to WebP or AVIF: expand the Assets panel, select the images, choose a format and click Compress. For CMS images, use Compress assets in the Collections panel. Then republish.
  • Set each image's loading Type: Eager for the hero, Lazy below the fold. Our lazy loading guide explains which images can wait.

Conversion replaces the original file and can't be reversed in Webflow, so download the originals first. Check Open Graph images separately: Webflow warns AVIF isn't widely supported for them.

Which custom code loads on every page?

Everything in Site settings, Custom code. Page settings load code on one page, and a code embed runs only where you place it. A booking widget used on one page belongs in that page's Before </body> tag box, so other pages never download it.

Add defer to scripts that need the page or another script, and async to independent ones such as an analytics pixel. Newly published Webflow sites already include jQuery, and Webflow warns another version can cause conflicts, so don't add a second copy.

Which publishing settings make a difference?

Minification, Per page CSS and asynchronous JavaScript, all under Site settings, Publishing, Advanced publishing options. Change one, publish and test again.

  • Minify HTML, CSS and JS. On new sites, HTML and JS are on by default and CSS is off, so switch CSS on too.
  • Per page CSS, which splits the site-wide stylesheet into a shared file plus one per page. Delete unused classes first in the Style selectors panel, then test custom CSS. Webflow advises keeping it off on sites using a shared Library.
  • Asynchronously load JavaScript, if your plan includes it, which loads Webflow's scripts while the page renders. Custom code that relies on Webflow's JavaScript may then fail.

The fix is defer on external scripts and a load event handler around inline code, because MDN notes defer has no effect on a script without a src.

<!-- Page settings, Custom code, Before </body> tag -->
<script src="https://widget.example.com/booking.js" defer></script>
<script>
  window.addEventListener('load', function () {
    // code that relies on Webflow's own JavaScript
  });
</script>

Are interactions or Lottie animations slowing the page?

They can, through the code they add and the content they hide during loading:

  • Use one interactions system. Webflow says each version loads its own resources, and ranks Interactions with GSAP alone first for performance, then Classic alone, then both.
  • Deleting a Classic animation or trigger doesn't fully remove it, so run the clean-up option in the Interactions panel.
  • Keep the hero out of entrance effects. Interactions with GSAP hides elements that animate from a starting state until Webflow's JavaScript is ready, and web.dev says an element only counts for Largest Contentful Paint once rendered and visible.
  • Set transitions on specific properties, not all, and animate moves, scales and fades rather than width or height, as Webflow recommends.
  • Webflow plays every Lottie animation as the page loads by default, so one further down plays out unseen. Start it with a Scroll into view trigger.

How many CMS items should one page show?

Only as many as the visitor needs. Webflow caps each Collection list at 100 items to help pages load faster, and its pagination guide suggests fewer per page for the same reason. A page can hold 40 Collection lists, including up to 10 nested lists, three levels deep. Treat those as ceilings, not targets.

  • Use Limit items for short selections, such as three related posts.
  • Paginate long lists.

Where to start

Run your homepage and two busiest templates through PageSpeed Insights and note the results. Then work through dashboard warnings, images, scripts, publishing settings, interactions and CMS lists, testing after each change. We built the John Deere dealer network on one Webflow system, and our Webflow development service can work through this list with you, or start with a website review.

FAQ

Frequently asked questions

Does Webflow hosting make our site slow?

Rarely. Webflow says every hosted site gets the same foundation: a global CDN, responsive image variants and per page JavaScript. It puts score differences between Webflow sites down mostly to content, meaning images, fonts, scripts and styles. If the site is slow only for you, Webflow suggests loading it through a VPN or asking someone elsewhere to try, to rule out your network.

What size images should we upload to Webflow?

About twice the largest width the image displays at, which covers high-resolution screens. Each upload must be under 4 MB. For image elements, Webflow creates up to seven smaller versions, from 500 to 3,200 pixels wide, and uses your original when it is already compressed enough. Background images get no versions, so size those exactly.

Why do our blog post images load at full size on phones?

Check whether they sit in a rich text field. Webflow doesn't create responsive versions for images in rich text, or for images added by CSV import or the API, so phones download each file as uploaded. Resize and compress those images before they go into the CMS, and check the largest posts first.

Will turning on Asynchronously load JavaScript break our custom code?

It can, if your code relies on Webflow's own JavaScript being ready. Webflow's fix is the defer attribute on external scripts and a window load event handler around inline code. Test the published site after switching it on. If something still fails, Webflow suggests switching the setting off and republishing while a developer fixes the code.

Can a Webflow page show more than 100 CMS items?

Yes, in two ways. Pagination splits a list across pages of up to 100 items each. Or duplicate the list and set Skip to 100 on the copy, so it shows items 101 to 200; each copy counts toward the limit of 40 lists per page. Webflow's site search only indexes the first page of a paginated list.

Does a good Webflow health scan score mean the site is fast?

No. The scan checks settings such as minification, Per page CSS and asynchronous JavaScript, and flags sites with more than 1,000 classes or 10 web fonts. Webflow says a better score isn't guaranteed to improve performance, because factors such as page size, images and custom code aren't included. Test your main pages in PageSpeed Insights too.

Next step

Ready for a website that sells?

Book a short call. We will look at your current site, agree what matters most and send a written scope with a fixed quote.

Book a callOr write to hello@sellwrightstudio.com