How fast could your site be?

Enter your address. We measure it as it is and through WebSpeed, side by side.

No signup. See your before/after PageSpeed score in about a minute. What the report shows

Speed up Wix — no rebuild, no migration

Your site stays on Wix. A DNS change routes traffic through WebSpeed, which optimizes each page on its way to the visitor — nothing is installed, and the editor keeps working as it does now. That route matters here, because Wix gives you no server, no build step and no access to the markup it emits, which is why most Wix speed advice ends at "use fewer apps". We measured what is actually on the critical path across 361 Wix sites; three things came back on at least 350 of them.

No signup. See your before/after PageSpeed score in about a minute. What the report shows

  • Nothing to install
  • Your site stays where it is
  • Any optimization can be switched off
Screen filled · mobile

How fast 1,134 sites fill the screen

Speed Index of the original sites, as they are, without our optimization.

Fastest quarter: 4.3 s or less

Where does yours land? The free check puts your site on this chart.

Across every platform we’ve measured — not enough Wix sites yet for a chart of their own. Updated 24 Sep 2026.

What WebSpeed does on Wix

Each one is independent and can be switched off for your domain — nothing here is all-or-nothing.

Scripts stop blocking the parse

Blocking scripts are deferred and inline body scripts are held until rendering is done, then run in order. Same behaviour, out of the way of the first paint.

Render-blocking resources TBT FCP

Connections open before they're needed

The origins your page genuinely uses get their DNS, TCP and TLS work started early, so the fetch itself is all that's left when the browser gets there.

TTFB

The first screen gets priority

The largest above-the-fold image is preloaded at high priority; everything below the fold waits until it approaches the viewport.

LCP Lazy loading

Unsized images get their real dimensions

We read each image's true aspect ratio server-side and write it into the markup, so the browser reserves the right box before the file lands and the text stops jumping.

CLS

Embeds load when they come into view

Maps, videos and social embeds stop loading their whole third-party payload with the page and wait until the visitor scrolls near them.

Lazy loading TBT

Your controls

What stays under your control

An optimization you cannot undo is a risk, not a feature. Each of these is a decision you keep after the site is live on WebSpeed.

  • Switch any optimization off

    Each one is independent. If something doesn't suit your Wix theme, it can be disabled for your domain alone and everything else keeps working.

  • Keep only what measurably helps

    On a tuned profile we measure each optimization against your own pages and drop the ones that do not earn their place there.

  • Re-check whenever you want

    Your audit page re-runs both measurements on demand, so "did it help" stays a number you can pull rather than a claim you have to take.

  • Turn it off entirely

    WebSpeed sits in front of your site, not inside it. Revert the DNS record and your original site serves again, unchanged — nothing to uninstall.

In progress: a dashboard where you flip these yourself and follow each page's scores over time. Today it is a message to us and we apply it to your domain.

Why Wix sites are slow

Measured, not assumed — this is what our filter logs recorded across the Wix sites we have audited, ranked by how many of them had something to fix.

Measured across 361 Wix audits · snapshot 2026-10-19

99%of sites

Scripts block the browser while it reads the page

Not a handful of Wix sites — 358 of the 361 we audited had scripts the browser had to stop and run before it could carry on building the page. On a phone, each one is dead time on a screen that is still blank.

97%of sites

Inline scripts run mid-render

Script blocks sitting in the body execute as the browser works through the markup, so drawing stops every time one runs. This is the platform's own runtime and the apps you added, not something you can reorder in the editor.

99%of sites

Connections to other origins open too late

Wix serves your page from one origin and its media, fonts and app code from several others. The browser only discovers those the moment it needs them, then pays for DNS, TCP and TLS before a single useful byte moves.

Real results

Measured on real Wix pages

Stored audits — the original page against the same page served through WebSpeed, on mobile and desktop. Not a demo build: these are the sites as they ship.

Wix puffinpackaging.co.uk
Measured with WebSpeed on
Screen filled · mobile
4.4s
was 5.0 s−0.6 s
Page weight
1.5MB
was 3.5 MB−56%
Mobile · PageSpeed
80
was 64+16
Desktop · PageSpeed
97
was 86+11
Forecast · if your visitors get this speed

Projections, not measurements: this run's measured LCP improvement scaled by published studies, and CO₂ from the measured bytes at ≈0.15 g/MB. Sources under the grid.

Google traffic ≤ +3%CO₂ −56%
25 optimizations applied
  • Deferred parser-blocking scripts
  • Gave unsized images their real aspect-ratio (anti-CLS)
  • Held inline body scripts until after render
  • Preloaded the LCP image (fetchpriority: high)
Wix eterna.com
Measured with WebSpeed on
Screen filled · mobile
2.7s
was 3.2 s−0.5 s
Page weight
1.2MB
was 2.5 MB−52%
Mobile · PageSpeed
76
was 62+14
Main content (LCP) · mobile
5.2s
was 7.2 s−1.9 s
Forecast · if your visitors get this speed

Projections, not measurements: this run's measured LCP improvement scaled by published studies, and CO₂ from the measured bytes at ≈0.15 g/MB. Sources under the grid.

Google traffic ≤ +16%Conversion +10%Bounce −15%CO₂ −52%
19 optimizations applied
  • Deferred parser-blocking scripts
  • Held inline body scripts until after render
  • Lazy-loaded CSS background images
  • Preloaded the LCP image (fetchpriority: high)
Wix cottons-restaurant.co.uk
Measured with WebSpeed on
Screen filled · mobile
3.2s
was 13.9 s−10.7 s
Page weight
1.3MB
was 9.2 MB−86%
Mobile · PageSpeed
68
was 30+38
Desktop · PageSpeed
97
was 47+50
Forecast · if your visitors get this speed

Projections, not measurements: this run's measured LCP improvement scaled by published studies, and CO₂ from the measured bytes at ≈0.15 g/MB. Sources under the grid.

Google traffic ≤ +33%Conversion +7%Bounce −11%CO₂ −86%
14 optimizations applied
  • JavaScript — 11 changes
  • Resource hints — 2 changes
  • Embeds — 1 change

Real Google Lighthouse audits, original vs. WebSpeed Fast. The filled tiles are measured: the score is shown per device only where it moved beyond the ±5 the audit counts as noise, “screen filled” is Speed Index, and page weight is transferred bytes. The outlined pills are projections from those measurements — not guarantees. Scores are per-page; yours will differ.

Google traffic Core Web Vitals are a Google ranking signal; the biggest lift is leaving the “Poor” zone (score < 50), scaled here by device search share.

Conversion Akamai / SOASTA (2017): a 100 ms delay cost 7% of conversions across ~10 billion retail visits; scaled here to the measured improvement.

Bounce Akamai / SOASTA (2017): a two-second delay raised bounce rate by 103%; scaled to the measured improvement, site-specific.

CO₂ The measured byte reduction at ≈0.15 g per MB per visit (Sustainable Web Design v4) — a model of the network and devices, not a measurement of them.

Why it's worth doing

What a faster Wix site is worth

SEO Rank ↑ out of the “Poor” band

Search sees a faster page

Core Web Vitals have been a confirmed Google ranking signal since 2021. The biggest win is leaving the "Poor" band, where faster competitors get preferred.

— Google Search Central
Conversion +7% per 100 ms you cut

More visitors finish what they started

Conversion tracks load time closely — on Akamai’s retail numbers a delay of just 100 ms cost 7% of conversions. Shaving seconds is the cheapest funnel work available.

— Akamai / SOASTA, 2017
Bounce ≈ ½ cutting a 2 s delay

Fewer people leave before it loads

Close a two-second gap and bounce rate roughly halves — Akamai measured those same two seconds raising it by 103%. A page that paints early keeps the visit a slow one loses outright.

— Akamai / SOASTA, 2017
CO₂ ≈ 0.15 g saved per MB you cut

Lighter pages, less energy

Transfer weight maps to emissions at roughly 0.15 g of CO₂ per MB. Cutting bytes is the one optimization that shows up on a sustainability report.

— Sustainable Web Design v4

Each figure links to the page that publishes it. The studies measure what delay costs; read here as what speed returns. Industry benchmarks, not a guarantee for a specific site — the per-site numbers are the audits above, and yours is a free check away.

What 361 Wix audits actually showed

Search for Wix speed advice and you find the same three suggestions: install fewer apps, compress your images, turn on Wix’s own optimizer. That advice exists because it is the only advice a Wix owner can act on — not because it is where the time goes.

We measured instead. Across 361 audited Wix sites, three things were true of at least 350 of them, and none of the three is reachable from the editor.

JavaScript is the story on Wix, not CSS. 358 of the 361 sites we audited shipped scripts that block the parser, and 350 had inline scripts executing while the page was still being drawn. That is a different picture from WordPress, where one of the two most common defects we record is a render-blocking head full of stylesheets. On Wix the stylesheets are comparatively tidy; it is the script work that fills the critical path.

Images are a smaller problem here than elsewhere. Wix serves modern formats from its own CDN, and it shows in our logs: we found images missing dimensions on 29% of the sites, against 96% on Webflow. Where Wix leaves room is not the file format — it is priority and ordering.

Why you can’t fix it from inside the editor

Wix is the most closed platform we audit, and that is usually described as a limitation of support. It is really a limitation of operations.

Speeding up a page is mostly deferring, reordering and dropping things the platform already emits. Those verbs need access to the markup. On Wix you cannot defer a script the runtime injected, reorder tags you did not write, or drop a connection hint that belongs to an app. So every honest Wix speed guide ends in the same place: use fewer apps, and wait for the platform.

A reverse proxy moves where the work happens. Your Wix site keeps serving the page it always did; WebSpeed receives that page, rewrites its critical path, and hands the result to the visitor. Nothing inside Wix changes, so there is nothing for a platform update to undo and nothing for your team to relearn.

Being straight about the range

Wix sites usually start from a better score than sites on most other platforms we measure: a typical Wix original scores higher on mobile than a typical original elsewhere in our base. A faster start leaves less to win, and a minority of Wix sites come out flat.

The platform itself does not hold the result back. Across our Wix audits, the share of sites that come out faster and the size of the typical gain sit in the same range we see on other platforms.

That is exactly why the check is free and takes a minute. You get your own number rather than our average.

What you get from the audit

It needs nothing but the URL:

  1. Your score, both devices — mobile and desktop, original vs the WebSpeed-served page.
  2. The individual metrics — LCP, CLS, TBT and the rest, side by side rather than rolled into one number.
  3. What actually changed — the itemised list of optimizations behind the result.
  4. A before/after video of your page loading, if the gain is big enough to see.

Wix speed — questions

Do I have to move my site off Wix?

No — that is the point. WebSpeed runs in front of your existing site. You keep the editor, the hosting, the apps and your workflow; only what the browser receives changes.

Will the Wix editor still work normally?

Yes. We never touch the site inside the platform. Your team keeps editing in Wix exactly as before, and every publish flows through unchanged.

What about Wix members, the store checkout and site logins?

Member account pages under /account/, the checkout and the calls your site makes to Wix's own API under /_api/ pass through as Wix sends them, never cached and never rewritten. The editor itself runs on wix.com and never reaches us. A visitor carrying a session cookie gets the optimized page, just not a copy from the shared cache.

Does it work with Wix Multilingual?

Yes. Wix Multilingual puts each language in a folder (/es/) or on a subdomain (es.yoursite.com), and each of those addresses is optimized and cached separately. Languages share nothing in our cache, so a visitor never gets a page in a language they did not choose.

Wix says it optimizes performance already. What is left?

Our measurements agree with them on part of it — Wix serves modern image formats and its own CDN, and our image-format work finds less to do here than on self-hosted platforms. What we still measured on nearly every site we audited is the JavaScript on the critical path: scripts that block the parse, and inline scripts that run while the page is drawing. That is what the gains come from.

Do I have to install anything?

No, and on Wix you largely could not: the usual route is the proxy, where traffic is routed through WebSpeed with a DNS change and nothing is installed anywhere.

Will it change how my site looks?

It should not — every optimization here is about when and in what order things load, not about what they are. The audit shows you the before and after so you can check the result yourself before deciding anything.

Pricing

Pick how hands-off you want it

The before/after check is free to run; it isn’t one of these plans. Choose a plan when you’re ready to make the speed-up permanent — or buy the report once and apply it yourself.

SaaS subscription

Growth

from €79 · /mo
For several sites at once
14-day free trial
  • Everything in Fast, across multiple sites
  • Priority cache — your pages stay warm
  • Support with a named contact
  • One invoice for the whole portfolio
Request access
Agencies and multi-site owners.
SaaS + hands-on service

Custom

from €179 · /mo
Hand-tuned for your site
  • Everything in Growth
  • A config built by hand for your site
  • What only you can change, written up for your team
  • Set up, measured and maintained by us
Get a plan for my site
We look at your site by hand first, then keep it tuned. Six months minimum.

Subscriptions start with a 14-day free trial (Fast and Growth). After it, Fast is billed yearly, and Growth and Custom run for a minimum of 6 months — you commit only after the trial. Fast is priced by monthly visits; indicative launch pricing.

Downloadable report

Not ready for a subscription?

Buy the Audit once and apply it yourself — the same findings the pipeline acts on, written up as instructions.

  • One site, up to 5 pages you choose
  • Fast’s changes to your page code, written up as a guide you run yourself
  • Server settings, code changes and ready-to-paste head snippets
  • Before/after PageSpeed from the free check (PDF / HTML / MD)
  • Re-issued free for a year as your site changes
€149 · one-time
DIY: you apply it
Get the audit See an example report →
Not useful? Email us within 14 days and we refund it. A document, not a service — you apply it; Custom is the same work done for you.

See your own before / after

Paste your URL for a free PageSpeed comparison on mobile and desktop. No signup, about a minute.

No signup. See your before/after PageSpeed score in about a minute. What the report shows

Other platforms: WordPress Duda WooCommerce Divi Tilda Bitrix Squarespace