Skip to main content

keyforgegd.vercel.app

https://keyforgegd.vercel.app/Privacypolit.html

Completed

Curious how yours stacks up?

keyforgegd.vercel.app scored 59/100. Where would your site land?

59

Overall Score

KeyForge's privacy policy page is a masterclass in transparency and technical honesty, but it's dressed up like a minimalist art installation that forgot to invite anyone to the gallery opening. The content is stellar; the presentation is aggressively understated.

🔥

The Roast

This page reads like a privacy policy written by someone who's so obsessed with NOT collecting data that they forgot to collect any design inspiration either. It's the digital equivalent of showing up to a party in a tuxedo made of plain cardboard—technically correct, absolutely sincere, but why are you like this? The hero section has more personality than a DMV waiting room, and the numbered list format screams 'I learned web design from a 2003 textbook.' That said, at least it's honest—unlike 99% of the internet, this page actually means what it says.

🎯 Start Here

🔍 SEO
15/100
🎯 Conversion
20/100
🎨 Design & UX
52/100

Google PageSpeed Insights

(Real metrics from Google)

These scores come directly from Google's PageSpeed API. The AI scores above evaluate broader aspects like copy, trust signals, and conversion.

⚡
100
Performance

Core Web Vitals

0.8s
LCP
Largest Contentful Paint
0.00
CLS
Cumulative Layout Shift
🔍 15

SEO

🎯 20

Conversion

🎨 52

Design & UX

♿ 58

Accessibility

🔒 72

Trust Signals

📱 78

Mobile

📝 82

Copy & Messaging

⚡ 95

Performance

🔍

SEO

15/100

This page is an SEO disaster wrapped in a privacy policy—it has a single H1, zero schema markup, a URL that looks like a typo (Privacypolit.html), and meta description that's more marketing than SEO. Google will index it, but it won't rank for anything useful.

Issues Found

  • URL is malformed: 'Privacypolit.html' looks like a typo (should be 'privacy-policy.html' or similar); this hurts both UX and SEO
  • Zero schema markup: no PrivacyPolicy schema, no Organization schema, no structured data to help search engines understand the page
  • Meta description is marketing copy, not a summary: 'KeyForge Privacy Policy — 100% client-side...' reads like a feature list, not a page description

Recommendations

  • Fix URL structure high

    Rename 'Privacypolit.html' to 'privacy-policy.html' or '/privacy/' to match SEO best practices and reduce user confusion.

  • Add PrivacyPolicy schema markup high

    Implement JSON-LD schema for PrivacyPolicy with datePublished, dateModified, and organization details to help search engines understand the page.

  • Rewrite meta description for clarity medium

    Change to 'KeyForge's privacy policy: no data collection, no cookies, no tracking. All processing happens on your device.' (under 160 chars).

🎯

Conversion

20/100

This page has zero conversion goals, zero CTAs, and zero user journey—it's a privacy policy, not a sales page, so that's technically correct. But even privacy policies can guide users back to the main app or encourage trust-building actions, and this one does neither.

Issues Found

  • No clear CTA: the 'Back to KeyForge' link is buried in the header; there's no prominent button encouraging users to return to the app
  • No trust-building actions: no 'View Source Code' CTA (though it's mentioned), no 'Download' button, no 'Try KeyForge' link
  • No conversion funnel: users land here, read the policy, and have no clear next step except manually navigating back

Recommendations

  • Add prominent 'Back to KeyForge' CTA medium

    Add a button-styled CTA at the bottom of the page (after section 7) that says 'Ready to generate secure passwords?' and links back to the app.

  • Make 'Source Code' link more discoverable low

    Change the inline 'Source code ↗' link to a button or card that says 'Verify our code on GitHub' to encourage trust-building verification.

🎨

Design & UX

52/100

The design is clean and functional but painfully utilitarian—it prioritizes information delivery over engagement, resulting in a page that feels more like technical documentation than a modern web experience. The dark hero card with the decorative circle is the only visual flourish, and it's doing all the heavy lifting for a page that otherwise looks like it was designed by someone who thinks CSS is a conspiracy.

Issues Found

  • Monotonous typography hierarchy: numbered sections (1-7) lack visual distinction beyond color, making the page feel like a checklist rather than a narrative
  • Hero card is the only visual element; the rest is plain text on white, creating zero visual rhythm or breathing room
  • No visual separation between sections; content blocks run together with minimal whitespace, reducing scannability

Recommendations

  • Add visual hierarchy with card-based sections medium

    Wrap each numbered section (1-7) in subtle cards with light backgrounds, icons, or left borders to create visual rhythm and improve scannability.

  • Introduce icon system for each policy point medium

    Add small, relevant icons (lock, cookie, chart, server, clipboard, key, document) next to each numbered heading to improve visual scanning and memorability.

  • Increase whitespace and section padding low

    Add 2-3rem vertical margin between sections and increase internal padding to create breathing room and reduce cognitive load.

♿

Accessibility

58/100

The page has basic accessibility features (3 ARIA attributes, footer and header landmarks) but is missing critical elements like skip links, proper heading hierarchy, and color contrast verification. It's accessible enough to not fail an audit, but not accessible enough to be truly inclusive.

Issues Found

  • No skip-to-content link: users must tab through the back button and header before reaching the main content
  • Single H1 with no H2-H6 hierarchy: all 7 sections are numbered but not semantically marked as subheadings, breaking screen reader navigation
  • Color contrast not verified: red text (#D97757 or similar) on white background may fail WCAG AA for body text; orange headings need verification

Recommendations

  • Add skip-to-main-content link high

    Add a visually hidden skip link that jumps to the first section heading, allowing keyboard users to bypass navigation.

  • Implement proper heading hierarchy high

    Change numbered sections to H2 tags (e.g., '<h2>1. NO DATA COLLECTION</h2>') to create a proper outline for screen readers.

  • Verify and fix color contrast medium

    Test red/orange text against white background with WCAG AA standards; adjust colors if needed to meet 4.5:1 contrast ratio for body text.

🔒

Trust Signals

72/100

The page builds trust through technical transparency and honesty—it explains exactly what KeyForge does and doesn't do, which is more credible than most privacy policies. However, it lacks third-party validation, security certifications, or social proof that would amplify that trust.

Issues Found

  • No third-party verification: no security audit badges, no certifications (SOC 2, ISO 27001), no external validation of claims
  • No social proof: no user testimonials, no GitHub stars count, no community indicators that others trust this tool
  • Source code link is mentioned but not prominently featured: users have to read the policy to know they can verify the code themselves

Recommendations

  • Add GitHub stars badge or link medium

    Display a GitHub stars badge or link in the hero section to show community trust and encourage code verification.

  • Highlight third-party verification opportunities medium

    Add a section or callout that says 'Verify our claims: View our source code on GitHub' with a prominent link to encourage trust-building verification.

  • Add security audit or certification badge (if applicable) low

    If KeyForge has undergone any security audits or holds certifications, display them prominently in the hero or footer.

📱

Mobile

78/100

Mobile responsiveness is solid—the layout stacks properly, text is readable, and touch targets are adequate. However, the mobile experience is just a scaled-down version of the desktop with no mobile-specific optimizations or considerations.

Issues Found

  • Hero card is cramped on mobile: the dark card with decorative circle takes up significant vertical space on small screens, pushing content down
  • Inline code snippets (crypto.getRandomValues, localStorage) are not wrapped and may overflow on narrow viewports
  • No mobile-specific navigation: the back button and copy icon are small and could be easier to tap on mobile

Recommendations

  • Optimize hero card for mobile medium

    Reduce hero card height on mobile (< 600px viewport) by removing or repositioning the decorative circle and reducing padding.

  • Wrap code snippets for mobile low

    Add CSS word-break or overflow-wrap to inline code elements to prevent horizontal scrolling on narrow screens.

  • Increase touch target size for header buttons low

    Ensure back button and copy icon are at least 44x44px on mobile for comfortable tapping.

📝

Copy & Messaging

82/100

The copy is refreshingly honest and technically precise—it explains complex privacy concepts in plain language without corporate doublespeak. However, it reads more like a technical spec sheet than persuasive marketing, missing opportunities to emotionally connect with privacy-conscious users.

Issues Found

  • Tone is clinical and defensive rather than confident and reassuring; phrases like 'We guarantee complete non-interference' sound like a legal threat rather than a promise
  • No user benefit framing: the policy explains WHAT KeyForge does but rarely WHY users should care (e.g., 'Your passwords stay private so you control your security')
  • Jargon density in sections 5-6 (crypto.getRandomValues, CSPRNG, Content-Security-Policy) will lose non-technical users despite the overall clarity

Recommendations

  • Reframe guarantees as user benefits high

    Change 'We do not collect, process, or store any personal information' to 'Your passwords never leave your device—only you control them,' shifting from feature to benefit.

  • Add plain-language summaries for technical sections medium

    After sections 5-6, add a 1-sentence plain-English summary (e.g., 'In short: your randomness comes from your browser's built-in security, not from us').

  • Lead with emotional reassurance, not legal language medium

    Replace 'We guarantee complete non-interference' with 'Your privacy is yours alone—we literally can't access it even if we wanted to.'

⚡

Performance

95/100

This page is a performance beast—100 Lighthouse performance score, 0.781s LCP, zero CLS, zero TBT. It's so fast it makes other websites look like they're loading on dial-up. The only reason it's not 100 is that SEO and best practices are being ignored.

Issues Found

  • Perfect performance metrics but no service worker verification visible in the data (though the copy claims one exists)
  • No image optimization needed (zero images), but this also means zero visual richness
  • Mobile performance is excellent but not differentiated from desktop—no mobile-specific optimizations visible

Recommendations

  • Verify service worker caching in production low

    Confirm the service worker is properly registered and caching assets; add a cache version header to prevent stale content.

  • Add performance monitoring low

    Implement Web Vitals tracking (without sending data anywhere) to monitor real-world performance and catch regressions early.

Embed this badge on your site: Roast by AI score badge
HTML
Markdown

Think you can beat 59/100?

Get your site brutally analyzed by the same AI. 8 scores, a punch list of fixes, 60 seconds.