Asana Website Analysis

“Touch targets are too small, keyboard navigation is broken, and your main content landmark is MIA.”

You're missing a proper `<main>` landmark—this absolutely tanks accessibility for screen readers and structural semantics. Your touch targets don't meet WCAG standards, meaning mobile users (50%+ of traffic) are accidentally clicking the wrong buttons. You have aria-hidden elements containing focusable descendants (a11y disaster), and 880ms First Input Delay means even after the page loads, it feels sluggish when people try to interact. The 54 Best Practices score reflects lazy implementation of fundamentals. Fix this by: (1) Adding semantic HTML (`<main>`, `<header>`, `<nav>`), (2) Ensuring touch targets are 44x44px minimum, (3) Testing with keyboard-only navigation, (4) Removing aria-hidden from interactive elements.

“Your SEO is basically perfect, which makes your performance score even more embarrassing.”

H1 tag is present and sensible, OG tags are dialed in, internal linking architecture is robust with 226 internal links showing strong site hierarchy, and your heading structure (H2s and H3s) is logical. You're doing everything a technical SEO specialist would high-five you for. This is the one area where you're genuinely crushing it. Don't change a thing here—seriously.

“Your copy is vague enough to fit a fortune cookie.”

'Supercharge your teams with AI that gets work done' could apply to literally any SaaS tool made in the last 6 months. Where's the specificity? What actually *is* Asana's competitive advantage? Your meta description is solid, but your value prop on the page reads like a Mad Libs game. Tell me what problems you solve—not what you dream about. Include concrete use cases, numbers, or customer outcomes instead of motivational poster language.

“Your visual design is chef's kiss, but your performance is giving 'dial-up modem energy.'”

The design itself is modern, clean, and visually cohesive—excellent use of whitespace and that coral accent color. Your 124 images are all properly alt-tagged, which is *chef's kiss* for accessibility. But here's the problem: you're loading all of them like a Russian nesting doll of asset bloat. Your LCP is 49.5 seconds. That's longer than it takes to microwave popcorn. Users are bouncing before they see your beautiful design, which is like spending $10k on a wedding dress and showing up 2 hours late.

“Your performance metrics read like a cry for help from the JavaScript Gods.”

A 49.5s LCP is genuinely catastrophic—users expect content in under 3 seconds. You're running 101 external scripts, which is like inviting 101 people to your dinner party and wondering why nobody can move. Your Time to Interactive is bottlenecked, font display is broken (users are seeing blank screens), and you have massive unused JavaScript bloat. Start by: (1) Lazy-load images and defer non-critical JavaScript, (2) Implement proper font-display CSS (swap or optional), (3) Audit and kill those 101 external scripts—you probably don't need 80% of them, (4) Use a performance budget and enforce it in CI/CD.