Ecommerce platform detected

What this check does

Fingerprints the page against a library of ecommerce-platform signatures and reports which one (if any) powers the storefront. This is informational — it doesn’t pass or fail. It changes which downstream recommendations apply, because every platform has different defaults for Schema.org, analytics, caching, and image handling.

Why it matters

Generic “make your store faster” advice is useless. The actionable advice is platform-specific:

• Shopify auto-emits Product Schema.org and handles image CDN delivery, but every third-party app you install adds JS to every page — that’s the main lever.
• WooCommerce runs on WordPress, so it inherits WordPress’s plugin sprawl problem and needs an object cache (Redis) plus a CDN to be fast.
• Magento / Adobe Commerce is the heaviest of the bunch and requires Varnish, flat catalog mode, and aggressive cache warming to be tolerable.
• BigCommerce is hosted, so most performance levers are out of your control — your levers are theme choice and Stencil customization.

Knowing the platform tells you which of these levers exist. The rest of the audit reads differently in context.

How to fix it

This check is informational, so the action depends on what was detected.

Detection heuristics, for reference. MetricSpot looks at:

• <meta name="generator"> tags (Shopify, WooCommerce 8.x, Magento).
• Global JS objects (window.Shopify, window.wc_cart_fragments_params, Mage namespace).
• Asset path patterns (/cdn.shopify.com/, /wp-content/plugins/woocommerce/, /skin/frontend/, /static/version*/frontend/).
• Cookies (shopify_session, woocommerce_cart_hash, frontend for Magento).
• URL conventions (/products/, /collections/, /cart/, /checkout/).

Shopify levers:

• Audit the installed apps. Each app injects scripts on every page even when unused — uninstall, don’t just disable. Use the theme’s native sections instead of third-party page builders.
• Native Online Store 2.0 sections beat third-party builders on Core Web Vitals every time.
• Shopify auto-emits Product schema; verify it with JSON-LD structured data on a product page.

WooCommerce levers:

• Install a persistent object cache (Redis via the Redis Object Cache plugin). Without it, every page load runs a cold query against the wp_options table.
• Put a CDN in front (Cloudflare APO is purpose-built for WordPress).
• Defer or remove wc-cart-fragments on non-cart pages — it triggers an AJAX call on every page load.
• Switch product images to AVIF/WebP via a plugin like Imagify or use Cloudflare Polish.

Magento / Adobe Commerce levers:

• Run Varnish (not the built-in PHP full-page cache). Magento ships first-class Varnish support.
• Enable flat catalog (product + category) if you have under ~1M SKUs.
• Production mode + compiled DI + merged JS/CSS. Developer mode in production will tank LCP.
• Move checkout JS bundles out of the critical path; Magento’s default checkout is the heaviest page on most stores.

BigCommerce / Wix / Squarespace levers:

• Theme choice is your main control. Pick a Stencil theme with high PageSpeed scores out of the box; customizations add weight, never remove it.
• Limit third-party scripts in the script manager — every analytics and chat widget compounds.

Pair this finding with the CMS detection check (often surfaces the host CMS), analytics installed (ecommerce reporting setup), and JSON-LD structured data (Product / Offer schema for rich results).

Frequently asked questions

Why didn’t MetricSpot detect my custom-built store?

Custom storefronts (Next.js Commerce, Hydrogen, Remix + Stripe) often don’t leave platform fingerprints — that’s by design. If detection comes back empty but you know it’s a store, you’re probably running a headless setup and the web framework check will identify the frontend. The platform-specific advice above doesn’t apply; you own every lever.

Can a site run more than one ecommerce platform?

Yes — and it’s a smell. Shopify Buy Buttons embedded on a WordPress site will trigger both detections. So will a WooCommerce site embedding a Stripe Checkout iframe (which only triggers the payment processor check, not the ecommerce check). Two platforms usually means duplicate analytics, double-counted conversions, and a confused customer journey. Pick one for checkout.

Does the detected platform affect my Lighthouse score?

Indirectly. The platform doesn’t run in Lighthouse — your rendered HTML does. But each platform’s defaults push you toward certain patterns: Shopify themes tend to ship heavy hero videos, WooCommerce loads cart-fragments JS site-wide, Magento sends megabytes of CSS. The platform shapes the score floor. Your theme and app choices determine where you land within that floor.