Site speed is not optional for eCommerce. Google has confirmed that Core Web Vitals are ranking signals, and for online stores the impact is even more direct: every 100ms of additional load time reduces conversion rates by approximately 1.1%. When you have a large product catalogue on Wix with hundreds of images, dynamic pricing, and third-party integrations, maintaining fast page speeds requires deliberate, ongoing optimisation. This lesson covers the specific speed challenges that eCommerce stores face, practical solutions that work within Wix's platform constraints, and a systematic approach to monitoring and maintaining performance over time as your catalogue grows.
The Three Core Web Vitals and Their eCommerce Impact
Largest Contentful Paint (LCP)
LCP measures how long it takes for the largest visible element to render on screen, typically a hero image or product image on eCommerce pages. Google requires LCP under 2.5 seconds for a "Good" rating. On product pages, the LCP element is usually the primary product image. On category pages, it is often the banner image or the first product thumbnail. Slow LCP directly increases bounce rates as shoppers leave before the page finishes loading.
Interaction to Next Paint (INP)
INP measures how quickly the page responds to user interactions like tapping buttons, selecting variants, or applying filters. Google requires INP under 200ms for a "Good" rating. On eCommerce pages, INP is often degraded by heavy JavaScript from third-party apps, variant selectors, and dynamic pricing widgets. A slow INP makes the shopping experience feel sluggish and directly reduces conversion rates.
Cumulative Layout Shift (CLS)
CLS measures unexpected layout movement as the page loads. Google requires CLS under 0.1 for a "Good" rating. On eCommerce pages, CLS is commonly caused by images loading without reserved dimensions, review widgets injecting content late, cookie consent banners pushing content down, and recommendation carousels appearing after the initial render. CLS frustrates shoppers and can cause misclicks.
Image Optimisation at Scale: The Biggest eCommerce Speed Win
Images are the single largest contributor to page weight on eCommerce sites. A typical product page with six product images, a lifestyle banner, and trust badge graphics can easily exceed 3MB if images are not properly optimised. Multiply that across a category page showing 24 products, and you are asking the browser to load 50 or more images simultaneously. Even with Wix's automatic WebP conversion and responsive image serving, your upload quality is the baseline that determines everything.
Batch image optimisation process for large catalogues
- 1Audit your current product images: check the file sizes by downloading a sample (anything over 300KB per image needs compression)
- 2Choose a batch compression tool: Squoosh for individual images, ShortPixel or TinyPNG for bulk processing
- 3Set maximum dimensions: 2000px on the longest side for product images, 1400px for banners and hero images
- 4Target file sizes: under 150KB for product images, under 200KB for hero images, under 50KB for icons and badges
- 5Convert to WebP format before uploading when possible (Wix will convert to WebP on delivery, but starting with WebP gives the best baseline)
- 6Re-upload optimised images to replace the originals in your Wix Media Manager
- 7Verify the improvement by running PageSpeed Insights on a sample product page and category page
Wix Image Delivery Pipeline
Wix serves images through its own CDN and automatically generates multiple sizes for different viewport widths. However, the source image you upload determines the maximum quality. If you upload a 5000x5000px image at 2MB, Wix will create responsive versions but may still serve a larger-than-necessary file to desktop users. Always upload images pre-sized to 2000px maximum and pre-compressed to ensure the fastest delivery across all devices.
Lazy Loading: Essential for Category Pages with Many Products
Lazy loading defers the loading of images that are not visible in the viewport until the user scrolls to them. For a category page displaying 48 products, this means only the first 8-12 product images load initially, dramatically reducing initial page load time. Wix has built-in lazy loading for images and galleries, but you need to verify it is working correctly and understand its interaction with your specific page layout.
The critical consideration with lazy loading is the Largest Contentful Paint (LCP) element. Your above-the-fold hero image or first visible product image should never be lazy-loaded because it needs to render as quickly as possible for a good LCP score. Wix generally handles this correctly by eager-loading the first visible images, but if you have customised your page layout extensively, verify that your LCP element is not accidentally lazy-loaded using the Chrome DevTools Performance panel.
Do not install third-party Wix apps that claim to add lazy loading. Wix handles lazy loading natively, and layering an additional lazy loading implementation on top of Wix's built-in system can cause images to fail to load entirely, create layout shift issues, or conflict with Wix's rendering pipeline. Stick with the platform's native implementation.
Speed-Killing Apps and Scripts to Audit
Third-party Wix apps are the second largest cause of slow eCommerce page speeds after images. Every app you install from the Wix App Market adds JavaScript to your pages. Chat widgets, pop-up builders, analytics trackers, social media feeds, and review platforms all inject code that the browser must download, parse, and execute. Each one adds latency, and their cumulative effect can be devastating.
- Live chat widgets (Tidio, Intercom, LiveChat) typically add 200-400KB of JavaScript and frequently cause CLS issues
- Pop-up and banner builders add render-blocking scripts that delay LCP
- Social media feed embeds (Instagram, Facebook) load external resources that are outside your control and often slow
- Analytics scripts beyond Google Analytics (Hotjar, Crazy Egg, Facebook Pixel, multiple ad trackers) compound JavaScript execution time
- Review platforms that load dynamically (Yotpo, Judge.me) can delay INP if they inject content into the DOM after page load
- Abandoned cart apps that add exit-intent pop-ups often trigger layout shifts and increase INP
App Audit and Removal Process
How to audit and reduce app-related speed impact
- 1Open your Wix Dashboard and go to Apps > Manage Apps to see all installed apps
- 2List every app and categorise them as essential, useful, or dispensable
- 3Remove all dispensable apps immediately; every removed app improves speed
- 4For essential apps, test whether they offer a "load on interaction" option (e.g., chat widgets that only load when clicked)
- 5Run PageSpeed Insights before and after removing each app to measure the specific impact
- 6Check if any functionality provided by an app could be achieved natively in Wix without the app
- 7Consider replacing heavy third-party review apps with Wix's built-in product reviews feature
CLS Issues on Dynamic eCommerce Pages
Cumulative Layout Shift is particularly problematic on eCommerce pages because of the dynamic elements that load at different times: product image galleries, variant selectors, price updates, stock availability badges, review widgets, and recommendation carousels. Each of these can cause the layout to shift as it loads, pushing content around and frustrating users.
- Cookie consent banners that push content down: set them as overlay modals rather than inline banners
- Review stars that load after main content: reserve space with a minimum-height container
- Product image galleries that resize as images load: set explicit width and height attributes
- Recommendation sections that inject content above the fold: move them below the fold or reserve space
- Late-loading fonts causing text reflow: use font-display: swap and preload critical fonts
- Promotional banners that appear after page load: use static banners or reserve space for dynamic ones
Quick CLS Fix
In the Wix Editor, ensure that every image element has explicit width and height values set rather than using "auto" sizing. For dynamic sections like review widgets, set a minimum height in the section properties that matches the typical rendered height of the content. This reserves space in the layout before the content loads, eliminating the shift.
Monitoring eCommerce Core Web Vitals Over Time
Speed optimisation is not a one-time task. Every new product you add, every app you install, and every design change you make can affect Core Web Vitals. Establish a monitoring routine that catches regressions before they impact rankings and conversions. Google Search Console's Core Web Vitals report is the primary monitoring tool because it uses real user data rather than lab simulations.
- Check Google Search Console Core Web Vitals report weekly for any pages that have moved from "Good" to "Needs Improvement" or "Poor"
- Run PageSpeed Insights on your homepage, top category page, and a sample product page at least monthly
- After installing any new Wix app, immediately test speed on affected page types and compare to pre-installation benchmarks
- Use the Web Vitals Chrome extension during development to catch issues before publishing changes
- Set up a Google Looker Studio dashboard that pulls Core Web Vitals data from Search Console for trend tracking
- Pay special attention to mobile speed scores as the majority of eCommerce browsing happens on mobile devices
Complete How-To Guide: Optimising Your Wix Store Speed for Core Web Vitals
This guide walks you through a systematic speed optimisation process for your Wix eCommerce store, covering image compression, app auditing, CLS prevention, and ongoing monitoring to maintain passing Core Web Vitals scores.
How to optimise your Wix Store for fast page speeds and passing Core Web Vitals
- 1Step 1: Run your homepage, top category page, and highest-traffic product page through Google PageSpeed Insights. Record the LCP, INP, and CLS scores for both mobile and desktop. These are your baseline measurements. Create a spreadsheet to track these numbers over time.
- 2Step 2: Check Google Search Console Core Web Vitals report for field data. Navigate to Experience > Core Web Vitals and review both mobile and desktop reports. This shows how real visitors experience your store and is more important than lab scores.
- 3Step 3: Address image optimisation first as it typically has the biggest impact. Download a sample of 10 product images and check their file sizes. Any image over 300KB needs compression. Use Squoosh to compress each image to under 150KB while maintaining visual quality.
- 4Step 4: Batch-process all product images. If you have more than 50 products, use ShortPixel or TinyPNG for bulk compression. Upload images at maximum 2000px on the longest side in WebP format. Re-upload compressed versions to replace originals in Wix Media Manager.
- 5Step 5: Audit all installed Wix Apps by going to Dashboard > Apps > Manage Apps. List every app with its purpose and whether it is essential, useful, or dispensable. Remove all dispensable apps immediately.
- 6Step 6: Run PageSpeed Insights on your product page after removing each dispensable app. Record the score improvement from each removal. This data helps you make informed decisions about which "useful" apps are worth their speed cost.
- 7Step 7: For essential apps (chat widgets, analytics), check if they offer deferred loading options. Configure chat widgets to load only when the user clicks to open them. Move non-critical analytics scripts to load in the footer after page render.
- 8Step 8: Fix CLS issues on product pages. In the Wix Editor, select every image element and set explicit width and height. For dynamic sections like review widgets, set a minimum height matching typical rendered content. For cookie banners, switch to overlay modal style.
- 9Step 9: Optimise above-the-fold content on category pages. Ensure the hero banner and first row of product images are compressed and appropriately sized. Move heavy elements like video embeds, testimonial carousels, and recommendation widgets below the fold.
- 10Step 10: Reduce the number of products displayed in collection page grids on initial load. Showing 12-16 products with a "Load More" button is faster than displaying 48 products at once. Configure this in the Wix Store product gallery settings.
- 11Step 11: Test on a real mobile device, not just Chrome DevTools. Load your store on an actual phone using a standard mobile connection. Time how long it takes from tapping a search result to seeing the first product image. If it exceeds 3 seconds, continue optimising.
- 12Step 12: Minimise the use of animations and video on product and category pages. Autoplay video backgrounds, complex scroll animations, and animated product galleries increase LCP and INP. Reserve heavy animations for the homepage where visual impact justifies the speed cost.
- 13Step 13: Re-test all three page types (homepage, category, product) in PageSpeed Insights after making all changes. Compare with your baseline scores. You should see measurable improvement in all three Core Web Vitals metrics.
- 14Step 14: Set a monthly calendar reminder to re-check Core Web Vitals in Search Console and re-run PageSpeed Insights. New products, images, and app installations can degrade speed over time if not monitored.
- 15Step 15: After making all speed improvements, request re-indexing of your key pages in Google Search Console. Google re-evaluates Core Web Vitals on re-crawl, and improved scores can lead to ranking improvements within 2-4 weeks as Google processes the updated performance data.
Speed Priority
Focus your speed optimisation on product and category pages first, not the homepage. These are the pages that rank in Google for commercial keywords and directly generate revenue. A fast product page converts better than a fast homepage.
