How do I run a Wix site speed test?

Pick a real product URL (not only the homepage), test mobile and desktop, record LCP, CLS, and interaction delay metrics, then change one variable and retest the same URL.

Which tool should I use?

Use PageSpeed Insights or Lighthouse-style lab data plus Wix site performance checks. Speed Booster also stores PSI-style metrics in its dashboard after install. Confirm live App Market details.

Why is my homepage fast but product pages slow?

Product templates often load review widgets, chat buttons, galleries, and apps the homepage does not. Always test money pages.

Does Speed Booster replace a speed test?

No. Measure first. Speed Booster - Load Faster helps after cleanup when third-party scripts still delay early load.

What Core Web Vitals should I watch?

Largest Contentful Paint, Cumulative Layout Shift, and Interaction to Next Paint (or TBT in lab tools). See web.dev Core Web Vitals.

Can I publish invented before/after scores?

No. Only publish numbers from your own tests on the same URL and conditions.

Where do I go next if the store is slow?

Read /blog/why-is-my-wix-store-slow/ and /blog/speed-up-wix-website/.

Wix Site Speed Test (Practical Process)

A useful Wix site speed test measures the product and checkout-adjacent URLs customers actually use, on mobile first, with Core Web Vitals recorded before you change anything. Homepage vanity scores hide the real problem.

If you already know the store feels slow and need causes, jump to why is my Wix store slow. For cleanup order after the test, see how to speed up a Wix website / improve LCP.

What to test first

One top-selling product URL
One category or collection URL if it is a major entry point
The homepage only as a secondary check
Mobile profile before desktop
Same URL before and after every change

Tip

Write down the URL, device profile, date, and tool. Without that, before/after comparisons are noise.

Which URLs to measure

Apps and media load differently by template. Review widgets, chat launchers, image galleries, and upsell scripts often sit on product pages only. Test those pages even if the homepage looks fine.

Hero product with reviews and chat enabled
A product with large gallery images
Any landing URL you buy ads for
Avoid editor preview URLs and unpublished drafts

Metrics that matter

Metric	What it tells you	Common Wix store cause
LCP	When the main content appears	Huge hero/product images, late fonts, blocked render
CLS	Visual jumpiness	Late-loading widgets, banners, fonts
INP / TBT (lab)	Interaction delay / main-thread busy work	Stacked third-party scripts
FCP / Speed Index	Early paint / visual completeness	Heavy above-the-fold media and CSS

Canonical overview: web.dev Core Web Vitals. Do not invent thresholds for marketing claims. Track your own URLs over time.

Tools and Wix checks

PageSpeed Insights or Chrome Lighthouse for lab data on a public URL
Wix site performance checks in the editor or dashboard: Wix performance article
Field data (CrUX) when available for real-user signals
After install, Speed Booster dashboard stores performance score, FCP, LCP, CLS, TBT, and speed index for desktop and mobile

Lab tools are noisy. Run the same URL at least twice and look for patterns, not a single lucky score.

How to read the report

Separate media problems from script problems.

If LCP is dominated by a large image: compress, resize, remove autoplay video backgrounds
If third-party scripts and unused JavaScript dominate: trim apps first
If CLS spikes when chat or review widgets appear: fix placement and reserved space, reduce late injections
If the homepage is fine but product URLs fail: audit product-template apps only

Important

A green homepage score does not clear a red product page. Always keep the money URL in the notebook.

Fix order after the test

Remove unused App Market apps and abandoned pixels.
Keep one reviews app and one chat path. See best Wix apps.
Compress product images and strip decorative motion that does not sell.
Retest the same product URL.
If third-party scripts still delay early load, consider Speed Booster - Load Faster.

Where Speed Booster fits

Speed Booster - Load Faster injects a domain-locked header script. It defers non-whitelisted third-party scripts from early load and restores them after a short delay or on first user interaction (mousemove, click, scroll, and similar). Non-whitelisted stylesheets use a deferred media swap. Preconnect hints target common Wix and Google Fonts hosts.

Dashboard PageSpeed-style analysis with stored FCP, LCP, CLS, TBT, speed index
Bypass query params for debugging
Listing context at last publish: from about US$3.30 per month; 4.0 from 15 reviews. Confirm live: Speed Booster listing

It will not fix apps you refuse to remove or images you refuse to compress. Use it after cleanup, not instead of cleanup.

Install Speed Booster - Load Faster

Defer heavy third-party scripts after you measure and clean.

Open App Market

Retest protocol

Change one thing (remove one app, compress one gallery, enable Speed Booster).
Wait for publish/propagation.
Retest the same product URL on mobile.
Record LCP, CLS, and interaction metric side by side.
Keep the change only if the metric moves in the right direction without breaking widgets.

Speed-test mistakes

Testing only the homepage
Comparing desktop today to mobile last week
Installing three new widgets, then blaming Wix
Publishing invented before/after claims
Using Speed Booster as permission to keep every abandoned app

When not to chase a score

Conversion is already healthy and Core Web Vitals are acceptable on money pages
You have not finished image cleanup
You are about to redesign templates next week (measure after the redesign)
The real leak is offer, shipping, or trust, not milliseconds

Lab data vs field data

Lab tools (Lighthouse, PageSpeed lab section) simulate a visit. Field data (CrUX when available) shows what real users experienced. Use lab data to debug changes quickly. Use field data to decide if customers still feel the problem after a week of traffic. Do not panic over one noisy lab run.

Lab: good for before/after on the same URL the same day
Field: good for confirming mobile users still struggle after publish
If lab improves but field does not, check that you tested the URL people actually visit

Spotting third-party script delay

When the report calls out third-party code, unused JavaScript, or long main-thread tasks, list every App Market app and every pixel. Remove abandoned tools first. Keep one reviews app and one chat path. If delay remains, Speed Booster can defer non-whitelisted scripts until interaction. That is a second-stage fix, not a license to keep junk installs.

Also separate first-party media problems: a huge product gallery image is not a third-party script issue. Compress it. Retest. Then look at scripts again.

Copy-paste test checklist

Write down product URL, tool, date, and device profile
Record LCP, CLS, and INP or TBT
Note the top opportunities in the report
Make one change only
Retest the same URL and keep the change only if metrics improve without breaking widgets

After the notebook is honest, follow causes in why is my Wix store slow and cleanup in speed up Wix website. Wix help: checking your site performance.

Speed tests for ad landing URLs

If you buy traffic, the speed test URL should be the same URL in the ad. Collection pages, discounted product templates, and seasonal landing pages often carry extra apps and banners the homepage does not. Measure those. A fast brand homepage with a slow offer page still burns spend.

Save a PSI or Lighthouse report PDF or screenshot with the URL visible
Compare mobile LCP before a campaign launch and after each widget change mid-campaign
If you add Proofy, chat, or pixels during a campaign, retest within a day
Do not chase a perfect score while creative and offer tests are unfinished; fix only clear LCP/CLS/script problems

Marketing stack context: best Wix marketing apps. Cleanup order: speed up Wix website.

Wix Site Speed Test: How to Measure What Actually Matters