Web Page Comparator

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.

The one that matches what the page is for, not its template: homepage to point visitors to the rest of the site, category page to browse a catalogue, product page to sell one item, pricing page for a price grid, sign-up or lead magnet landing page depending on what the page asks in return, checkout for one payment step. Each type applies its own criteria set: navigation, for instance, counts in your favour on a homepage and against you on a landing page.

Look at the detailed criteria first, not just the overall score: a competitor might win on CTA clarity while losing on trust signals. The gap points to priorities to address, not an overall verdict on your page.

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.

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.

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.

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.

Clear navigation to key sections, an identifiable primary CTA, trust signals and decent readability. Unlike a landing page, visible navigation here is a positive sign, not a distraction.

That's a common case (B2B and B2C, or multiple personas). The tool can't judge whether the targeting itself makes sense, but it checks that each proposed path stays clear: too many competing CTAs for different audiences dilutes everyone's attention, regardless of persona.

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.

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.

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.

Product, Offer and Review/AggregateRating tags let Google display rich snippets (price, rating, availability) directly in search results, which improves click-through rate.

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.

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.

The tool flags the absence of pricing as a potential barrier, but some complex B2B models justify quote-based pricing: assess this based on your commercial context, not as an absolute rule.

No, it checks display clarity (price, plans, trust signals), not the pricing strategy itself. The number of plans and their positioning call for a deeper CRO audit.

It detects the price as displayed when the page loads, usually the toggle's default option. If your page dynamically switches between monthly and annual, the result reflects the default state, not both views.

A sign-up landing page has a single conversion goal. Full navigation offers escape routes that reduce the form completion rate.

Yes, the tool counts every link on the page, including those inherited from the site's global template. That's actually the most common blind spot: a dedicated landing page that still keeps the site's main menu.

No, the analysis only covers the URL provided, so the landing page itself. The confirmation page shown after form submission (often decisive for what follows) is outside this tool's scope.

Ideally just one (email), two at most. Each additional field measurably reduces the conversion rate on this type of page.

That's a legitimate trade-off, but every extra field has a cost in lead volume. Best practice is to qualify afterward (follow-up email, behavioral scoring), not at the moment of the first exchange for content.

No, it can't judge the perceived value of the deliverable itself (guide, checklist, webinar). It only checks the structural criteria of the page around it: form, CTA, absence of distraction.

On a checkout flow, missing HTTPS is a dealbreaker for trust: most visitors abandon immediately if they see an insecure connection warning at the moment of payment.

Analyze each step separately (cart, address, payment) by changing the URL entered. The tool evaluates one page at a time; it can't reconstruct an entire multi-page journey from a single URL.

No, it can't detect which payment methods are actually integrated (often loaded via JavaScript). It does check for the presence of secure payment logos or mentions in the page content, a distinct reassurance signal.