Find what your store is losing sales to
A slow product page costs you twice — once in rankings, once in shoppers who leave before it loads. Audit speed, Core Web Vitals, checkout security and product-page SEO across your whole catalogue in one free report.
Speed where it earns
LCP and CLS measured on the product and category templates that actually convert, not just the homepage.
Trust at checkout
Certificate expiry, HTTPS enforcement and security headers — the things that spook a shopper mid-purchase.
Products that get found
Titles, canonicals and structured data checked across the catalogue so product pages can rank.
Your homepage is not the problem
Store owners test their homepage because it is the page they look at. But almost nobody buys from a homepage. Traffic from Google lands on product and category pages, and those are built from templates that quietly accumulate weight — a reviews app, an upsell widget, a chat bubble, three pixels, and product images uploaded straight from a phone at 4000px wide.
Running a full crawl instead of a single-page test is what surfaces this. It is common to see a homepage scoring in the 90s while the product template sits in the 50s, and the product template is the one taking the orders.
Speed costs you at both ends
Core Web Vitals are a confirmed Google ranking signal, so a store with poor LCP and CLS on product pages gets less organic traffic to begin with. Then the shoppers who do arrive meet the same slow page and some of them leave. The loss compounds, which is why speed work on a store usually pays back faster than on a brochure site.
Layout shift deserves specific attention on stores. A price or an Add to Cart button that jumps as a late image loads is not just a metric — it is a shopper tapping the wrong thing at the moment of purchase.
Trust signals at checkout
Stores take payment details, which makes them a target and makes browser warnings expensive. An SSL certificate that quietly expires produces a full-page browser warning at the worst possible moment, and most owners find out from a customer rather than a monitor.
siteIQ also checks security headers and flags known CVEs against the platform and plugin versions it detects — relevant if you are running an older WooCommerce install or a theme that has not been updated in two years.
Catalogue SEO at scale
Large catalogues generate large SEO problems: variant URLs competing with each other, duplicate titles across near-identical products, canonicals pointing at the wrong variant, and category pages orphaned by a navigation change nobody noticed. These are invisible on a single-page test and obvious on a crawl.
The audit lists duplicate titles and descriptions grouped together, so you can see that 340 product pages share one title tag rather than discovering it one page at a time.
Common questions
- Does siteIQ work with Shopify and WooCommerce?
- Yes. It audits the rendered store the way a shopper's browser and Googlebot see it, so the platform underneath does not matter. It will also detect and name the platform, theme and major apps as part of the tech stack report.
- Can it crawl a store with thousands of product URLs?
- Yes — the full-site crawl has no 500-URL cap, which is where Screaming Frog's free licence stops. Large catalogues take longer, and progress streams live so you can watch it work rather than guess.
- Why do my product pages score worse than my homepage?
- Usually images and apps. Homepages get optimised because everyone looks at them; product templates accumulate unoptimised uploads, review widgets, upsell scripts and tracking pixels that nobody revisits. Since product pages are where the money is made, that is backwards — and it is the most common finding on store audits.
- Does site speed really affect sales?
- It affects two things at once. Core Web Vitals are a Google ranking signal, so slow product pages rank lower and get less traffic. Separately, shoppers abandon slow pages regardless of ranking. A store with a 4-second LCP is losing sales at both ends of the funnel.
- What security issues matter most for a store?
- An expiring or misconfigured SSL certificate is the urgent one — browsers will warn shoppers at exactly the wrong moment. After that, missing HSTS and Content-Security-Policy headers, and known CVEs in an outdated platform or plugin version, since stores handle payment data and are actively targeted.
Check your store now
Works with Shopify, WooCommerce, Magento and custom builds. No signup.
