Website audit scorecard for singlefeather.com

No title tag was detected.

Failed: earned 0 of 10 points.

Priority: Priority 8: fix during launch polish.

Why it matters: Search engines, social previews, and saved browser tabs use the title to tell people what your product is.

Fix: Set one concise title tag, ideally 10 to 70 characters, that includes the product name and the main promise.

No meta description was detected.

Failed: earned 0 of 10 points.

Priority: Priority 3: fix before sharing the page publicly.

Why it matters: A missing description makes previews weaker when early users share or find the page.

Fix: Add a meta description around 50 to 170 characters that says who the product helps and what outcome it creates.

Detected 0 H1 heading(s) and 0 total headings.

Failed: earned 0 of 8 points.

Priority: Priority 9: fix during launch polish.

Why it matters: Clear headings help visitors, search engines, and assistive technology understand the page quickly.

Fix: Keep one H1 for the main promise, then use H2 and H3 headings in order for sections below it.

No canonical link tag was detected.

Failed: earned 0 of 10 points.

Priority: Priority 9: fix during launch polish.

Why it matters: A canonical tag reduces duplicate URL confusion before marketing links start spreading.

Fix: Add a canonical link tag that points to the final public landing page URL.

HTTP 403 returned for sitemap_xml.

Failed: earned 0 of 12 points.

Priority: Priority 7: fix during launch polish.

Why it matters: A sitemap helps search engines discover the landing page and related public pages sooner.

Fix: Add /sitemap.xml with your public URLs and confirm it returns HTTP 200.

Detected 0 JSON-LD schema block(s).

Failed: earned 0 of 10 points.

Priority: Priority 12: fix during launch polish.

Why it matters: Structured data gives search and answer engines explicit facts about your product.

Fix: Add JSON-LD for SoftwareApplication, Product, Organization, or WebSite using only accurate public facts.

Detected 0 of 4 Open Graph basics.

Failed: earned 0 of 5 points.

Priority: Priority 18: lower-risk cleanup after urgent launch blockers.

Why it matters: Launch links on X, LinkedIn, Slack, and communities look less trustworthy without a strong preview.

Fix: Add og:title, og:description, og:image, and og:url that match the landing page content.

Detected 0 internal link(s).

Failed: earned 0 of 6 points.

Priority: Priority 16: lower-risk cleanup after urgent launch blockers.

Why it matters: Internal links help visitors find pricing, docs, contact, legal, or product details without getting stuck.

Fix: Add clear public links such as pricing, docs, contact, privacy, terms, or product detail pages where appropriate.

Heading levels found: none.

Failed: earned 0 of 11 points.

Priority: Priority 13: fix during launch polish.

Why it matters: A clean heading outline helps visitors scan the page and helps assistive technology navigate it.

Fix: Use headings in order: one H1, then H2 for major sections, then H3 for subsections.

Detected 0 landmark element(s) or roles.

Failed: earned 0 of 10 points.

Priority: Priority 18: lower-risk cleanup after urgent launch blockers.

Why it matters: Landmarks make the page easier to navigate for assistive technology and keyboard users.

Fix: Use semantic elements such as header, nav, main, and footer around the appropriate page areas.

No html lang attribute was detected.

Failed: earned 0 of 9 points.

Priority: Priority 19: lower-risk cleanup after urgent launch blockers.

Why it matters: Screen readers use the language attribute to pronounce content correctly.

Fix: Add the correct lang attribute to the html element, such as lang="en".

14 of 14 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.61.

Failed: earned 0 of 8 points.

Priority: Priority 20: lower-risk cleanup after urgent launch blockers.

Why it matters: Low contrast makes a launch page feel less polished and can exclude users with low vision.

Fix: Review key text, buttons, and links against a 4.5:1 contrast target for normal text.

axe found 1 violation rule(s), including 1 serious or critical rule(s). Top rules: meta-refresh (1).

Failed: earned 0 of 18 points.

Priority: Priority 5: fix before sharing the page publicly.

Why it matters: axe checks the actual browser-rendered page, so these issues can affect people using keyboards, screen readers, or other assistive technology.

Fix: Fix the top axe rule IDs first, especially critical and serious violations around names, roles, labels, headings, contrast, landmarks, and keyboard-accessible controls.

Detected 0 CTA candidate(s).

Failed: earned 0 of 14 points.

Priority: Priority 4: fix before sharing the page publicly.

Why it matters: Early visitors need a clear next step, such as trying the product, joining a waitlist, or booking a demo.

Fix: Add one prominent CTA above the fold with action-oriented text such as Start, Join, Try, Book, or Get started.

Detected 0 H1 heading(s) and 0 meta-description characters.

Failed: earned 0 of 13 points.

Priority: Priority 6: fix during launch polish.

Why it matters: Visitors decide quickly whether the product is relevant; a vague hero weakens every acquisition channel.

Fix: Use one clear H1 plus supporting copy that names the audience, problem, and outcome.

Detected about 0 visible word(s).

Failed: earned 0 of 10 points.

Priority: Priority 21: lower-risk cleanup after urgent launch blockers.

Why it matters: Too little copy can leave visitors confused; too much copy can bury the value proposition.

Fix: Add concise sections for value, proof, how it works, and next steps, then remove repetitive copy.

Detected 0 trust-signal keyword occurrence(s).

Failed: earned 0 of 10 points.

Priority: Priority 16: lower-risk cleanup after urgent launch blockers.

Why it matters: Trust signals reduce hesitation when strangers see the product for the first time.

Fix: Add honest proof such as customer quotes, usage stats, founder credibility, security notes, or relevant logos.

No viewport meta tag was detected.

Failed: earned 0 of 12 points.

Priority: Priority 3: fix before sharing the page publicly.

Why it matters: Launch traffic often comes from phones; missing viewport metadata can make the page render poorly.

Fix: Add a viewport meta tag with width=device-width and initial-scale=1.

Average sentence length is about 0 word(s).

Failed: earned 0 of 9 points.

Priority: Priority 23: lower-risk cleanup after urgent launch blockers.

Why it matters: Launch visitors often skim; long sentences make the offer harder to understand.

Fix: Shorten long sentences, use direct language, and break dense paragraphs into smaller sections.

Detected 0 spacing class/style signal(s).

Failed: earned 0 of 7 points.

Priority: Priority 25: lower-risk cleanup after urgent launch blockers.

Why it matters: Consistent spacing helps the page feel deliberate and easier to scan.

Fix: Use consistent section padding, gaps, and margins across repeated content blocks.

Detected 0 hierarchy signal(s) from headings, CTA, and emphasized text.

Failed: earned 0 of 9 points.

Priority: Priority 12: fix during launch polish.

Why it matters: Hierarchy tells visitors what to read first and what action to take next.

Fix: Create a clear H1, supportive section headings, emphasized proof, and one visually prominent primary CTA.

Detected 1 console error(s) and 0 uncaught page error(s) during render.

Failed: earned 0 of 7 points.

Priority: Priority 15: fix during launch polish.

Why it matters: Runtime errors can break forms, CTAs, animations, tracking, or responsive behavior even when the static HTML looks fine.

Fix: Open the page in a browser, reproduce the console errors, and fix missing assets, hydration problems, client-side exceptions, or failing third-party scripts.