Wix site speed optimisation: a step-by-step Core Web Vitals guide

Site speed is a confirmed ranking factor. Google's Page Experience update made this explicit, and the Core Web Vitals metrics are now part of the ranking algorithm. For Wix sites, speed optimisation requires understanding what Wix controls automatically, what you can control, and what requires creative workarounds. Many Wix users assume speed is entirely in the platform's hands, but in reality 60-70% of speed issues on Wix sites are caused by user choices: oversized images, excessive apps, heavy animations, and unoptimised third-party scripts. This lesson gives you complete control over every speed lever available on Wix.

Understanding Core Web Vitals

Core Web Vitals are three specific metrics Google uses to evaluate page experience. Each measures a different aspect of how users experience your page.

• LCP (Largest Contentful Paint): measures loading performance. How quickly does the main content become visible? Target: under 2.5 seconds.
• INP (Interaction to Next Paint): measures interactivity. How quickly does the page respond when a user clicks or taps? Target: under 200 milliseconds.
• CLS (Cumulative Layout Shift): measures visual stability. Do elements jump around as the page loads? Target: under 0.1.

Running Your Speed Audit

Complete speed audit process

• Go to pagespeed.web.dev and enter your Wix site URL.
• Run the test on both Mobile and Desktop tabs.
• Note your Core Web Vitals scores: LCP, INP, CLS for both mobile and desktop.
• Scroll to "Opportunities" for specific actionable fixes ranked by estimated impact.
• Check "Diagnostics" for additional technical insights.
• Open Google Search Console > Experience > Core Web Vitals for real-world field data.
• In GSC, check which URLs are failing and which metrics they fail on.
• Test your top 5 pages individually, not just the homepage.
• Record all scores in a spreadsheet as your baseline before making changes.

What Wix Controls Automatically

Wix handles several speed optimisations automatically that you do not need to worry about:

• CDN delivery: Wix serves all sites from a global Content Delivery Network.
• HTTP/2: all Wix sites use HTTP/2 for faster resource loading.
• SSL/TLS: HTTPS is automatic and free on all Wix sites.
• Image format conversion: Wix automatically serves images in WebP format to supported browsers.
• Code minification: Wix minifies JavaScript and CSS automatically.
• Server-side rendering: Wix renders pages server-side for faster initial load.
• Automatic lazy loading: images below the fold are lazy-loaded by default.

Fixing LCP (Largest Contentful Paint)

LCP is usually the most impactful metric to fix on Wix sites. The largest element in the viewport (typically your hero image or hero video) determines the LCP score.

Hero Image Optimisation

Optimising your hero image for LCP

• Identify your hero image: the largest visible element above the fold on each page.
• Compress the hero image to under 200KB before uploading. Use squoosh.app or TinyPNG.
• Use WebP format for the hero image. Convert from JPEG/PNG using squoosh.app.
• Set dimensions to match the display size. A 4000px wide image displayed at 1200px wastes bandwidth.
• In the Wix Editor, select the hero image and set loading to "Eager" (not lazy). This ensures it loads immediately.
• Remove any filters, overlays, or effects applied to the hero image in the Wix Editor, as these add rendering time.
• Consider using a solid colour background or gradient instead of an image if the page purpose allows it.

Video Background Issues

Video backgrounds are the number one LCP killer on Wix sites. A video background forces the browser to download megabytes of video before the page appears loaded.

• Replace video backgrounds with a high-quality static image. The visual impact difference is minimal; the speed difference is massive.
• If you must keep a video, replace it with a static image on mobile using the Wix Mobile Editor.
• Use short loops (5-10 seconds max) at 720p resolution, not 1080p or 4K.
• Host videos externally (YouTube or Vimeo) and embed them below the fold to avoid blocking LCP.

Font Optimisation for LCP

• Reduce the number of web fonts. Every font weight is a separate HTTP request.
• Use 2-3 font weights maximum across your entire site.
• Prefer Wix system fonts (Arial, Helvetica, Georgia) which load instantly.
• If using Google Fonts, use font-display: swap to prevent invisible text during loading.
• Avoid decorative fonts in large hero text sections.

Fixing CLS (Cumulative Layout Shift)

CLS measures visual stability. When elements jump around as a page loads, it creates a frustrating experience and Google penalises it.

Common CLS Causes on Wix

• Images without explicit dimensions: as images load, surrounding content shifts to accommodate them.
• Ads or embedded content loading asynchronously and pushing content down.
• Web fonts loading late and causing text to reflow (FOIT/FOUT).
• Dynamic content injected above existing content (cookie banners, chat widgets).
• Wix lightbox/popup elements that trigger on page load.

CLS Fixes for Wix

Eliminating layout shifts

• Set explicit dimensions for all images in the Wix Editor. Click the image and verify width/height are set.
• Avoid using sticky elements that appear after page load (cookie banners should load with the page, not after).
• Use Wix's built-in section heights rather than auto-height containers where possible.
• Position chat widgets in the bottom-right corner where they do not push content.
• Avoid inserting content above the fold dynamically. If you need a banner, reserve space for it.
• Test with Chrome DevTools Performance panel: enable "Layout Shift Regions" to see exactly what shifts.

Fixing INP (Interaction to Next Paint)

INP measures how quickly your page responds to user interactions. High INP scores are usually caused by excessive JavaScript execution blocking the main thread.

Reducing INP on Wix

• Remove unused Wix apps. Go to your Wix Dashboard > Apps and uninstall anything not actively used.
• Every Wix app adds JavaScript that runs on page load, even if the app's features are not visible on the current page.
• Delay loading of non-critical third-party scripts (chat, analytics, heatmaps) using async loading in Wix Custom Code.
• Reduce the number of animations on the page. Complex parallax and scroll animations are INP killers.
• Check the Wix App Market for apps marked as "may affect performance" and remove if not essential.
• Simplify hover effects and interactive elements that require heavy JavaScript.
• Avoid using multiple lightbox/popup elements on a single page.

The Wix App Performance Audit

Wix apps are the single biggest controllable factor in site speed. Each app adds JavaScript, CSS, and sometimes iframes that increase page weight and execution time.

Auditing your Wix apps

• Go to your Wix Dashboard > Apps and list every installed app.
• For each app, ask: is this app actively used on the live site?
• Remove any app that is not actively used. Even "inactive" apps can load JavaScript.
• For remaining apps, check if Wix provides a lighter alternative.
• Test page speed before and after removing each app to measure its impact.
• Consider replacing heavy third-party apps with lighter custom code solutions where possible.

Image Optimisation Beyond the Hero

Comprehensive image optimisation for Wix

• Audit every image on your site. Are any over 500KB? Compress them.
• Use WebP format for all images. Wix auto-converts, but uploading WebP ensures the smallest file size.
• Set images below the fold to lazy loading (Wix does this automatically for most images).
• Use responsive image sizes: upload images at the maximum display size, not larger.
• For decorative images (backgrounds, textures), compress aggressively. Quality loss is barely noticeable.
• Remove unnecessary images. Every image is an HTTP request.

Third-Party Script Management

Third-party scripts (Google Analytics, Facebook Pixel, chat widgets, heatmaps) can significantly impact speed.

• Audit all scripts in Wix Custom Code. List every script added to Head, Body Start, and Body End.
• Move non-critical scripts from Head to Body End to prevent render blocking.
• Add async or defer attributes to script tags where possible.
• Remove tracking scripts you no longer use (old analytics, expired marketing tags).
• Consolidate tracking through Google Tag Manager rather than individual scripts.
• Load chat widgets only after user interaction (click to load) rather than on page load.

Mobile Speed Optimisation

Mobile speed is typically worse than desktop due to slower processors and network conditions. Since Google uses mobile-first indexing, your mobile speed is what matters for rankings.

• Switch to the Wix Mobile Editor and simplify layouts for mobile.
• Hide heavy visual elements on mobile that are not essential (decorative images, complex animations).
• Reduce the number of sections visible above the fold on mobile.
• Use system fonts on mobile for faster text rendering.
• Test on real mobile devices, not just Wix's mobile preview or Chrome DevTools.
• Consider using AMP-style simplicity on mobile even without AMP: minimal elements, fast-loading images, simple layouts.

Speed Monitoring and Maintenance

Ongoing speed maintenance

• Set a monthly calendar reminder to check Core Web Vitals in GSC.
• After any site change (new app, design update, content addition), re-test speed.
• Track speed scores over time in a spreadsheet to catch gradual regressions.
• Set up Google PageSpeed Insights alerts using third-party monitoring tools.
• When Wix releases platform updates, re-test your speed as improvements may be automatic.

What PageSpeed Score to Aim For

• Desktop: aim for 90+ on PageSpeed Insights. Most Wix sites can achieve this.
• Mobile: aim for 70+ on PageSpeed Insights. Wix mobile scores are typically lower due to platform overhead.
• Field data (GSC): all three CWV metrics should be green (Good) for the majority of URLs.
• Perfection is not required. A score of 75 mobile with green field data is fine for rankings.
• Focus on field data over lab scores. Lab data is a guide; field data is what Google uses.