Website review, no card needed

mnmentalhealth.com logo

mnmentalhealth.com website review

Visit site (opens in a new tab)Reviewed 23 October 202629 issues · 82 checks

This review found 29 issues worth fixing on mnmentalhealth.com, 11 of them high impact, across 82 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
4.1 s1.1 sMay 2Oct 171.7 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.5 s
May 9, 20263.6 s
May 16, 20263.5 s
May 23, 20263.5 s
May 30, 20263.8 s
Jun 6, 20263.6 s
Jun 13, 20263.5 s
Jun 20, 20263.2 s
Jun 27, 20262.7 s
Jul 4, 20262.8 s
Jul 11, 20262.8 s
Jul 18, 20262.9 s
Jul 25, 20262.9 s
Aug 1, 20262.8 s
Aug 8, 20262.4 s
Aug 15, 20261.9 s
Aug 22, 20261.6 s
Aug 29, 20261.4 s
Sep 5, 20261.6 s
Sep 12, 20261.7 s
Sep 19, 20261.6 s
Sep 26, 20261.6 s
Oct 3, 20261.5 s
Oct 10, 20261.6 s
Oct 17, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
164 ms95 msMay 2Oct 17127 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026103 ms
May 9, 2026104 ms
May 16, 2026104 ms
May 23, 2026107 ms
May 30, 2026110 ms
Jun 6, 2026114 ms
Jun 13, 2026127 ms
Jun 20, 2026128 ms
Jun 27, 2026133 ms
Jul 4, 2026138 ms
Jul 11, 2026136 ms
Jul 18, 2026138 ms
Jul 25, 2026150 ms
Aug 1, 2026156 ms
Aug 8, 2026152 ms
Aug 15, 2026153 ms
Aug 22, 2026139 ms
Aug 29, 2026137 ms
Sep 5, 2026137 ms
Sep 12, 2026132 ms
Sep 19, 2026133 ms
Sep 26, 2026129 ms
Oct 3, 2026127 ms
Oct 10, 2026127 ms
Oct 17, 2026127 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 mnmentalhealth.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mnmentalhealth.com at 0.7 s0.7 s
  2. mnmentalhealth.com at 1.4 s1.4 s
  3. mnmentalhealth.com at 2.1 s2.1 s
  4. mnmentalhealth.com at 2.8 s2.8 s
  5. mnmentalhealth.com at 3.5 s3.5 s
  6. mnmentalhealth.com at 4.2 s4.2 s
  7. mnmentalhealth.com at 4.9 s4.9 s
  8. mnmentalhealth.com at 5.7 s5.7 s

Speed

10 to fix35
  • Reduce unused JavaScript

    6.9 s · 1.2 MB

    About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.9 s faster on a phone.

  • Improve image delivery

    1.2 s · 191 KiB

    3 images could be 191 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.2 s faster on a phone.

  • Mobile performance score: 35

    35/100

    Your mobile performance score is 35 (desktop: 79). 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 (Google Tag Manager, Google CDN and psychplus.io and others), adding 2.3 MB and 1.6 s of main-thread time.

  • Google Tag Manager adds 613 ms

    613 ms

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

  • Google CDN adds 518 ms

    518 ms

    Google CDN costs a phone 518 ms of main-thread work and 757 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.6 s

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

  • psychplus.io adds 259 ms

    259 ms

    psychplus.io costs a phone 259 ms of main-thread work and 703 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.

  • 18 long tasks on the main thread

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

  • Google Maps adds 164 ms

    164 ms

    Google Maps costs a phone 164 ms of main-thread work and 354 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.

  • Legacy JavaScript

    250 ms · 11 KiB

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

  • Use efficient cache lifetimes

    200 ms · 39 KiB

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

  • Reduce unused CSS

    33 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 79 but mobile only 35. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

1 checks passed
  • Server response: 29 ms

    29 ms

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

Core Web Vitals

6 to fix100
  • First Contentful Paint: 9.1 s

    9.1 s

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

  • Largest Contentful Paint: 18.7 s

    18.7 s

    Your largest element takes 18.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Mental health care that actually knows you.”.

  • Time to Interactive: 21.0 s

    21.0 s

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

  • Speed Index: 9.1 s

    9.1 s

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

  • Total Blocking Time: 957 ms

    957 ms

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

  • Tap response (INP) got 23% slower for real visitors

    +23%

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

8 checks passed
  • Passes Core Web Vitals for real visitors

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

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

    129 ms

    Real visitors wait 129 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: 1.3 s

    1.3 s

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

  • Real-user TTFB: 580 ms

    580 ms

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

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

    -55%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 3.5 s to 1.7 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 fix85
  • Page weight: 3.4 MB in 96 requests

    3.4 MB

    Your homepage downloads 3.4 MB in 96 requests on a phone: scripts 2.3 MB (54), images 398 KiB (17) and other files 365 KiB (13). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

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

  • About 1.0 g of CO₂ per visit

    0.98 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

4 to fixGoogle 9495
  • 4 text elements with low contrast

    4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 3 tap targets too small

    3 tap targets are too small or too close together to hit reliably with a finger.

  • 23 links without text

    23 visible links have no text or label, so screen readers cannot say where they go.

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 11 images in the HTML carry an alt attribute.

  • 53 automated accessibility rules passed

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

SEO

2 to fixGoogle 10090
  • Title is long (85 characters)

    Your title is 85 characters, so Google will cut it off around 60: “Minnesota Mental Health Clinics | Locally Owned Mental Health Care in the Twin Cities”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 98 internal links, 7 external

    The homepage links to 98 pages on mnmentalhealth.com and 7 external pages.

6 checks passed
  • Meta description: 138 characters

    Your meta description is 138 characters: “Therapy, psychiatry, and assessments across 11 Twin Cities locations and via telehealth statewide. Locally owned and ma…”.

  • One H1 headline

    Your main headline reads: “Mental health care that actually knows you.”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: ImageObject, MedicalClinic, MedicalOrganization, WebPage and WebSite.

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

AI search readiness

100
4 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: 6 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://mnmentalhealth.com/llms.txt (4 KiB, 18 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 1 page without an H1

    https://mnmentalhealth.com/locations has 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 45 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.

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

  • 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 9287
  • 5 small tap targets

    5 of 13 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 “Minified React error #418; visit https://react.dev/errors/418?args[]= for the full message or use the non-minified dev …”.

  • 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

2 to fix81
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • Thin social proof

    Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No opening hours

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

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

    The homepage carries about 713 words of visible text.

6 checks passed
  • 9 calls to action

    The homepage has 9 calls to action, for example “📞 Call now”, “Pricing” and “📞 Call (651) 454-0114”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 4 phone links and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.

  • 9 cookies set on arrival

    9

    Opening the homepage sets 9 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.

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

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 mnmentalhealth.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Next.js
Analytics
Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on mnmentalhealth.com, including 16 speed issues, 2 SEO 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