Loading Report View…
0/ 100
claude.ai Website Audit Report
claude.ai scored 63 out of 100 in this SavageAudit website audit covering Performance, SEO, Design, Copy, User Experience, and Conversion. The report uses captured website evidence to explain what is working, what is limiting the experience, and which improvements deserve attention first.
“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/
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.
Where It Burns
6 categoriesWebsite Audit Findings for claude.ai
SavageAudit identified 42 visible findings and recommendations across 6 audit categories. Each section below combines the category score with observed evidence and prioritized fixes.
3301 PERFORMANCELCP 20.8s8302 SEOSEO score 83/1005403 DESIGNHeadings 347704 COPYWord count 4016005 UXConsole errors 17606 CONVERSIONButtons 28
01
PERFORMANCE AUDIT
33
LCP20.8sFCP16.1sInteractive25.4sUnused JS2,343 KiB
- 🔥Your LCP of 20.8 s is not a loading time; it’s a hostage situation.
💀
A gorgeous case of Claude arriving after everyone has already left the meeting.
- →Split the homepage bundle and defer non-critical JavaScript so the first load isn’t carrying a small archive.
- →Inline critical CSS, remove the 59 KiB of unused CSS, and delay render-blocking resources to cut the 450 ms savings gap.
- →Audit the 10 long tasks and move expensive work off the main thread with code splitting, lazy hydration, or workerization.
02
SEO AUDIT
83
SEO score83/100CanonicalmissingRedirects1OG title/descriptionempty
- 🔥Your canonical URL is missing, so search engines get one page and the browser quietly serves another.
💀
SEO is mostly competent, but the missing canonical and awkward login redirect make the signal wobble.
- →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
DESIGN AUDIT
54
Headings34H3 count29Missing alt text5Word count401
- 🔥The page has 34 headings, but it starts at H2, so the hierarchy is already doing interpretive dance.
💀
The visual system exists, but the heading ladder and missing alt text make it feel assembled, not designed.
- →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
COPY AUDIT
77
Word count401Sentence count11CTA count11Repeated CTATry 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.
💀
The copy is polished enough to function, but the repetition and loose details keep it from sounding sharp.
- →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
UX AUDITUSER EXPERIENCE AUDIT
60
Console errors1Broken assets1Redirect count1CLS0
- 🔥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.
💀
The interface is stable once it loads, but the login flow and console noise make the journey feel jittery.
- →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
CONVERSION AUDIT
76
Buttons28CTAs11Form count1Social proof1
- 🔥You’ve got 28 buttons and 11 CTAs, which is less a funnel and more a button buffet.
💀
The conversion path exists, but the page keeps mixing urgency, login friction, and scattered calls to action.
- →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.
Audit overview
claude.ai Audit 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.
Based on the category scores in this report, SEO is the strongest area while Performance has the most room for improvement.
How SavageAudit Evaluated claude.ai
SavageAudit evaluated the public website at https://claude.ai/ across performance, technical SEO, design, copy, user experience, and conversion signals. Scores and recommendations reflect the website evidence available when this audit was generated on April 2, 2026.
Similar Website Audit Reports
Compare this result with other public SavageAudit reports that received a similar overall website score.