SINGLE URL ROAST
https://claude.ai/ “Smart AI, but the homepage is stuck in traffic and lost its sign.” Claude’s homepage has the confidence of a keynote and the patience of a dial-up modem. It talks like a sleek product, then makes you wait long enough to question your life choices.
https://claude.ai/ screenshot TECHNICAL SUMMARY The page is technically crawlable and the SEO basics mostly exist, but the experience falls apart under weight. Performance is the real villain: LCP is 20.8 s, FCP is 16.1 s, Interactive is 25.4 s, and the page ships 5,074 KiB with 2,343 KiB of unused JavaScript plus 59 KiB of unused CSS. SEO is mostly healthy, but the missing canonical and the redirect from / to /login muddy the signal, while the empty OG title and description leave social sharing looking unfinished.
Categories 6 categories AI Visibility Ready Rewrite Owner only Share Share link 02
SEO score 83/100 Canonical missing Redirects 1 OG title/description empty
🔥 Your canonical URL is missing, so search engines get one page and the browser quietly serves another.Show 3 more roasts 💀 SEO is mostly competent, but the missing canonical and awkward login redirect make the signal wobble.
Priority Fixes (3) → Add a self-referencing canonical tag on https://claude.ai/ so indexing signals stop freelancing.
→ Keep the public homepage at a stable URL and avoid sending root traffic straight to /login unless that’s truly the intended entry point.
→ Fill in og:title and og:description with concise, shareable copy so previews don’t show up like an empty chair at the table.
03
Headings 34 H3 count 29 Missing alt text 5 Word count 401
🔥 The page has 34 headings, but it starts at H2, so the hierarchy is already doing interpretive dance.Show 3 more roasts 💀 The visual system exists, but the heading ladder and missing alt text make it feel assembled, not designed.
Priority Fixes (3) → Start with a true H1, then reorganize the sections so H2 and H3 levels follow a clean, readable progression.
→ Add descriptive alt text to all six images, especially the five currently missing it, so the design works for everyone.
→ Reduce heading fragmentation by merging redundant sections and using fewer, stronger blocks with clearer visual hierarchy.
04
Word count 401 Sentence count 11 CTA count 11 Repeated CTA Try Claude ×4
🔥 401 words and 11 sentences is lean, but the page still repeats ‘Try Claude’ four times like it’s trying to win by volume.Show 3 more roasts 💀 The copy is polished enough to function, but the repetition and loose details keep it from sounding sharp.
Priority Fixes (3) → Rewrite the primary CTA set so each placement has a distinct job instead of repeating ‘Try Claude’ everywhere.
→ Tighten the headline and supporting copy around one clear promise, then remove any duplicate phrasing that adds noise.
→ Correct the copyright year to the current year so the page stops looking like it borrowed tomorrow’s calendar by accident.
05
Console errors 1 Broken assets 1 Redirect count 1 CLS 0
🔥 A console error from accounts.google.com/gsi/client shows FedCM throwing a TypeError, which is a rough first handshake for a login-heavy page.Show 3 more roasts 💀 The interface is stable once it loads, but the login flow and console noise make the journey feel jittery.
Priority Fixes (3) → Fix the Google Identity Services FedCM error so the login flow doesn’t start by tripping over itself.
→ Resolve the ORB-blocked Datadog request or adjust the reporting setup so monitoring doesn’t masquerade as a broken asset.
→ Remove unnecessary root-to-login friction by making the destination explicit earlier in the flow or clarifying the purpose of the redirect.
06
Buttons 28 CTAs 11 Form count 1 Social proof 1
🔥 You’ve got 28 buttons and 11 CTAs, which is less a funnel and more a button buffet.Show 3 more roasts 💀 The conversion path exists, but the page keeps mixing urgency, login friction, and scattered calls to action.
Priority Fixes (3) → Reduce the CTA set to one primary action and one secondary action so the page stops arguing with itself.
→ Add stronger social proof near the main conversion point, such as customer logos, quantified outcomes, or concise testimonials.
→ If login is the goal, make that pathway explicit and remove competing paths that dilute intent before the user commits.
