Category Page Comparator
Compare a category or listing page to two competitors' on SEO, UX and CRO criteria specific to browsing a catalog: navigation, filters, pricing, readability.
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 category 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 category page without visible navigation or filters slows down catalog browsing before the visitor even reaches a product page. This tool specifically checks these orientation criteria, specific to this page type.
A concrete example
On a typical category page, the tool might find good readability and prices displayed on every product thumbnail, but a very low number of navigation links: a possible sign of a filter system handled entirely in JavaScript, invisible in the raw HTML and therefore probably underused by search engines.
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 does navigation matter so much on a category page?
Unlike a landing page where navigation is a distraction, a category page should instead make browsing and filtering easier: its absence is a real conversion barrier here.
Does the tool detect JavaScript-driven filters?
Not directly: the analysis covers the raw HTML returned by the server, not the DOM after JavaScript execution. A fully dynamic filter system may therefore appear as weak navigation even though it works well for the user.
Are pagination or infinite scroll evaluated?
The tool doesn't judge this choice on its own, but poorly implemented infinite scroll can reduce the number of navigation links detectable in the initial HTML, which may look like a weak navigation signal without always being one in practice.