Product Page Comparator
Compare a product page to two competitors' on SEO, UX and CRO criteria specific to e-commerce: visible pricing, CTA, trust signals, structured Product/Offer data.
This tool analyzes the page's HTML structure (CTAs, forms, trust signals, pricing, navigation) and its loading performance. It cannot measure a real conversion rate: that requires the analyzed site's own tracking (Contentsquare, Hotjar, GA4...), which isn't accessible on a third-party URL.
🕵️
How to use this tool
- 1Enter your product page URL and up to two competitors'
- 2Run the comparison
- 3Review which criteria pass or fail, with the advice for each
Why it matters
A product page that doesn't clearly show its price or carries no trust signal loses sales before the buyer even starts comparing. This tool checks these specific signals, plus the structured Product/Offer/Review data that also feeds Google's rich results.
A concrete example
On a typical product page, the tool might find a clearly visible price and a clear purchase CTA, but no structured Product/Offer data detected in the source code: the page can be flawless visually while remaining invisible to Google's rich snippets (price, rating, availability in search results).
Frequently asked questions
Does this tool measure a real conversion rate?
No. A real conversion rate requires tracking specific to the site (Google Analytics, Contentsquare, Hotjar...), which isn't accessible on a third-party URL. The tool analyzes the page structure that correlates with conversion, without measuring it directly.
What do FCP, LCP, CLS and INP/TBT mean?
These are the Core Web Vitals, the indicators Google uses to assess a page's loading experience. FCP (First Contentful Paint) measures the time until the first visible element appears. LCP (Largest Contentful Paint) measures the time until the largest visible element appears. CLS (Cumulative Layout Shift) measures visual stability during loading. INP (Interaction to Next Paint) measures the page's actual responsiveness to interactions; TBT (Total Blocking Time) is its lab equivalent.
What's the difference between PSI, Lighthouse and CrUX?
PageSpeed Insights (PSI) is the Google API this tool uses. It combines two sources: Lighthouse, a lab test that simulates loading on a standardized device and network, and CrUX (Chrome User Experience Report), which aggregates real measurements from Chrome users who visited the page. This tool's "Mobile performance" score comes from Lighthouse. The Core Web Vitals block shows CrUX data when available, otherwise the Lighthouse lab estimate.
Why does the Core Web Vitals block sometimes show a lab estimate instead of field data?
CrUX only returns data if the page received enough Chrome traffic over the last 28 days. Below that threshold, common on lower-traffic sites or recent pages, no field data exists: the tool then falls back to the Lighthouse lab estimate, a simulated test rather than a real measurement.
Why does the indicator become TBT instead of INP in the lab estimate?
INP measures real responsiveness to actual visitor interactions: it can only be measured on real traffic, not in a lab test where no one interacts with the page. TBT is the closest lab indicator: it estimates the time the page stays blocked and unable to respond quickly to an interaction.
Why check structured data on a product page?
Product, Offer and Review/AggregateRating tags let Google display rich snippets (price, rating, availability) directly in search results, which improves click-through rate.
Can the tool detect a price that varies by option (size, color)?
It detects a price displayed on the page as loaded, not variants loaded dynamically after a click. If your prices only appear after selecting an option, test the URL with the default option selected.
Do customer reviews count as a trust signal?
Yes, the tool looks for mentions of reviews, ratings or testimonials in the page content. Their absence isn't disqualifying, but it's one of the most effective trust signals on an e-commerce product page.