Give me comprehensive website feedback for founderkarma.co

FounderKarma — Website Feedback

FounderKarma is a single-hero persuade-mode landing page for a founder reciprocity community. Its strongest choice is naming the mechanism directly in the headline — "by supporting others" — so a first-time visitor understands the exchange in one read.

What's working

• Headline carries the whole page. The H1 splits into a white promise ("Get your first set of users") and a purple mechanism ("by supporting others"). The color split makes the value proposition scannable before the visitor reads the subhead.
• Typography hierarchy is disciplined. Space Grotesk at three sizes — 48px H1, 16px body, 13px tracked eyebrow — creates clear levels without ornament. The 2.6px tracking on the eyebrow reads as a deliberate label, not body copy.
• Body contrast is excellent. #ededed on #0a0a0a measures 16.92:1 WCAG and −95.97 APCA, well above every threshold.

Priority issues, ranked by impact

### 1. The page proves nothing about the community it sells The subhead says "Join a community of 171 founders" but the page shows zero evidence of that community — no avatars, no recent activity, no testimonial, no example exchange. For a product whose entire value is the community, the hero is the only place to prove it exists. A persuade-mode visitor who lands here from a cold channel has no reason to trust the number.

Concrete change: Replace the empty space below the CTA cluster with a single horizontal strip of 8–12 founder avatars (overlapping circles, ~32px each) and one line of recent activity — "Sarah just reviewed Acme's landing page" or a similar timestamped micro-proof. This converts the abstract "171 founders" into visible social proof without adding a new section.

Reference that explains it: Count's landing leads with a product screenshot in the hero, proving the tool exists before asking for signup.

### 2. The primary conversion button fails WCAG AA The "Sign up" button uses white text on #7f77dd purple at 14px / weight 500. The measured pair is 3.76:1 WCAG and −70.48 APCA — below the 4.5:1 minimum for small text. This is the button that converts anonymous visitors into accounts, and it sits next to a "Sign in" outline button that draws the eye away from it.

Concrete change: Either darken the button background to a purple that clears 4.5:1 against white (try #5b54c4 or darker), or switch the button text to the near-black #0a0a0a. The current purple is decorative; the button is functional.

### 3. The CTA cluster has no clear primary action Three buttons sit in a row: "Continue with Google" (white, full-width above), "Sign up" (purple), "Sign in" (outline). A first-time visitor doesn't know which one to click. "Continue with Google" is the actual fastest path, but it's visually separated from the email options by a gap, and "Sign up" competes with it for attention.

Concrete change: Stack the actions vertically with "Continue with Google" as the visually dominant option (full-width, white background, Google logo left), then a thin "or" divider, then "Sign up" and "Sign in" as a compact pair below. This matches the mental model most visitors bring from other auth flows.

### 4. The floating chat bubble is a generic SaaS default A circular chat icon in the bottom-right corner is a template pattern that signals "we added Intercom" rather than "this is FounderKarma." It also overlaps the Product Hunt badge on mobile, creating a collision in the conversion zone.

Concrete change: Remove the chat bubble on the landing page entirely, or replace it with a product-specific affordance — a "See how it works" link, or a small "171 founders online" indicator that reinforces the community claim.

### 5. The Product Hunt badge floats in dead space Below the CTA cluster, a large vertical gap separates the buttons from the Product Hunt badge. This gap reads as "the page is unfinished" rather than "breathing room." The badge itself is a launch artifact, not a product feature.

Concrete change: Either move the badge into the nav (top-right, next to "Sign in") so it doesn't compete with the CTA, or replace it with a single line of social proof — "Featured on Product Hunt" as text, not a full badge.

Contrast table

The "Sign up" button is the only failing pair and the highest-impact one — it's the conversion path.

Vibe-coded default audit

• Single hero with eyebrow + H1 + subhead + CTA cluster — present, but the eyebrow ("PEOPLE HELP YOU FASTER IF YOU HELP THEM") is a generic motivational statement that could belong to any community product. Generic/default. Replace with a product-specific label like "FOR FOUNDERS SHIPPING IN PUBLIC" or "REVIEW-FOR-REVIEW COMMUNITY."
• "Continue with Google" as primary CTA — present and appropriate for an auth-first product. Earned.
• Floating chat bubble — present, generic SaaS pattern, overlaps content on mobile. Generic/default. Remove or replace.
• Product Hunt badge — present, sits in dead space below CTAs. Neutral. Move into nav or replace with text.
• Purple accent on dark background — present, specific enough to the brand. Earned.
• No social proof, no feature explanation, no screenshots — the page is a single hero with no supporting evidence. Generic/default. This is the biggest gap.

First change to make

Fix the "Sign up" button contrast. Darken the purple to #5b54c4 or switch the text to #0a0a0a. This is a five-minute CSS change that removes the only accessibility failure on the page and makes the primary conversion button visually dominant over the "Sign in" outline.

Reference pages

Palette

Typography

Design values