Core Web Vitals for Wix

What real Wix sites measure

We measured Wix’s own homepage and a well-known Wix commerce site (The Spice Suite, featured by Wix itself) with Lighthouse 13, mobile emulation, in July 2026. wix.com scored 41/100 with LCP at 6.8 s and TBT of 1,750 ms; thespicesuite.com scored 40/100 with LCP at 6.0 s, TBT 1,268 ms, and CLS 0.03. Note what is and is not in those numbers: layout shift is near zero on both — Wix’s renderer reserves space properly — and blocking time, while real, is not catastrophic. The metric that fails is LCP, and on both pages the largest element is rich hero media arriving behind the platform runtime. That is exactly the lever this guide focuses on: you cannot slim Wix’s runtime, but the hero that renders after it is entirely your choice.

What Wix already does for you

Start by not re-fixing what the platform fixed. Wix serves every site over its own global CDN with Brotli compression and HTTP/2+, converts uploaded images to WebP or AVIF automatically, generates responsive image variants per breakpoint, lazy-loads below-the-fold media, and server-renders the first viewport so the page paints before the JavaScript bundle finishes. None of that needs a setting — it is the default for every site on the current editor.

The practical consequence: generic advice like “enable a CDN” or “convert images to WebP” is already done, and Lighthouse findings about Wix’s own runtime bundle are not actionable. Your entire influence is the content layer — what you put on the page, how heavy it is, and what third-party code you invite in. That is where the rest of this guide lives.

Media: the uploads are yours

Wix optimizes what you give it, but garbage in still degrades out: a 6000px camera original gets resized, yet the largest generated variant is bigger and the processing less predictable than a clean 2500px upload. Pre-size photos to roughly their largest display size before uploading, and prefer photographs over PNG exports of designs — PNGs of photographic content are several times larger for identical quality.

The bigger media decision is video. A full-bleed autoplaying video background above the fold is the single most expensive thing you can do on Wix: it competes with everything for bandwidth exactly when the LCP image needs it, and on slow connections visitors watch a blurry poster stall. If the brand needs motion, keep the hero static and put video further down the page — or use a short, aggressively compressed clip and accept the cost knowingly.

Animations, apps, and repeaters

Entrance animations are the signature Wix performance mistake. Elements set to fade, float, or fly in are hidden until their animation runs — if that element is your headline or hero image, you have voluntarily delayed your own LCP and added layout movement. Keep the first viewport static; animate below the fold if you must.

Every Wix App Market widget embeds either an iframe or a script bundle. Chat, bookings, Instagram feeds, and review widgets each add requests and main-thread work to every page they sit on — keep the homepage lean and give heavy widgets dedicated pages. Velo custom code runs after the page becomes interactive, so prefer it over pasted third-party embed snippets when either would work. Finally, repeaters bound to large datasets generate enormous DOMs; paginate or “load more” after a dozen items rather than rendering hundreds of cards into one page.

The Wix settings that matter for SEO

Wix gives you real control where it counts: per-page titles and meta descriptions in the SEO panel, canonical URLs, structured-data markup per page (SEO settings → Advanced → Structured data), a URL Redirect Manager for anything you re-slug, and automatic sitemap.xml and robots.txt with editable rules. The defaults are sensible, but the structured-data field is empty until you fill it — pasting valid JSON-LD for your organization and key pages is a five-minute win most Wix owners skip.

One editor-specific trap: hiding an element for mobile in the editor hides it visually but can still load its assets. For genuinely different mobile and desktop experiences, keep the mobile layout minimal rather than stacking hidden desktop elements. And check your mobile view deliberately — Wix layouts are edited desktop-first, and unreviewed mobile auto-layouts are where stray elements and clipped sections accumulate.

Measuring Wix correctly

Wix has a built-in Site Speed dashboard (under Analytics & Reports) that shows your real Chrome UX Report field data — the same 28-day field metrics Google actually evaluates. Start there rather than with a single lab run: it tells you whether you have a problem and on which device class before you start diagnosing.

When you do run lab tests, test the published site, not the editor preview — preview URLs carry editor scaffolding and are dramatically slower. Test your homepage and your highest-traffic content page separately, since app widgets differ per page. And after removing an animation or a widget, re-run the lab test immediately for the mechanical confirmation, then watch the Site Speed dashboard over the following weeks for the field data to catch up.