Skip to content
Tutorials Center
My learning

Topics

Lesson 31 of 37 ยท SEO and Performance

Performance, Images and Core Web Vitals

Make Wix and Webflow sites faster: Core Web Vitals (LCP, INP, CLS), image formats and sizes, lazy loading, fonts, scripts and video, with runnable budget calculators.

Speed affects conversions, search visibility and plain good manners. Slow pages lose visitors, and many of them are on phones with imperfect connections. Both Wix and Webflow host your site on a fast global network and apply many optimizations automatically, but the biggest wins are still in your hands: the images you upload, the fonts and scripts you add, and the effects you stack.

Neither platform can run on this site. Speed numbers below are guidelines and tools change, so test your own published site. The calculators are stand-ins for explanation.

Core Web Vitals in plain words

Google's Core Web Vitals measure real user experience:

Metric What it measures Good target
LCP (Largest Contentful Paint) How fast the main content (often the hero image or headline) appears 2.5 seconds or less
INP (Interaction to Next Paint) How quickly the page responds to taps and clicks 200 ms or less
CLS (Cumulative Layout Shift) How much content jumps around while loading 0.1 or less

Measure with PageSpeed Insights, Lighthouse in Chrome DevTools and the Core Web Vitals report in Search Console. Field data (real users) matters more than a single lab test. Run tests on the published site, not in the editor.

Images: the biggest lever

Images are usually most of a page's bytes.

  1. Right size. Do not upload a 6000-pixel photo for a 800-pixel slot. Resize before upload to around twice the largest display width (for sharp high-density screens) and no more.
  2. Right format. WebP and AVIF are much smaller than JPEG or PNG at similar quality. Webflow converts uploaded images to responsive sizes and can serve WebP (with an option to convert in the asset settings), and Wix serves optimized formats automatically for images in its media manager. Use SVG for logos and icons.
  3. Compress. Quality 70โ€“85 is usually indistinguishable for photos.
  4. Responsive images. Both platforms generate different sizes for different screens (srcset); you choose the displayed size in the editor, so set it properly.
  5. Lazy loading. Images below the fold load only when needed. Webflow images are lazy by default (with a setting for loading: lazy, eager or auto), and Wix lazy-loads media. Do not lazy-load the hero image: it is usually the LCP element, so mark it eager (Webflow's Loading: Eager setting).
  6. Set dimensions. Fixed width and height (or aspect ratio) reserve space and prevent layout shift (CLS).

Use the next stand-in to estimate how much an image strategy saves.

JS Stand-in: page weight estimate

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Fonts

Custom fonts are files the browser must fetch before it can show text in them.

  • Use two families at most, and few weights (regular and bold).
  • Prefer the platform's built-in font library (Webflow's Google Fonts integration and uploaded fonts; Wix's font list), and use WOFF2 files if you upload your own.
  • Show fallback text immediately (font-display: swap), so words are never invisible. Webflow lets you add custom CSS for this; check what the platform already sets.
  • Use system fonts for body text if speed is the main goal.

Scripts and apps

Every tracking script, chat widget and app adds JavaScript that competes with your own content for the phone's processor. This hurts INP and LCP.

  • Audit your scripts: do you need all of them?
  • Load heavy widgets (chat, maps) on interaction or after the page settles.
  • Remove apps you no longer use, since removed apps may still leave code behind in some cases; check the page source or a speed test afterwards.
  • Embeds such as YouTube iframes are heavy: use a click-to-load facade (a thumbnail image that loads the player on click), which many embed tools support.

Video and animation

Autoplaying background video can add megabytes. If you use it: keep it short (5โ€“10 seconds), muted, compressed, with a poster image, and consider turning it off on mobile. Heavy scroll interactions and big blurred shadows also cost frames (see Easing and Motion Performance).

Layout shift fixes

  • Give images and embeds explicit dimensions.
  • Avoid inserting banners above content after load.
  • Reserve space for ads, cookie notices and late-loading widgets.
  • Do not animate layout properties.

A budget checker

A performance budget is a limit you agree on before building, for instance "pages under 1.5 MB, hero image under 150 KB". This stand-in checks a page report against a budget.

JS Stand-in: budget check

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Hosting and caching

You do not tune servers on these platforms: Webflow serves sites through a global CDN, and Wix serves through its own global network with caching and compression, with features such as HTTPS and HTTP/2 or later on by default. Your job is the front end. Publish, then test; changes are cached, so wait a moment and re-test in a private window.

Mobile first

Test on a mid-range phone on a throttled connection. Check the first screen: is the headline visible, is the main image loaded, can you tap the menu without delay? Fix mobile first, because desktop will follow.

Common mistakes

  • Uploading original camera files.
  • Lazy loading the hero.
  • Stacking multiple analytics and chat scripts.
  • Autoplaying video with sound-less loops of 30 MB.
  • Optimizing the editor preview rather than the published page.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What does LCP measure?

    Largest Contentful Paint is the time until the main content is rendered.
  2. 2. Which image should NOT be lazy-loaded?

    The hero is usually the LCP element and should load immediately.
  3. 3. Which format typically gives smaller files than JPEG at similar quality?

    WebP and AVIF compress more efficiently than JPEG for photos.
  4. 4. How do you reduce layout shift from images?

    Reserved space prevents content from jumping when the image loads.

Summary

  • Aim for LCP under 2.5 s, INP under 200 ms and CLS under 0.1, measured on the published site.
  • Resize, compress and convert images; lazy-load below the fold, keep the hero eager.
  • Limit fonts, scripts, apps and video; each one has a cost.
  • Reserve space to prevent layout shift and set a performance budget.

Next: Domains, DNS and SSL