brief/Open console

Website critique

Compare a site against its category.

Critique report

Internet for people, not profit

Score

99

Hero specificity

strong

Primary claim detected: “Choose your language or locale to browse Mozilla.org”.

Make sure the H1 names the buyer situation and first proof object, not only the category.

Pattern memory

partial

24 anti-pattern risk(s) detected. First risk: Conversion section has visuals, but they appear decorative or too small to carry the claim..

Conversion section has visuals, but they appear decorative or too small to carry the claim.

Taste intelligence

strong

Strongest taste signal: enterprise-safe for enterprise or regulated buyer.

Preserve the strongest taste signals while making proof, visuals, and copy more scenario-specific.

Proof quality

strong

3 proof object candidate(s) detected: Code, Security, Pricing.

Move the strongest proof object into the first two scrolls and label what the visitor is seeing.

Visual evidence

weak

8 visual asset role(s) detected: UI Mockup, Integration Logos, Compliance / Security Badge, Background Decoration, Icon / SVG System, Chart / Graph, Hero / Primary Visual, Unclassified Visual. Visual evidence score: 48.

Add section-specific visual evidence instead of relying on text, cards, or decorative backgrounds.

Section visual support

weak

28 of 28 major section(s) are missing or relying on decorative-only visuals. First issue: Conversion section has visuals, but they appear decorative or too small to carry the claim.

Add a visual asset that supports this section's claim. Target roles: hero_product_screenshot, ui_mockup, customer_person_image.

Trust layer

strong

3 trust signal candidate(s) detected: Security, Pricing Clarity, Docs.

Layer trust with customer proof, security/compliance, pricing clarity, docs, changelog, or status evidence.

CTA path

strong

1 primary CTA candidate(s) detected.

Keep one dominant primary CTA per major section and pair it with one lower-friction evaluator path.

Responsive capture

strong

Mobile screenshots exist for every captured page.

Inspect mobile captures for text overlap, unreadable screenshots, CTA stacking, and sticky header coverage.