Website review, no card needed

Discord logo

discord.com website review

Visit site (opens in a new tab)Reviewed 11 October 202625 issues · 75 checks

This review found 25 issues worth fixing on discord.com, 13 of them high impact, across 75 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

Read the full growth playbook for Discord

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
8.2 s7.2 sApr 18Oct 38.1 s
Show as table
DateReal-visitor load time (LCP)
Apr 18, 20267.5 s
Apr 25, 20267.4 s
May 2, 20267.3 s
May 9, 20267.3 s
May 16, 20267.3 s
May 23, 20267.3 s
May 30, 20267.4 s
Jun 6, 20267.4 s
Jun 13, 20267.5 s
Jun 20, 20267.7 s
Jun 27, 20268.0 s
Jul 4, 20268.1 s
Jul 11, 20268.1 s
Jul 18, 20267.8 s
Jul 25, 20267.5 s
Aug 1, 20267.5 s
Aug 8, 20267.4 s
Aug 15, 20267.4 s
Aug 22, 20267.5 s
Aug 29, 20267.6 s
Sep 5, 20267.8 s
Sep 12, 20268.0 s
Sep 19, 20268.1 s
Sep 26, 20268.1 s
Oct 3, 20268.1 s
Real-visitor tap response (INP)75th percentile, phones
450 ms400 msApr 18Oct 3407 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 2026441 ms
Apr 25, 2026429 ms
May 2, 2026420 ms
May 9, 2026411 ms
May 16, 2026412 ms
May 23, 2026418 ms
May 30, 2026427 ms
Jun 6, 2026436 ms
Jun 13, 2026440 ms
Jun 20, 2026443 ms
Jun 27, 2026444 ms
Jul 4, 2026443 ms
Jul 11, 2026441 ms
Jul 18, 2026437 ms
Jul 25, 2026432 ms
Aug 1, 2026424 ms
Aug 8, 2026419 ms
Aug 15, 2026412 ms
Aug 22, 2026406 ms
Aug 29, 2026406 ms
Sep 5, 2026408 ms
Sep 12, 2026409 ms
Sep 19, 2026409 ms
Sep 26, 2026410 ms
Oct 3, 2026407 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of discord.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. discord.com at 0.8 s0.8 s
  2. discord.com at 1.6 s1.6 s
  3. discord.com at 2.3 s2.3 s
  4. discord.com at 3.1 s3.1 s
  5. discord.com at 3.9 s3.9 s
  6. discord.com at 4.7 s4.7 s
  7. discord.com at 5.5 s5.5 s
  8. discord.com at 6.2 s6.2 s

Speed

12 to fix33
  • Use efficient cache lifetimes

    5.1 s · 39.8 MB

    44 files are served with short cache lifetimes, so returning visitors download them again (39.8 MB).

  • Render-blocking requests

    7.5 s

    5 files block the first paint until they finish downloading. Deferring or inlining them could save about 7.5 s.

  • Reduce unused CSS

    2.3 s · 473 KiB

    About 473 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.3 s faster on a phone.

  • Reduce unused JavaScript

    1.9 s · 653 KiB

    About 653 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.

  • Mobile performance score: 33

    33/100

    Your mobile performance score is 33 (desktop: 48). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 8 third-party services on the page

    8 third-party services load with your homepage (website-files.com, Google Tag Manager and cloudfront.net and others), adding 11.9 MB and 1.1 s of main-thread time.

  • website-files.com adds 728 ms

    728 ms

    website-files.com costs a phone 728 ms of main-thread work and 11.4 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Improve image delivery

    150 ms · 264 KiB

    10 images could be 264 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • Main-thread work: 3.8 s

    A phone's processor spends 3.8 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 13 long tasks on the main thread

    13 long tasks block the main thread while loading, the longest for 372 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    300 ms · 42 KiB

    Polyfills for old browsers add 42 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

  • Google Tag Manager adds 281 ms

    281 ms

    Google Tag Manager costs a phone 281 ms of main-thread work and 352 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 3 ms

    3 ms

    Your server sent the HTML in 3 ms, well inside Google's 600 ms guideline.

Core Web Vitals

8 to fix67
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • First Contentful Paint: 8.0 s

    8.0 s

    The first text or image appears after 8.0 s on a phone. Good is under 1.8 s.

  • Largest Contentful Paint: 19.5 s

    19.5 s

    Your largest element takes 19.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “GROUP CHAT THAT’S ALL FUN & GAMES Discord is great for play…”.

  • Time to Interactive: 19.7 s

    19.7 s

    The page becomes fully interactive after 19.7 s. Good is under 3.8 s.

  • Speed Index: 8.4 s

    8.4 s

    Visually, the page fills in at 8.4 s (Speed Index). Good is under 3.4 s.

  • Total Blocking Time: 1.2 s

    1.2 s

    Scripts block taps and scrolling for 1.2 s in total while the page loads. Good is under 200 ms.

  • Real-user INP: 352 ms

    352 ms

    Real visitors wait 352 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user FCP: 2.1 s

    2.1 s

    Real visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.

  • Tap response (INP) held steady for real visitors

    -6%

    Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 441 ms to 407 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    +8%

    Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 7.5 s to 8.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

4 checks passed
  • Real-user LCP: 2.5 s

    2.5 s

    Real visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user CLS: 0.02

    0.02

    For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.

  • Real-user TTFB: 461 ms

    461 ms

    Real visitors wait 461 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Cumulative Layout Shift: 0.03

    0.03

    The layout barely moves while loading (CLS 0.03, good is under 0.1).

Images and page weight

1 to fix70
  • Page weight: 44.1 MB in 121 requests

    44.1 MB

    Your homepage downloads 44.1 MB in 121 requests on a phone: media 40.1 MB (22), scripts 1.6 MB (25) and images 1.1 MB (52). Under 2 MB keeps phones on slow connections fast.

  • 2 images in older formats

    2 images (220 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • 1 image below the first screen load straight away

    1 image further down the page (22 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 12.5 g of CO₂ per visit

    12.51 g

    By the Sustainable Web Design model, a visit to your homepage emits about 12.51 g of CO₂e: 1500.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

Google 100100
2 checks passed
  • Every image has alt text

    All 171 images in the HTML carry an alt attribute.

  • 38 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 38 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 0 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

Google 100100
  • 107 internal links, 24 external

    The homepage links to 107 pages on discord.com and 24 external pages.

8 checks passed
  • Meta description: 155 characters

    Your meta description is 155 characters: “Discord is great for playing games and chilling with friends, or even building a worldwide community. Customize your ow…”.

  • One H1 headline

    Your main headline reads: “Group chat that’s all fun & games”.

  • Title: 43 characters

    Your title is a healthy 43 characters: “Discord - Group Chat That’s All Fun & Games”.

  • Canonical URL set

    The canonical URL is https://discord.com/.

  • Structured data in place

    Structured data found: Organization, WebPage and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://discord.com/servers/servers-sitemap-index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://discord.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (682 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 48 found) and read each the way a search engine does.

7 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 8891
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Executing inline script violates the following Content Security Policy directive 'script-src 'self' 'unsafe-inline' 'no…”.

  • 3 distorted images

    3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    5 of 5 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix70
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 315 words of copy

    The homepage carries about 315 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Download for Linux”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Download”, “Submit a Request” and “Download for Windows”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 10 cookies set on arrival

    10

    Opening the homepage sets 10 cookies, 1 of them by other companies (measured from a US location before any click).

  • 10 other companies contacted

    Loading the homepage contacts 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at discord.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
Webflow
Analytics
Google Tag Manager

Hiring

Hiring
49 open roles
Teams
Product Engineering (10), Developers (8), Data Science & Engineering (7), Product Design (7)
Job board
greenhouse

Company

Founded
2015

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on discord.com, including 20 speed issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25