Page speed warning

Moderate effort

Found on 76% of audited stores.

Reduce your page load time to under 1.5 seconds by optimizing images, eliminating render-blocking resources, and enabling caching and compression.

What it is

Page load time is how long it takes for a visitor's browser to fully display your store page after they click a link or type your URL. When a page takes more than 1.5–2 seconds to load, visitors experience a noticeable delay before they can see and interact with your content. A load time of 3 seconds or more (like the example finding) is considered slow by both Google and modern shoppers. Page speed is measured by several signals — the most important being Google's Core Web Vitals, which assess how fast your content appears, how quickly it becomes interactive, and how stable the layout is as it loads.

Why it matters

Google has officially made page speed and Core Web Vitals a direct ranking factor for all pages. Slow pages rank lower in search results, meaning fewer people find your store organically — costing you traffic and revenue before a visitor even arrives. For shoppers who do visit, studies consistently show that every additional second of load time reduces conversions: a 3-second page loses a significant portion of mobile shoppers to bounce before they see a single product. Slow stores also perform poorly in Google's mobile-first index, which evaluates your mobile experience first when deciding your rankings. Fixing page speed is one of the highest-ROI improvements an ecommerce store can make — it simultaneously boosts your SEO rankings, increases conversion rates, and improves accessibility for users on slower connections or lower-end devices.

How to fix it

  1. Audit your current speed using Google PageSpeed Insights (pagespeed.web.dev) or Google Search Console's Core Web Vitals report to identify your specific bottlenecks — look for the Opportunities and Diagnostics sections.
  2. Compress and convert all images to modern formats (WebP or AVIF), resize them to their actual display dimensions, and add lazy loading to images that appear below the fold (not visible immediately on page load).
  3. Enable server-side compression (Gzip or Brotli) and browser caching / CDN delivery so returning visitors and users in different regions receive assets faster.
  4. Remove or defer render-blocking JavaScript and CSS — scripts that are not needed for the initial page view should load asynchronously or after the main content, so the browser can paint the page faster.
  5. Reduce the number of HTTP requests by combining small CSS/JS files, removing unused third-party scripts (live chat widgets, analytics pixels, social embeds) you no longer need, and using system fonts or self-hosted fonts instead of multiple web font requests.
  6. Re-run PageSpeed Insights and Google Search Console's Core Web Vitals report after each change to verify improvement, aiming for a Largest Contentful Paint (LCP) under 2.5 s, Interaction to Next Paint (INP) under 200 ms, and Cumulative Layout Shift (CLS) under 0.1.

Fix it on your platform

Pick your platform for the exact steps.

How to fix page speed warning on Shopify
  1. Images: In the Shopify admin go to Content > Files and re-upload key images as WebP before adding them to your theme. In your theme's Liquid templates use the built-in image_url filter with 'width' and 'format: 'webp'' parameters so Shopify's CDN serves correctly sized, modern-format images automatically.
  2. Theme speed: Go to Online Store > Themes > Customize, and in the theme settings disable any built-in features you do not use (e.g. predictive search animations, sticky header effects, video autoplay) — each one loads extra JS/CSS.
  3. Apps: In the Shopify admin go to Apps and uninstall any app you are not actively using — every installed app injects its own JavaScript into every storefront page even when idle.
  4. Scripts: In Online Store > Themes > Edit code, open theme.liquid and move non-critical <script> tags to load with defer or async attributes, and place them just before </body> rather than in <head>.
  5. Speed app: Install a reputable performance app such as 'Booster: Page Speed Optimizer' from the Shopify App Store for automated script deferral and image lazy loading without code edits.
  6. Fonts: In your theme settings, choose a system font stack instead of a Google Font, or self-host the font files and add font-display: swap to reduce layout shift.
Full Shopify guide →Official Shopify docs ↗
How to fix page speed warning on WooCommerce
  1. Caching plugin: In your WordPress admin go to Plugins > Add New and install WP Rocket (paid) or W3 Total Cache (free). Enable page caching, browser caching, Gzip compression, and CSS/JS minification from the plugin's settings dashboard.
  2. Image optimization: Install the Imagify or ShortPixel plugin (Plugins > Add New) to bulk-convert all existing images to WebP and automatically optimize future uploads; enable lazy loading for below-the-fold images.
  3. CDN: In your caching plugin's settings (or via Cloudflare — add your site at cloudflare.com for free), enable a CDN so static assets (images, CSS, JS) are served from edge servers closer to each visitor.
  4. Hosting: If you are on shared hosting, consider upgrading to a managed WordPress host (e.g. Kinsta, WP Engine, Cloudways) — server response time (TTFB) is the single biggest WooCommerce bottleneck and is fixed at the hosting layer.
  5. Plugins: Go to Plugins > Installed Plugins and deactivate then delete any plugin you do not use. Each active plugin may load JS/CSS on every page.
  6. Database: Install WP-Optimize (Plugins > Add New) and run the database cleanup to remove expired transients, post revisions, and spam comments, which speeds up database queries on large product catalogues.
Full WooCommerce guide →Official WooCommerce docs ↗
How to fix page speed warning on BigCommerce
  1. Stencil theme: In your BigCommerce admin go to Storefront > My Themes and ensure you are on a Stencil-based theme (not Blueprint) — Stencil themes are optimized for Core Web Vitals and support modern asset pipelines.
  2. Images: In the BigCommerce admin go to Products and re-upload product images at their correct display resolution. BigCommerce automatically serves images via Akamai CDN; use the ?imbypass=on URL parameter to verify CDN delivery is active.
  3. Script manager: Go to Storefront > Script Manager and remove any third-party scripts (chat widgets, social pixels) you no longer need. For remaining scripts, set placement to 'Footer' and set load method to 'Defer' or 'Async'.
  4. Page Builder: Go to Storefront > Page Builder, edit your homepage, and remove unused content sections (large hero banners with unoptimized images are the #1 BigCommerce speed killer). Replace large background images with WebP versions uploaded via Marketing > Image Manager.
  5. Apps: Go to Apps > My Apps and uninstall apps you are not actively using — each app may inject storefront JavaScript.
  6. Speed app: Consider installing a performance app from the BigCommerce App Marketplace (search 'page speed') for automated lazy loading and script management.
Full BigCommerce guide →Official BigCommerce docs ↗
How to fix page speed warning on Wix
  1. Enable Turbo mode / Performance: In your Wix dashboard go to Settings > Performance and make sure 'Minify HTML, CSS & JS' and 'Browser caching' are enabled. Wix has rolled these out as automatic optimizations but verify they are active for your site.
  2. Images: In the Wix Editor, click any image and use the Image Settings to upload images at the correct size. Wix automatically converts images to WebP when served, so the main task is uploading correctly-sized source images rather than oversized originals.
  3. Video/animations: In the Wix Editor, select any autoplay background videos or heavy animations on your homepage and either remove them or replace with a static image — these are the single biggest Wix speed offenders.
  4. Apps: Go to your Wix dashboard > App Market > Manage Apps and remove any Wix App you have installed but do not actively use — each one can add JavaScript to your pages.
  5. Fonts: In the Wix Editor go to Site Design > Text Themes and switch to a font already available in Wix's system font list (e.g. Helvetica Neue, Arial) for the body text to eliminate an extra font download.
  6. Check Core Web Vitals: In the Wix dashboard go to Marketing & SEO > SEO Tools > Core Web Vitals to see your field data, then use PageSpeed Insights for lab data to identify remaining issues.
Full Wix guide →Official Wix docs ↗
How to fix page speed warning on Squarespace
  1. Images: In the Squarespace editor, click any image block and in Image Settings choose the correct focal point and reduce the image file size before uploading by using Squarespace's built-in 'Compress images on upload' setting (Settings > Advanced > Image Compression). Squarespace serves images via Fastly CDN and converts to WebP automatically.
  2. Video backgrounds: In the Pages panel, click any section that uses a video background and replace it with a high-quality static image — video backgrounds are the biggest single Squarespace speed issue.
  3. Code injection: Go to Settings > Advanced > Code Injection and audit any custom HTML/CSS/JS you or a developer has added. Remove or defer any third-party scripts that are not business-critical.
  4. Fonts: In Design > Fonts, reduce the number of font styles you use. Each distinct font weight or style is a separate HTTP request. Choose two fonts maximum and limit to the weights you actually use.
  5. Extensions: Go to Extensions in your Squarespace dashboard and remove any extension (third-party app) you are not actively using.
  6. Squarespace does not allow server-level caching configuration — it is handled automatically — so focus on asset optimization (images, video, scripts) and reducing page complexity.
Full Squarespace guide →Official Squarespace docs ↗
How to fix page speed warning on Webflow
  1. Images: In the Webflow Designer, select any image element and in the element settings enable 'Lazy load' for all images below the fold. Upload images at the correct display size and enable WebP output in Project Settings > General > Image Optimization.
  2. Interactions / animations: In the Webflow Designer, go to the Interactions panel (the lightning bolt icon) and audit all animations. Remove or simplify page-load trigger animations on hero sections — these block perceived performance.
  3. Custom code: In Project Settings > Custom Code, review any scripts added to the <head> or before </body> tags. Move non-critical scripts to the footer position and add defer or async attributes via a custom code embed.
  4. Fonts: In Project Settings > Fonts, use system fonts for body text and limit web font imports to one or two families. Each Google Font variant is a separate request.
  5. CMS images: For CMS-driven pages (e.g. product or blog pages), open the Collection Template in the Designer and ensure the image element bound to your CMS image field has 'Lazy load' enabled and a defined 'Max width' so Webflow auto-sizes it.
  6. Publish and verify: After publishing changes, run PageSpeed Insights on your live Webflow domain (not the .webflow.io preview) to get accurate results, since the preview subdomain may have different caching behaviour.
Full Webflow guide →Official Webflow docs ↗
How to fix page speed warning on Adobe Commerce (Magento)
  1. Full-page cache: In the Magento admin go to System > Cache Management and ensure 'Full Page Cache' is enabled. For production, configure Varnish Cache as the FPC application (Stores > Configuration > Advanced > System > Full Page Cache > Caching Application = Varnish Cache) — this is the single highest-impact Magento speed improvement.
  2. JS/CSS bundling: In the admin go to Stores > Configuration > Advanced > Developer > JavaScript Settings: set 'Enable JavaScript Bundling' to Yes, 'Minify JavaScript Files' to Yes; and under CSS Settings set 'Minify CSS Files' to Yes.
  3. Images: In the admin go to Stores > Configuration > General > Web > Engines and enable WebP conversion. Use a Magento image optimization extension (e.g. TinyPNG for Magento) or optimize images before upload. Ensure the built-in lazy load is active under Catalog > Configuration.
  4. CDN: In Stores > Configuration > General > Web > Base URLs (Secure), configure a CDN base URL (e.g. Fastly, which is included with Adobe Commerce Cloud) so all static assets are served from edge nodes.
  5. Third-party modules: In the admin go to System > Web Setup Wizard > Module Manager (or use bin/magento module:status in CLI) and disable any module you are not using — unused modules still load code on every request.
  6. For Adobe Commerce Cloud: Use the Fastly CDN and image optimisation settings in the Cloud Console under your environment's Fastly configuration panel rather than the Magento admin, as Cloud overrides some admin settings.
Full Adobe Commerce (Magento) guide →Official Adobe Commerce (Magento) docs ↗
How to fix page speed warning on Shopify Plus
  1. All standard Shopify steps apply (see Shopify above).
  2. Scripts: In Shopify Plus, go to Online Store > Themes > Edit code and audit the checkout.liquid file for any checkout-specific scripts added by an agency or app. Remove unused checkout scripts — they delay the most conversion-critical page in your funnel.
  3. Launchpad / Flow: Use Shopify Flow to schedule script-heavy promotional apps to activate only during sale periods rather than running 24/7.
  4. Headless consideration: If your Plus store is on a headless or custom storefront (Hydrogen / Remix), work with your developer to implement streaming SSR, route-based code splitting, and Shopify's built-in CDN for media.
Full Shopify Plus guide →Official Shopify Plus docs ↗
How to fix page speed warning on PrestaShop
  1. In the PrestaShop admin go to Advanced Parameters > Performance: set 'Smart cache for CSS' and 'Smart cache for JavaScript' to Yes, enable CCC (Combine, Compress, Cache) for both CSS and JS, and set 'Minimize HTML' to Yes.
  2. Enable 'Use CCC for CSS files', 'Use CCC for JavaScript files', and 'Compress inline JavaScript' all from the same Performance page.
  3. Images: Go to Design > Image Settings and configure WebP format output. Then go to Catalog > Products and use the 'Regenerate Thumbnails' option after changing settings to rebuild all product images at optimal sizes.
  4. Caching: On the Performance page, under 'Caching', enable the file system cache. For high-traffic stores add a Memcached or Redis module from the PrestaShop Addons marketplace.
  5. Modules: Go to Modules > Module Manager and disable or uninstall modules you are not using. Filter by 'Installed' to audit the full list.
Full PrestaShop guide →Official PrestaShop docs ↗
How to fix page speed warning on OpenCart
  1. In the OpenCart admin go to System > Settings > [your store] > Server tab: set 'Compression Level' to a value between 1–9 (use 6 as a balanced default) to enable Gzip output compression.
  2. Enable the built-in OpenCart cache: go to System > Settings > Server tab and set 'Cache' to the file-based cache driver and enter a cache expiry time (3600 seconds is a good starting point).
  3. Images: Before uploading, compress product images using a tool like Squoosh (squoosh.app) and save in WebP format. Install an image optimisation extension from the OpenCart Marketplace to automate this on future uploads.
  4. Extensions: Go to Extensions > Extensions > Modules and disable any module not in active use — each enabled module may add queries and assets to every page load.
  5. For a larger performance gain, configure your web server (Apache/Nginx) to serve Gzip-compressed files and add browser cache headers — this requires access to your hosting control panel (e.g. cPanel > .htaccess) or your server's Nginx config.
Full OpenCart guide →Official OpenCart docs ↗
How to fix page speed warning on Klaviyo
  1. In your Klaviyo account, go to Settings → Integrations and locate your Klaviyo JavaScript snippet (onsite tracking). Confirm you are using the latest async/non-blocking version of the snippet — it should use 'async' or 'defer' attributes so it does not block page rendering.
  2. In your storefront theme, find where the Klaviyo snippet is injected (commonly in theme.liquid or a header snippet). Move the Klaviyo <script> tag to just before the closing </body> tag rather than in the <head>, so it loads after critical above-the-fold content and does not contribute to render-blocking.
  3. Remove any duplicate Klaviyo script tags across your theme files (e.g., in header.liquid, footer.liquid, and product templates). Multiple instances of the snippet multiply its load impact — only one instance should exist per page.
  4. Disable any unused Klaviyo onsite features (e.g., back-in-stock, web push, signup forms) in Klaviyo → Website → Forms/Notifications. Each active feature injects additional JavaScript; disabling unused ones reduces total script payload.
  5. For Klaviyo signup popup/flyout forms, go to Klaviyo → Website → Sign-up Forms, open each active form, click 'Settings', and enable the 'Show after page load delay' option (set to at least 3–5 seconds). This delays form script execution until after the main page has loaded and rendered.
  6. After changes are made, test page load time using Google PageSpeed Insights or WebPageTest and confirm the Klaviyo scripts no longer appear as render-blocking resources in the diagnostics before re-publishing your theme.
Full Klaviyo guide →Official Klaviyo docs ↗
How to fix page speed warning on Yotpo
  1. In your Yotpo admin, go to Settings → General Settings, and ensure the 'Load Yotpo Asynchronously' option is enabled. This prevents Yotpo's JavaScript from blocking the main thread and rendering of your page.
  2. Navigate to Settings → Widgets in Yotpo and audit which widgets are active (Reviews, Star Ratings, Q&A, Visual UGC, etc.). Disable any widgets not actively displayed on your storefront — each active widget loads additional JS/CSS resources.
  3. For Star Rating widgets on collection/product listing pages, switch to Yotpo's 'Inline' or 'Bottomline' widget variant rather than the full Reviews widget. These are significantly lighter and reduce render-blocking payload on high-traffic pages.
  4. In your theme code, locate the Yotpo snippet (typically yotpo.liquid or a <script> tag referencing staticw2.yotpo.com). Ensure the script tag uses the 'defer' or 'async' attribute (e.g. <script async src='...'>) so it does not block HTML parsing.
  5. In Yotpo Settings → Display, disable any unused Yotpo features such as 'Yotpo Loyalty', 'SMS Bump', or 'Subscriptions' widgets if those products are not in use — each inactive-but-loaded integration adds unnecessary JavaScript weight.
  6. After making changes, test your page load time using Google PageSpeed Insights (pagespeed.web.dev) or WebPageTest.org to confirm Yotpo-related resources are loading asynchronously and are no longer flagged as render-blocking.
Full Yotpo guide →Official Yotpo docs ↗
How to fix page speed warning on Next.js (Headless)
  1. Use next/image for ALL product and hero images — set `priority` on above-the-fold images, always supply `width`/`height` or `fill`, and configure `remotePatterns` in `next.config.ts` so images are auto-converted to WebP/AVIF and lazy-loaded by default.
  2. Eliminate render-blocking fonts by switching to `next/font` (e.g. `next/font/google`). Call the font loader at the module level, apply the returned `className` to your root layout, and remove any manual `<link rel='stylesheet'>` font imports from `app/layout.tsx`.
  3. Enable HTTP response compression and long-lived caching headers in `next.config.ts`: set `compress: true`, add `Cache-Control` headers for static assets via the `headers()` async function, and leverage Next.js's built-in ISR (`revalidate`) to avoid full SSR on every request.
  4. Code-split and lazy-load heavy below-the-fold components (carousels, modals, review widgets) with `next/dynamic` and `{ ssr: false, loading: () => <Skeleton /> }` so their JS is not part of the critical bundle.
  5. Add a `<link rel='preconnect'>` and `<link rel='dns-prefetch'>` for every third-party origin (CDN, analytics, payment scripts) inside `app/layout.tsx` via the Next.js `<Head>` equivalent metadata exports or direct JSX in the root layout.
  6. Run `next build && next start` and audit with Lighthouse / `@next/bundle-analyzer` — set `ANALYZE=true` in `.env.local`, identify large chunks, and either tree-shake or dynamically import them.
Full Next.js (Headless) guide →Official Next.js (Headless) docs ↗
How to fix page speed warning on Elementor
  1. In your WordPress dashboard, go to Elementor → Settings → Performance. Enable 'Improved Asset Loading' (loads only the CSS/JS required for each page) and set 'CSS Print Method' to 'External File' so stylesheets are cached by the browser rather than inlined on every request.
  2. Still in Elementor → Settings → Performance, enable 'Lazy Load Background Images' and turn on 'Optimized DOM Output' to reduce the number of wrapper divs Elementor renders, shrinking HTML payload and speeding up rendering.
  3. Go to Elementor → Settings → Experiments and enable 'Flexbox Container' (replaces legacy nested divs with a leaner flex layout) and 'Optimized CSS Loading' if available — both reduce render-blocking CSS delivered per page.
  4. For every image widget in your Elementor pages, open the widget settings, set the Image Size to the smallest display-appropriate size (e.g. 'Large' instead of 'Full'), and enable the native 'Lazy Load' attribute under Advanced → Additional Options so off-screen images are deferred.
  5. Install a caching and minification plugin compatible with Elementor (e.g. LiteSpeed Cache, WP Rocket, or W3 Total Cache). In that plugin: enable Page Caching, enable GZIP/Brotli compression, and minify + combine CSS/JS files — then go to Elementor → Tools → Regenerate CSS & Data after saving, to ensure Elementor's generated stylesheets are refreshed under the new caching rules.
  6. After all changes, go to Elementor → Tools → Regenerate CSS & Data and click 'Regenerate Files'. Then test your page speed in a tool such as Google PageSpeed Insights or WebPageTest to confirm load time is under 1.5 seconds; revisit any remaining Elementor widgets that load unused third-party scripts (e.g. Google Maps, Video) and switch them to a 'facade' or lazy-load approach where possible.
Full Elementor guide →Official Elementor docs ↗

Does your site have this issue?

Run a free SEOLZ scan to find page speed warning — and every other issue — across your whole site in minutes.

Scan my site free

Frequently asked questions

What is Page speed warning?

Page load time is how long it takes for a visitor's browser to fully display your store page after they click a link or type your URL. When a page takes more than 1.5–2 seconds to load, visitors experience a noticeable delay before they can see and interact with your content. A load time of 3 seconds or more (like the example finding) is considered slow by both Google and modern shoppers. Page speed is measured by several signals — the most important being Google's Core Web Vitals, which assess how fast your content appears, how quickly it becomes interactive, and how stable the layout is as it loads.

Why does page speed warning matter?

Google has officially made page speed and Core Web Vitals a direct ranking factor for all pages. Slow pages rank lower in search results, meaning fewer people find your store organically — costing you traffic and revenue before a visitor even arrives. For shoppers who do visit, studies consistently show that every additional second of load time reduces conversions: a 3-second page loses a significant portion of mobile shoppers to bounce before they see a single product. Slow stores also perform poorly in Google's mobile-first index, which evaluates your mobile experience first when deciding your rankings. Fixing page speed is one of the highest-ROI improvements an ecommerce store can make — it simultaneously boosts your SEO rankings, increases conversion rates, and improves accessibility for users on slower connections or lower-end devices.

How do I fix page speed warning?

Reduce your page load time to under 1.5 seconds by optimizing images, eliminating render-blocking resources, and enabling caching and compression.

Related SEO issues