Discord Website Analysis

“Accessibility is flawless, but users abandon ship before they see anything.”

You nailed accessibility (100/100) with perfect alt text and semantic HTML—genuinely impressive. The problem is nobody sticks around long enough to experience it. A 310ms First Input Delay means even simple interactions feel sluggish, and an 18.9-second LCP is a user abandonment time bomb. Your best practices score (69/100) and browser console errors (0/100) indicate technical debt piling up in the basement. The experience on fast networks might be okay, but on 3G? Your site is a cruel joke. Prioritize perceived performance: show skeleton screens, lazy-load below-the-fold content, and consider moving to a lightweight frontend framework or static generation.

“Perfect SEO score—you've hired someone who actually reads documentation.”

Your title, meta description, heading hierarchy, and link structure are textbook SEO done right. The H1 matches intent, H2s organize content logically, and you've got 106 internal links creating a coherent information architecture. This is the one category where you're not embarrassing yourself. Seriously, whoever handles SEO gets a raise and a juice box.

“Your messaging is fun but speaks to 17-year-olds, not the enterprise teams paying your bills.”

The copy has personality—'all fun & games' and 'chill with friends' absolutely nails the brand voice for Gen Z. Problem: you've got exactly one CTA visible, buried like a Schrute beet in a corn field, and your value proposition shifts between 'gaming' and 'worldwide communities' without committing. H2s like 'MAKE YOUR GROUP CHATS MORE FUN' are shouty all-caps energy that belonged in 2015. Dial it back 15% and add concrete benefits beyond vibes.

“Visually competent but drowning in 170 images like a hoarder who discovered JPEGs.”

Your visual hierarchy is solid and the brand identity reads clearly, but you're hauling 170 images across the wire like you're running a digital art museum. Yes, alt text is perfect (chef's kiss on accessibility), but quantity over optimization is killing your load times. Consider lazy loading, WebP conversion, and asking yourself: 'Do I really need 170 images to explain chat software?' The answer is no. 170 is the speed of a sloth, not a Discord user.

“An 18.9-second LCP is what happens when you treat JavaScript like unlimited breadsticks.”

Your Lighthouse scores read like a performance car that only runs in reverse: 36 overall with a Time to Interactive of 3/100. You're bleeding performance across every metric—render-blocking requests, unused CSS (0/100), unused JavaScript (0/100), and main-thread work that's getting an existential crisis. 20 external scripts is 19 too many. Your Speed Index at 14/100 suggests users are watching a loading spinner more than your actual content. This needs a code audit ASAP: eliminate render blockers, defer non-critical JS, and tree-shake that unused code like your site depends on it (it does).