Why your Wix site is slow, and how to fix it

A slow site loses visitors before they read a word, and page speed is one of the signals Google uses for ranking. Wix handles hosting and much of the setup for you, but a few common choices can still make a site slow. Here’s where to look, roughly in order of impact.

1. Measure first#

Before changing anything, get a baseline:

• Run your key pages through PageSpeed Insights, on mobile, since that’s where most sites are slowest.
• Note the Largest Contentful Paint (how long the main content takes to appear) and Interaction to Next Paint (how quickly the page responds to taps).
• In your Wix dashboard, check the site speed report for real-visitor data if your site has enough traffic.

Measure the same pages again after each change, so you know what actually helped.

2. Images#

Images are the most common cause of slow pages.

• Don’t upload huge originals. A 6000-pixel photo shown at 1200 pixels wide still has to be processed. Resize large photos before uploading.
• Avoid full-screen background videos and slideshows at the top of the page, especially on mobile. A single strong image usually works better.
• Use fewer images above the fold. Everything visible on the first screen competes to load first.

3. Apps and embeds#

Every app, chat widget, tracking script and embedded social feed adds code that the browser has to download and run.

• Open Apps in your dashboard and remove anything you no longer use.
• Replace embedded social feeds with a simple link to your profile.
• Check custom code under Settings → Custom Code and remove old tracking scripts.

4. Fonts and page length#

• Stick to two fonts, each in only the weights you use. Each extra font is another file to download.
• Split very long pages. A home page with fifteen sections loads more than one with six focused ones. Move detail to its own pages and link to it.

5. Velo code that delays the page#

Custom code can slow things down if it waits for data before showing anything. A common pattern:

// Slow: each query waits for the previous one
$w.onReady(async () => {
  const products = await wixData.query("Products").find();
  const reviews = await wixData.query("Reviews").find();
  const faqs = await wixData.query("FAQ").find();
  // ...fill the page
});

Better: run independent queries at the same time, and limit what you load.

// Faster: queries run in parallel, and only what's needed is loaded
$w.onReady(async () => {
  const [products, reviews] = await Promise.all([
    wixData.query("Products").limit(12).find(),
    wixData.query("Reviews").limit(5).find(),
  ]);
  // ...fill the page
});

Other Velo habits that help:

• Don’t load what isn’t visible. Load content for tabs, popups or sections below the fold when the visitor opens or scrolls to them.
• Use .limit() on queries and add a “Load more” button rather than loading a whole collection.
• Move heavy work to the backend and return only the fields the page needs.

6. Check the mobile version separately#

Wix lets you hide elements on mobile, but hidden elements are often still loaded. If the mobile version is cluttered, simplify the layout rather than hiding large parts of it.

When to get help#

If your site is still slow after these steps, the cause is usually specific: a heavy app, a large dynamic page, or custom code that needs restructuring.

I build fast Wix sites and fix slow ones as part of Wix website design and Wix Velo development.