Website review, no card needed

anthropic.com logo

anthropic.com website review

Visit site (opens in a new tab)Reviewed 23 October 202631 issues · 73 checks

This review found 31 issues worth fixing on anthropic.com, 10 of them high impact, across 73 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  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
5.6 s844 msMay 2Oct 171.5 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20264.2 s
May 9, 20264.3 s
May 16, 20264.3 s
May 23, 20264.4 s
May 30, 20264.6 s
Jun 6, 20264.8 s
Jun 13, 20264.8 s
Jun 20, 20264.5 s
Jun 27, 20264.3 s
Jul 4, 20264.6 s
Jul 11, 20264.6 s
Jul 18, 20264.8 s
Jul 25, 20265.0 s
Aug 1, 20264.0 s
Aug 8, 20262.8 s
Aug 15, 20261.7 s
Aug 22, 20261.4 s
Aug 29, 20261.4 s
Sep 5, 20261.4 s
Sep 12, 20261.5 s
Sep 19, 20261.6 s
Sep 26, 20261.6 s
Oct 3, 20261.6 s
Oct 10, 20261.5 s
Oct 17, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
104 ms87 msMay 2Oct 1794 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202693 ms
May 9, 202691 ms
May 16, 202693 ms
May 23, 202693 ms
May 30, 202691 ms
Jun 6, 202692 ms
Jun 13, 202689 ms
Jun 20, 202694 ms
Jun 27, 202697 ms
Jul 4, 202696 ms
Jul 11, 2026102 ms
Jul 18, 202699 ms
Jul 25, 202695 ms
Aug 1, 202696 ms
Aug 8, 202696 ms
Aug 15, 202694 ms
Aug 22, 202694 ms
Aug 29, 202694 ms
Sep 5, 202693 ms
Sep 12, 202696 ms
Sep 19, 2026100 ms
Sep 26, 2026100 ms
Oct 3, 202699 ms
Oct 10, 202696 ms
Oct 17, 202694 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 anthropic.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. anthropic.com at 0.6 s0.6 s
  2. anthropic.com at 1.3 s1.3 s
  3. anthropic.com at 1.9 s1.9 s
  4. anthropic.com at 2.5 s2.5 s
  5. anthropic.com at 3.2 s3.2 s
  6. anthropic.com at 3.8 s3.8 s
  7. anthropic.com at 4.4 s4.4 s
  8. anthropic.com at 5.0 s5.0 s

Speed

7 to fix62
  • Reduce unused JavaScript

    2.3 s · 564 KiB

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

  • Render-blocking requests

    1.6 s

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

  • Main-thread work: 4.9 s

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

  • Mobile performance score: 62

    62/100

    Your mobile performance score is 62 (desktop: 73). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    450 ms · 73 KiB

    About 73 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • Improve image delivery

    405 KiB

    4 images could be 405 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Google Tag Manager adds 206 ms

    206 ms

    Google Tag Manager costs a phone 206 ms of main-thread work and 312 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.

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, TikTok and Hubspot and others), adding 560 KiB and 340 ms of main-thread time.

  • 8 long tasks on the main thread

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

  • Use efficient cache lifetimes

    43 KiB

    2 files are served with short cache lifetimes, so returning visitors download them again (43 KiB).

  • Minify JavaScript

    20 KiB

    20 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    14 KiB

    Polyfills for old browsers add 14 KiB JavaScript that modern phones do not need.

  • 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: 9 ms

    9 ms

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

Core Web Vitals

7 to fix100
  • 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.

  • Largest Contentful Paint: 15.2 s

    15.2 s

    Your largest element takes 15.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “AI research and products that put safety at the frontier. A…”.

  • Time to Interactive: 23.3 s

    23.3 s

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

  • Speed Index: 7.4 s

    7.4 s

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

  • Real-user TTFB: 844 ms

    844 ms

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • Total Blocking Time: 241 ms

    241 ms

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

  • Tap response (INP) held steady for real visitors

    +3%

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

6 checks passed
  • Real-user LCP: 1.4 s

    1.4 s

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

  • Real-user INP: 86 ms

    86 ms

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

  • 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 FCP: 1.4 s

    1.4 s

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

  • Largest content (LCP) got 64% faster for real visitors

    -64%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix33
  • Page weight: 4.7 MB in 91 requests

    4.7 MB

    Your homepage downloads 4.7 MB in 91 requests on a phone: images 2.1 MB (7), scripts 1.5 MB (53) and fonts 875 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • About 1.3 g of CO₂ per visit

    1.33 g

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

Accessibility

1 to fixGoogle 10099
  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 4 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

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

SEO

3 to fixGoogle 9287
  • Title is short (16 characters)

    Your title is only 16 characters: “Home \ Anthropic”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 28 internal links, 5 external

    The homepage links to 28 pages on anthropic.com and 5 external pages.

6 checks passed
  • Meta description: 121 characters

    Your meta description is 121 characters: “Anthropic is an AI safety and research company that's working to build reliable, interpretable, and steerable AI system…”.

  • One H1 headline

    Your main headline reads: “AI research and products that put safety at the frontier. AI will have a vast impact on the world. Anthropic is a publi…”.

  • Canonical URL set

    The canonical URL is https://www.anthropic.com/.

  • 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://www.anthropic.com/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://www.anthropic.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.

2 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.

  • Text is in the HTML

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

Other pages

5 to fix69
  • 3 pages without a title

    https://www.anthropic.com/document/claude-haiku-5-5-system-card, https://www.anthropic.com/document/claude-sonnet-5-5-system-card and https://www.anthropic.com/document/claude-opus-5-5-system-card have no <title>, so Google invents the link text in results.

  • 3 pages without a meta description

    https://www.anthropic.com/document/claude-haiku-5-5-system-card, https://www.anthropic.com/document/claude-sonnet-5-5-system-card and https://www.anthropic.com/document/claude-opus-5-5-system-card have no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages share a meta description

    https://www.anthropic.com/news, https://www.anthropic.com/news/announcements, https://www.anthropic.com/institute, https://www.anthropic.com/research/team/alignment and https://www.anthropic.com/constitution use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.anthropic.com/public-benefit-charter, whose canonical is https://www.anthropic.com/public-benefit-report. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 3 pages without an H1

    https://www.anthropic.com/document/claude-haiku-5-5-system-card, https://www.anthropic.com/document/claude-sonnet-5-5-system-card and https://www.anthropic.com/document/claude-opus-5-5-system-card have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

2 to fixGoogle 9287
  • 13 small tap targets

    13 of 25 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Loading the script 'https://js.hsadspixel.net/pixels.js' violates the following Content Security Policy directive: "scr…”.

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix60
  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 339 words of copy

    The homepage carries about 339 words of visible text.

2 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Try Claude”.

  • 2 calls to action

    The homepage has 2 calls to action, for example “Try Claude” and “Learn more”.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Tag Manager, HubSpot and TikTok Pixel (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 7 cookies set on arrival

    7

    Opening the homepage sets 7 cookies (measured from a US location before any click).

  • No consent tool detected

    No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

  • 7 other companies contacted

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

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 anthropic.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

Hiring

Hiring
667 open roles
Teams
Sales (109), AI Research & Engineering (65), Applied AI (53), Finance (49)
Job board
greenhouse

Company

Employees
2,500
Founded
2021
Headquarters
San Francisco

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on anthropic.com, including 14 speed issues, 3 SEO issues and 3 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