Skip to main content

tinder.com

https://tinder.com/@watadawg

Completed

Curious how yours stacks up?

tinder.com scored 17/100. Where would your site land?

17

Overall Score

This is a Tinder profile page that's basically a JavaScript-dependent wasteland masquerading as a web experience. Scott's profile loads with a loading spinner and a "Log in to like me" CTA, but the page suffers from catastrophic performance issues, accessibility failures, and a mobile experience that would make a UX designer weep into their energy drink.

🔥

The Roast

Scott, buddy—your profile page loads slower than you probably text back, with a Core Web Vitals score that screams 'I was built by someone who thinks CSS and JavaScript are the same thing.' The page is 46% performant on mobile (nice participation trophy), has zero SEO optimization, and requires JavaScript just to display a picture of your hot rod restoration hobby. It's like showing up to a first date with a loading spinner instead of your personality. Even the image is missing alt text, which means screen readers can't see you either—at least SOMEONE has standards.

🎯 Start Here

🔍 SEO
5/100
♿ Accessibility
8/100
⚡ Performance
12/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.

⚡
46
Performance

Core Web Vitals

8.4s
LCP
Largest Contentful Paint
0.01
CLS
Cumulative Layout Shift
666ms
TBT
Total Blocking Time
🔍 5

SEO

♿ 8

Accessibility

⚡ 12

Performance

📝 15

Copy & Messaging

📱 18

Mobile

🎯 22

Conversion

đź”’ 24

Trust Signals

🎨 28

Design & UX

🔍

SEO

5/100

The SEO score of 0 is telling: meta tags are generic ('Scott (@watadawg) is on Tinder'), there's zero heading hierarchy (only 1 h3), and the entire page content is hidden behind JavaScript—completely unfriendly to search engines.

Issues Found

  • Meta description and OG tags are boilerplate—they could apply to ANY Tinder profile, offering zero SEO differentiation
  • Single h3 heading with no h1 or h2—broken heading hierarchy fails SEO best practices
  • Content hidden behind JavaScript—search engines can't index profile details (bio, interests, photos, age, verification badges)

Recommendations

  • Add proper heading hierarchy high

    Implement h1 (Scott's name) followed by h2 (interests/bio sections) to establish semantic structure that search engines can parse.

  • Server-render profile content high

    Include profile bio, interests, and verification status in initial HTML so crawlers can index the actual profile data instead of just the framework.

  • Write descriptive meta tags medium

    Create unique meta description and OG tags that highlight Scott's age, interests ('44-year-old hot rod enthusiast near Berlin') to improve click-through rates.

♿

Accessibility

8/100

With only 3 ARIA attributes, no skip link, and a missing image alt text, this page is an accessibility catastrophe—screen reader users will hear 'loading spinner' and silence, then navigate a blank profile card with no context.

Issues Found

  • Missing alt text on profile image—screen readers announce 'image' with no meaningful description of Scott or profile content
  • No skip link to main content—users with keyboard navigation must tab through header menu before reaching profile
  • Minimal ARIA attributes (only 3)—loading state, profile container, and interactive elements lack proper semantic roles and labels

Recommendations

  • Add descriptive alt text to images high

    Replace missing alt with 'Scott, 44, verified Tinder member with hot rod restoration interests' so screen readers provide profile context.

  • Implement skip-to-content link high

    Add a visually hidden but keyboard-accessible link at the top that jumps directly to the profile card, bypassing the header navigation.

  • Enhance ARIA markup medium

    Add aria-label to loading spinner ('Loading profile'), aria-live regions for asynchronous content updates, and proper roles for interactive buttons.

⚡

Performance

12/100

This page is a performance dumpster fire: mobile performance score of 46%, LCP of 8.16s (should be <2.5s), CLS of 1.0 (should be <0.1), and 335ms INP. The site is bloated with unused CSS/JS that's strangling performance.

Issues Found

  • LCP of 8.16s is catastrophically slow—users see a blank/loading state for 8+ seconds before main profile image appears
  • CLS of 1.0 indicates massive layout shift (expected 0.1 or lower)—content is likely jumping around after initial load, destroying user experience
  • Unused CSS and JavaScript reducing performance—the bundle is carrying dead weight that should be eliminated or lazy-loaded

Recommendations

  • Optimize Largest Contentful Paint (LCP) high

    Pre-render profile image in initial HTML with appropriate aspect ratio to eliminate loading delay; ensure image is responsive and optimized for mobile.

  • Fix Cumulative Layout Shift (CLS) high

    Reserve space for all interactive elements (CTA button, image container) so the layout doesn't reflow after JavaScript execution.

  • Audit and remove unused CSS/JS high

    Run webpack-bundle-analyzer to identify unused dependencies; split code so authentication UI loads separately from profile display.

📝

Copy & Messaging

15/100

The only visible copy is "Log in to like me" (weak CTA) and a privacy notice that screams legal compliance theater, with zero personality or storytelling about Scott's profile.

Issues Found

  • CTA is generic and transactional—'Log in to like me' has zero emotional appeal or value proposition
  • No headline, bio, or descriptive content—the profile is content-bankrupt before authentication
  • Privacy notice dominates the mobile viewport instead of profile content—poor content prioritization

Recommendations

  • Write compelling profile headline high

    Replace generic CTA with a personality-driven headline (e.g., 'Scott: Hot Rod Restoration Enthusiast') that appears server-side.

  • Add visible bio/interests preview high

    Display 2-3 key interests or bio snippet before login to give viewers a reason to engage (e.g., 'Loves cars, coffee, and conversations').

  • Deprioritize privacy notice medium

    Move privacy consent banner below the fold so profile content takes center stage.

📱

Mobile

18/100

Mobile experience is a disaster: 46% performance score, privacy notice dominates the viewport instead of profile content, and the loading spinner takes up precious mobile screen real estate with zero payoff.

Issues Found

  • Privacy consent banner occupies 40%+ of mobile viewport—content prioritization is backwards (legal > profile)
  • Loading spinner is large and prominent—screams 'this app is slow' before any real content appears
  • Profile image container appears blank/unresponsive until JavaScript executes—users see a broken state on slow 4G networks

Recommendations

  • Move cookie banner below profile high

    Prioritize profile image and bio for mobile—push privacy notice to bottom or into a sticky footer so it doesn't block content.

  • Implement responsive image with proper sizing high

    Use srcset and sizes attributes to deliver optimized images for mobile (320px, 400px viewports); add explicit width/height to prevent layout shift.

  • Optimize viewport and touch targets medium

    Ensure buttons (CTA) have 44+ px touch target height/width; use mobile-first layout that displays profile content first, auth UI second.

🎯

Conversion

22/100

The conversion funnel is basically 'see blank profile → click 'Log in to like me' → get redirected to login'—there's zero persuasion, no social proof, and the CTA is the only interactive element visible, making it conversion-hostile.

Issues Found

  • Single CTA has zero context—users don't see WHY they should like Scott, what his interests are, or what makes him interesting
  • No social proof (verified badges, mutual interests, common connections)—visible only after authentication, which defeats persuasion-before-commitment
  • Conversion funnel is broken—the page's job is to make Scott's profile appealing, but it hides all appealing content behind a login wall

Recommendations

  • Display verification badges prominently high

    Show 'Selfie Verified' and 'ID & DOB Verified' badges on the public profile so visitors see trust signals before login.

  • Add interest preview before CTA high

    Display 'Hot Rod Restoration' and 2-3 key interests above the 'Log in to like me' button to give users a reason to convert.

  • Improve CTA messaging medium

    Change 'Log in to like me' to 'See Scott's profile' or 'Start swiping'—more action-oriented and less presumptive.

đź”’

Trust Signals

24/100

Verification badges (selfie verified, ID/DOB verified) exist in the data but are completely invisible on the public profile—they're hidden behind authentication, which defeats the entire purpose of trust signals.

Issues Found

  • Verification badges are hidden from public view—users have no way to assess credibility before logging in
  • No visible social proof (mutual matches, profile views, interaction counts)—can't assess popularity or authenticity
  • No security indicators visible—HTTPS (likely present) is not communicated; Tinder's safety features are not mentioned

Recommendations

  • Show verification badges on public profile high

    Display 'Selfie Verified' and 'ID & DOB Verified' checkmarks next to Scott's name to establish credibility without login.

  • Add Tinder safety messaging medium

    Include small text badge ('Verified on Tinder' or 'ID Verified') to reinforce that this is a legitimate, safe profile.

  • Consider displaying interaction metrics (if appropriate) low

    Show 'Recently active' status or mutual connection count (if the user has matches in common) to demonstrate genuine engagement.

🎨

Design & UX

28/100

The design is a minimalist nightmare: a loading spinner, a blurry profile image container, and a single CTA button constitute the entire visible experience, with zero context or profile information displayed before login.

Issues Found

  • Loading spinner is the primary visual element—creates impression of incompleteness or technical failure
  • Profile card is completely empty/blank until JavaScript loads and user authenticates—zero visual hierarchy or content preview
  • No profile bio, interests, or descriptive content visible without authentication—defeats the purpose of a shareable web profile

Recommendations

  • Show profile preview without login high

    Display Scott's basic info (name, age, interests, photos) server-side so the profile is immediately visible and shareable without requiring JavaScript execution.

  • Replace loading spinner with actual content high

    Pre-render profile content as HTML instead of relying on client-side JavaScript to hydrate empty DOM nodes.

  • Improve visual hierarchy and spacing medium

    Add breathing room between the profile image, bio section, and CTA—current layout is cramped and uninviting.

Think you can beat 17/100?

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