The Invisible Tax on Every Wix, Squarespace, and WordPress.com Website

I spend a lot of time looking at source code. Partly because I enjoy it, honestly, but mostly because when a business owner tells me their website "feels slow" or "isn't getting leads," the source code usually tells me why in the first 30 seconds.

I keep finding the same thing: hundreds of kilobytes of JavaScript, CSS and tracking scripts that the business owner never asked for, didn't know existed, and can't control.

This is the invisible tax of using a website builder, and it's behind most of the website builder performance problems I see. You pay your $16 to $49 per month, pick a nice template, and add your logo and photos. Everything looks fine on your laptop. Behind the scenes, though, your site is shipping a bloated package of platform code to every visitor on every page load.

Here's what that looks like.

What your visitors are actually downloading

When someone visits your Wix site on their phone, here is what happens before they see a single word of your content:

1. The browser downloads Wix's core runtime framework (this is the code that makes the drag-and-drop editor work, even though your visitor is not editing anything)
2. It loads scripts for every Wix feature that might exist on any page of your site, including ones you are not using
3. It pulls in tracking and analytics code for Wix's own purposes
4. It downloads render-blocking CSS for layout systems your page does not use
5. Then, finally, it starts loading your actual content

The HTTP Archive's 2024 Web Almanac measured the median web page at 570 KB of JavaScript on mobile. That is the median across all websites. Wix and Squarespace sites routinely exceed that by 40 to 60 percent. A simple five-page business site on Wix can easily ship 800 KB to over 1 MB of JavaScript before a single customer photo loads.

For context, this entire blog post is about 12 KB.

Why should a business owner care about kilobytes?

Fair question. Nobody walks into a plumber's office and asks about JavaScript payload sizes, but people do notice when a website takes forever to load on their phone. The data on what happens next is brutal.

Sites that load in under 2 seconds have a bounce rate around 9 percent. Once you cross 3 seconds, that bounce rate jumps to 53 percent, which means more than half your visitors leave before they see your phone number.

PortioLabs and Landbase both published conversion data in 2025 showing that sites loading in 1 second convert at roughly 3 times the rate of sites that take 5 seconds. For a service business getting 500 visitors a month, that is the difference between 15 leads and 5 leads. That's ten potential customers a month lost to code nobody asked for.

The numbers behind the curtain

Google's Core Web Vitals Technology Report tracks how websites built on different platforms perform in the real world using Chrome user data. The platform numbers are worth a look.

As of late 2025, only 52 percent of Wix sites achieved "good" Core Web Vitals scores. That means nearly half of all Wix websites fail Google's own performance standards.

Squarespace does a bit better, but DebugBear's 2025 Website Builder Performance Review measured a typical Squarespace site at a Lighthouse performance score of 72 on mobile. That sounds okay until you see that a well-built custom site routinely scores 90 to 98.

Why the gap? Business owners can't fix any of the following, however carefully they optimize and compress their photos:

Platform overhead. Every Wix site loads the same core framework whether you have a one-page site or a 200-page e-commerce store. Squarespace does the same. You can't remove it or slim it down, so you pay for the entire platform toolkit on every page load.

Plugin and app bloat. Add a contact form app on Wix and you are adding its entire JavaScript bundle, even on pages where the form does not appear. The same goes for a gallery or a booking widget. Each one injects its own scripts globally.

Render-blocking resources. Both Wix and Squarespace inject CSS and JavaScript that blocks the browser from rendering anything until those files finish downloading. On a slow mobile connection (which is most of rural Michigan and plenty of suburban Texas), this can add 2 to 4 seconds of dead time where the visitor stares at a blank screen.

The part nobody talks about: you cannot fix it

This is what makes the website builder performance problem different from an ordinary "my site is slow" problem.

If you built a custom site and it was slow, a developer could open the code, find the bottleneck, and fix it: remove an unused library, defer a script, lazy-load an image. The code is yours to change.

On Wix, Squarespace, or WordPress.com (the hosted version, not self-hosted WordPress.org), you do not control the underlying code. Wix's own support documentation acknowledges this. Their help article on reducing unused JavaScript literally says that some flagged files "may come from third-party code" that users cannot remove.

You are renting a platform, and the platform decides what code ships. If their framework is heavy, your site is heavy, and there's nothing you can do about it.

A developer on Reddit put it bluntly when someone asked for help with their Wix Lighthouse scores: "Your top flags are for things you can't control using Wix. Literally. Reducing unused JavaScript, removing duplicate modules, unused CSS, these are all things that come bundled with using Wix."

When a website builder is actually fine

I won't tell you that every small business needs a $10,000 custom website, because it isn't true.

A website builder works fine when:

• Your business gets most of its customers through referrals or word of mouth, and the website is basically a digital business card
• You are testing a business idea and need something up in a weekend
• Your competitors are equally slow (nobody has an advantage)
• You do not depend on organic search traffic for leads

If your website exists to confirm that you are a real business when someone Googles your name, Squarespace is perfectly adequate for that.

When the invisible tax starts hurting

The math changes when your website is supposed to generate leads. If you are a contractor, a medical practice, a restaurant, a law firm, or any service business that needs people to call, fill out a form, or book an appointment, your website's speed directly affects your revenue.

I run into this scenario constantly. A roofing company in Grand Rapids is spending $1,500 a month on Google Ads. Those ads send people to their Wix website. The site takes 4.5 seconds to load on mobile. Fifty-three percent of visitors bounce before the page finishes loading.

That roofing company is burning $795 a month in ad spend on visitors who never see the website. The ads may be fine and the site may look good. The platform code just took too long to deliver the content.

A custom site loading in under 2 seconds would keep those visitors on the page. Even a modest improvement from 53 percent bounce to 20 percent bounce means an additional 165 visitors per month actually seeing the site. At a 3 percent conversion rate, that is 5 more leads per month. For a roofing company, that could be $25,000 to $50,000 in additional annual revenue.

That's what the invisible code costs.

What the alternative actually looks like

A hand-coded or custom-built website does not have to be a six-month, $50,000 enterprise project. For a small business, a well-built custom site typically means:

• Only the code your site actually needs ships to the browser
• Pages load in 1 to 2 seconds on mobile instead of 4 to 6
• Lighthouse performance scores of 90 to 98 instead of 50 to 72
• Full control over every script and stylesheet
• No platform overhead eating your visitors' bandwidth

Modern frameworks like Astro and Next.js can produce a five-page business site that ships under 100 KB of JavaScript total. Compare that to the 800 KB or more that a comparable Wix site ships. That's an 8x reduction in code weight.

Every person who visits your site feels a difference that size.

How to check your own site

You do not need to hire anyone to see this for yourself. Open Google's PageSpeed Insights (pagespeed.web.dev), type in your URL, and look at two things:

1. Performance score on mobile. If it is below 70, your site has a code weight problem.
2. The "Reduce unused JavaScript" and "Reduce unused CSS" sections. These tell you exactly how much dead code is shipping. On a website builder site, these sections will be full of files you have never heard of.

If you see file names with "wix" or "static.parastorage" or "squarespace" in them, those are platform files you cannot remove. That is the invisible tax.

The bottom line

Website builders are convenient, and they solve a real problem for people who need a site quickly and cheaply. They also come with a cost that doesn't appear on any invoice: the invisible code that ships to every visitor on every page load.

If your website is a brochure that confirms you exist, that cost does not matter much. If your website is supposed to bring in customers, that invisible tax is eating into your leads, ad spend and search rankings every day.

Start by measuring it. Run your site through PageSpeed Insights and look at what is actually loading. If the results bother you, that is worth a conversation about what a purpose-built site could do for your business.

Check your website's performance score and see what your visitors are actually downloading.