Why your Wix site scores 50 on Lighthouse.

If you run a small business with a Wix site, open it in Chrome, hit F12, switch to the Lighthouse tab, and run a test. Pick mobile. Click “Analyze page load.”

In a sample of 50 Wix small-business sites measured on 2026-08-27, the median Performance score was 68, and about a quarter scored 60 or below. Our own site measured 92 the same day.

That number isn’t a Wix conspiracy or a personal failure. It’s the math of how page-builder platforms work. The good news: now that you know why, you can decide whether it’s worth doing anything about it.

The actual problem

When you build a site on Wix, you’re not writing HTML. You’re telling Wix’s editor what you want, and Wix is generating the HTML for you. But Wix doesn’t generate your HTML in isolation. It generates the HTML on top of a giant runtime that includes:

• The Wix Editor engine. Renders all the drag-drop primitives, even on pages that don’t use them.
• Element libraries for every widget type Wix supports - carousels, galleries, contact forms, booking widgets, e-commerce primitives - loaded whether your page uses them or not.
• Animation and interaction libraries. Loaded eagerly so the live editor can show drag-drop previews.
• Tracking, analytics, and ad-pixel scripts. Some are Wix’s own. Some are added by apps you installed (Wix Bookings, Wix Email, Wix Forms, etc.).
• Wix's editor and app runtime, which ships with the page whether or not you use most of what it offers.

The result: your homepage downloads about 4-6 MB of code, fonts, scripts, and assets before a visitor sees anything useful. On a desktop with a fast connection, that’s ~2 seconds. On a phone with a 4G connection in a parking lot, that’s ~6-9 seconds.

Lighthouse measures “Largest Contentful Paint,” “Total Blocking Time,” “Cumulative Layout Shift” - metrics that all suffer when you ship 5 MB of framework. Hence the median of 68 we measured, against 92 for our own site.

Why this matters for Google rankings

Google documents Core Web Vitals as part of page experience, and says its systems aim to reward pages that deliver a good one. Google is also explicit that page experience does not outrank genuinely useful content, so speed is a tiebreaker, not a shortcut.

Translation: when Google decides which of three plumbers in Edmond shows up first on a phone, page speed is one of the factors. Two plumbers might be equally licensed, equally reviewed, equally close. If one’s site loads in 1.5 seconds and the other’s loads in 6, Google quietly nudges the fast one up.

This effect is strongest on mobile, which is where most local-business searches happen. Your customers Googling “HVAC repair near me” aren’t on a desktop with fiber. They’re on a phone with 1 bar standing next to a broken AC unit. Speed isn’t a luxury - it’s the difference between you and the next guy.

How fast can a hand-coded site be?

Our own site measured 92 on mobile and 99 on desktop for Lighthouse Performance on 2026-08-27, and 100 on SEO, accessibility and best practices, for one simple reason: we ship a fraction of the code. There’s no editor framework. No widget libraries you’re not using. No drag-drop runtime. Just the HTML, the CSS, and one small JavaScript file for the parts that actually need it.

It’s the same approach a developer would have used to build a website in 2005, before page-builder platforms existed. The web hasn’t changed - only what people pay for hosting has.

What you can do about it (if you’re on Wix today)

Three honest options. We’ll tell you which we’d pick.

Option 1: Stay on Wix and accept the ceiling

You can squeeze a few points out of Wix by removing apps you don’t use, and compressing photos. You can move the number some, but you can’t get to 90+ on Wix because the framework itself is the bottleneck.

If your local SERP isn’t competitive (you’re a niche service, or you serve a small town with few competitors), this might be fine. Don’t spend $1,000 on a new site if your phone is already ringing.

Option 2: Hire a Wix consultant to optimize

$50-$150/hour. They’ll trim unused apps, compress images, simplify your homepage layout. You might gain 10-15 Lighthouse points. You’re still on Wix. You’ll still pay their monthly subscription. The ceiling moves up but it doesn’t go away.

Option 3: Switch to a hand-coded site

Hire a developer (us or anyone else) to rebuild your site in clean HTML. You keep your domain, your content, your photos. You lose the Wix subscription. You gain a Lighthouse score in the 90s and the page-speed ranking signal that goes with it.

The math depends on how long you keep the site. Year 1, it’s a wash (build cost vs. cancelled subscription). Year 2 onward, you’re ahead by $400-$1,200 a year because Wix’s monthly stack adds up faster than people realize. We did the full year-by-year math in our Wix switching guide.

How to verify any of this yourself

You don’t have to take our word for it. Try this in the next 5 minutes:

1. Open your Wix site in Chrome.
2. Press F12 to open DevTools.
3. Click the Lighthouse tab.
4. Pick Mobile, leave the categories on default, click Analyze page load.
5. Wait 30 seconds. Look at the Performance number.

Then do the same test on a hand-coded site - ours, or any small-business site you suspect was built by a developer instead of a page builder. The difference is rarely subtle.

You can also test from outside Chrome at pagespeed.web.dev - same engine, no install needed.

- Dominic