Website review, no card needed

mindmed.co logo

mindmed.co website review

Visit site (opens in a new tab)Reviewed 21 October 202628 issues · 101 checks

This review found 28 issues worth fixing on mindmed.co, 3 of them high impact, across 101 checks. The most urgent: page weight: 14.9 MB in 115 requests. 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
1.2 s805 msMay 2Oct 171.1 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.1 s
May 9, 20261.1 s
May 16, 20261.0 s
May 23, 2026910 ms
May 30, 20261.0 s
Jun 6, 20261.0 s
Jun 13, 2026974 ms
Jun 20, 20261.1 s
Jun 27, 2026847 ms
Jul 4, 2026850 ms
Jul 11, 2026862 ms
Jul 18, 2026849 ms
Jul 25, 2026950 ms
Aug 1, 2026906 ms
Aug 8, 2026919 ms
Aug 15, 2026868 ms
Aug 22, 2026886 ms
Aug 29, 2026885 ms
Sep 5, 2026853 ms
Sep 12, 2026958 ms
Sep 19, 2026916 ms
Sep 26, 2026931 ms
Oct 3, 2026970 ms
Oct 10, 2026981 ms
Oct 17, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
98 ms82 msMay 2Oct 1795 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202691 ms
May 9, 202693 ms
May 16, 202692 ms
May 23, 202687 ms
May 30, 202687 ms
Jun 6, 202687 ms
Jun 13, 202684 ms
Jun 20, 202687 ms
Jun 27, 202688 ms
Jul 4, 202688 ms
Jul 11, 202689 ms
Jul 18, 202690 ms
Jul 25, 202695 ms
Aug 1, 202696 ms
Aug 8, 202696 ms
Aug 15, 202694 ms
Aug 22, 202691 ms
Aug 29, 202690 ms
Sep 5, 202690 ms
Sep 12, 202687 ms
Sep 19, 202687 ms
Sep 26, 202688 ms
Oct 3, 202689 ms
Oct 10, 202692 ms
Oct 17, 202695 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

Live view · interaction off

Speed

8 to fix79
  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, quotemedia.com and Vimeo and others), adding 14.3 MB and 757 ms of main-thread time.

  • Vimeo adds 125 ms

    125 ms

    Vimeo costs a phone 125 ms of main-thread work and 13.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.

  • Mobile performance score: 79

    79/100

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

  • Reduce unused JavaScript

    605 KiB

    About 605 KiB of JavaScript is downloaded but never used on this page.

  • Google Tag Manager adds 371 ms

    371 ms

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

  • quotemedia.com adds 246 ms

    246 ms

    quotemedia.com costs a phone 246 ms of main-thread work and 538 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.

  • Main-thread work: 3.0 s

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

  • 11 long tasks on the main thread

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

  • Reduce unused CSS

    63 KiB

    About 63 KiB of CSS is downloaded but never applied on this page.

  • Use efficient cache lifetimes

    48 KiB

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

  • Legacy JavaScript

    10 KiB

    Polyfills for old browsers add 10 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.

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 6 ms

    6 ms

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

Core Web Vitals

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

  • Time to Interactive: 15.6 s

    15.6 s

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

  • Real-user LCP: 2.6 s

    2.6 s

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

  • Total Blocking Time: 564 ms

    564 ms

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

  • Speed Index: 4.9 s

    4.9 s

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

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

  • Tap response (INP) held steady for real visitors

    +2%

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

  • Largest content (LCP) held steady for real visitors

    -6%

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

6 checks passed
  • Real-user INP: 112 ms

    112 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 0.7 s

    0.7 s

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

  • Real-user TTFB: 545 ms

    545 ms

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

  • Largest Contentful Paint: 2.3 s

    2.3 s

    Your largest element renders in 2.3 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Forging a New Era of Psychiatry”.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 14.9 MB in 115 requests

    14.9 MB

    Your homepage downloads 14.9 MB in 115 requests on a phone: other files 12.8 MB (32), scripts 1.3 MB (43) and images 424 KiB (24). Under 2 MB keeps phones on slow connections fast.

  • About 4.2 g of CO₂ per visit

    4.23 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

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

Accessibility

1 to fixGoogle 9899
  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 11 images in the HTML carry an alt attribute.

  • 40 automated accessibility rules passed

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

SEO

1 to fixGoogle 9298
  • 4 links with vague text

    4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 31 internal links, 20 external

    The homepage links to 31 pages on mindmed.co and 20 external pages.

8 checks passed
  • Meta description: 145 characters

    Your meta description is 145 characters: “Definium Therapeutics (Formerly MindMed) is forging a new era in psychiatry by harnessing the full therapeutic potentia…”.

  • One H1 headline

    Your main headline reads: “Forging a New Era of Psychiatry”.

  • Title: 63 characters

    Your title is a healthy 63 characters: “Definium Therapeutics (Formerly MindMed) | Psychedelic Medicine”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, 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://definiumtx.com/sitemap_index.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes /llms.txt (3 KiB, 34 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 3 pages without a meta description

    /insights, /research-development and /pipeline have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

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

  • 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

4 to fixGoogle 5483
  • 3 third-party cookies

    3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 1 small tap target

    1 of 5 tappable elements near the top of the page is smaller than 24 px, hard to hit with a thumb.

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “%c%d font-size:0;color:transparent NaN”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Security and trust

1 to fix93
  • No Content-Security-Policy

    No Content-Security-Policy header, the main browser-side defence against injected scripts.

  • No clickjacking protection

    Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

  • No Referrer-Policy

    No Referrer-Policy header, so full URLs can leak to the sites you link to.

  • No Permissions-Policy

    No Permissions-Policy header to switch off camera, microphone and location for embedded content.

  • No security.txt

    There is no /.well-known/security.txt telling researchers how to report a security problem to you.

6 checks passed
  • Served over HTTPS

    The homepage is served over HTTPS (definiumtx.com).

  • Valid certificate (86 days left)

    The certificate from Google Trust Services · WE1 verifies for mindmed.co and is valid for another 86 days.

  • HSTS enabled

    Strict-Transport-Security is set, so browsers always use https.

  • http:// redirects to https

    http://mindmed.co redirects to the secure version.

  • HTTP/2 and HTTP/3

    The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.

  • All 38 links work

    All 38 links checked from your homepage (21 internal, 17 external) answered without errors; 1 did not answer within 5 s.

Domain and trust

  • No CAA record

    definiumtx.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

  • DNSSEC is off

    definiumtx.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

2 checks passed
  • Domain is 1 year old

    1 year

    definiumtx.com was registered in Jul 2025 through MarkMonitor Inc.. An established domain carries more trust with email providers and search engines.

  • Registered until Jul 2029

    definiumtx.com is registered until Jul 2029.

Content and conversion

4 to fix71
  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

    Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

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

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 957 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: “Learn More”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Contact Us” and “Learn More”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Meta Pixel and LinkedIn Insight.

Email authentication

95
  • Email authentication score: 95/100

    Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

3 checks passed
  • DMARC policy: reject

    DMARC tells receivers to reject mail that fails authentication, and sends you reports.

  • SPF in place (~all)

    An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 include:_spf.google.com include:spf.protection.outlook.com include:spf-us.emailsignatures365.com include:spfa.cp…”.

  • DKIM signing found

    A DKIM key is published (selector “google”, “selector1” and “k2”), so receivers can verify mail really came from you.

Privacy and tracking

  • 2 trackers load before any consent

    2

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

  • 4 cookies set on arrival

    4

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

  • 12 other companies contacted

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

1 checks passed
  • Consent tool: CookieYes

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

Upkeep, stack and company

  • The footer still says © 2025.

Stack

CMS
WordPress 18.3.1
Framework
React
Analytics
Google Tag Manager

Hiring

Hiring
21 open roles
Teams
27 - Medical Affairs (7), 12 - Finance (2), 17 - Commercial (2), 11 - Marketing (1)
Job board
greenhouse

Company

Headquarters
New York City

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

Go beyond the website

What your $25 Growth Playbook adds

This free review found 28 issues on mindmed.co, including 14 speed issues, 1 SEO issue and 4 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