Website review, no card needed

ttbh.org logo

ttbh.org website review

Visit site (opens in a new tab)Reviewed 18 November 202614 issues · 68 checks

This review found 14 issues worth fixing on ttbh.org, 3 of them high impact, across 68 checks. The most urgent: 3 images over 500 KB. 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.2 s127 msMay 30Nov 14783 ms
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.8 s
Jun 6, 20261.6 s
Jun 13, 20263.4 s
Jun 20, 20263.9 s
Jun 27, 20264.0 s
Jul 4, 20264.6 s
Jul 11, 20264.4 s
Jul 18, 20264.3 s
Jul 25, 20264.2 s
Aug 1, 20262.4 s
Aug 8, 2026784 ms
Aug 15, 2026722 ms
Aug 22, 2026726 ms
Aug 29, 2026750 ms
Sep 5, 2026753 ms
Sep 12, 2026773 ms
Sep 19, 2026762 ms
Sep 26, 2026725 ms
Oct 3, 2026715 ms
Oct 10, 2026713 ms
Oct 17, 2026715 ms
Oct 24, 2026781 ms
Oct 31, 2026784 ms
Nov 7, 2026821 ms
Nov 14, 2026783 ms
Real-visitor tap response (INP)75th percentile, phones
153 ms51 msMay 30Nov 1477 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202694 ms
Jun 6, 202690 ms
Jun 13, 202695 ms
Jun 20, 2026104 ms
Jun 27, 2026102 ms
Jul 4, 2026141 ms
Jul 11, 2026126 ms
Jul 18, 2026111 ms
Jul 25, 202699 ms
Aug 1, 202670 ms
Aug 8, 202667 ms
Aug 15, 202663 ms
Aug 22, 202663 ms
Aug 29, 202667 ms
Sep 5, 202670 ms
Sep 12, 202670 ms
Sep 19, 202668 ms
Sep 26, 202667 ms
Oct 3, 202668 ms
Oct 10, 202670 ms
Oct 17, 202672 ms
Oct 24, 202675 ms
Oct 31, 202674 ms
Nov 7, 202678 ms
Nov 14, 202677 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 ttbh.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ttbh.org at 0.4 s0.4 s
  2. ttbh.org at 0.8 s0.8 s
  3. ttbh.org at 1.1 s1.1 s
  4. ttbh.org at 1.5 s1.5 s
  5. ttbh.org at 1.9 s1.9 s
  6. ttbh.org at 2.3 s2.3 s
  7. ttbh.org at 2.6 s2.6 s
  8. ttbh.org at 3.0 s3.0 s

Speed

2 to fix99
  • Improve image delivery

    3.0 MB

    7 images could be 3.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Render-blocking requests

    750 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 750 ms.

  • 1 third-party service on the page

    1 third-party service load with your homepage (Google Fonts), adding 79 KiB and 0 ms of main-thread time.

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

3 checks passed
  • Mobile performance score: 99

    99/100

    Your mobile performance score is 99. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.1 s

    A phone's processor spends 0.1 s on main-thread work while loading, 5 ms of it running JavaScript. That is comfortably low.

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

100
14 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.1 s

    1.1 s

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

  • Real-user INP: 69 ms

    69 ms

    Real visitors wait 69 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.1 s

    1.1 s

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

  • Real-user TTFB: 584 ms

    584 ms

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

  • Tap response (INP) got 16% faster for real visitors

    -16%

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

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

    -53%

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

  • First Contentful Paint: 1.6 s

    1.6 s

    The first text or image appears after 1.6 s, inside the 1.8 s “good” threshold.

  • Largest Contentful Paint: 1.6 s

    1.6 s

    Your largest element renders in 1.6 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “TTBH improves the lives of people with behavioral health ne…”.

  • Cumulative Layout Shift: 0.007

    0.007

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

  • Speed Index: 1.6 s

    1.6 s

    Visually, the page fills in at 1.6 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

  • Time to Interactive: 1.6 s

    1.6 s

    The page is fully interactive after 1.6 s.

Images and page weight

4 to fix50
  • 3 images over 500 KB

    3 images weigh 2.3 MB together. On a phone connection a single image that size takes seconds.

  • 6 images in older formats

    6 images (3.0 MB) 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.

  • Page weight: 3.1 MB in 11 requests

    3.1 MB

    Your homepage downloads 3.1 MB in 11 requests on a phone: images 3.1 MB (7), fonts 77 KiB (2) and HTML 9 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    399 KiB

    1 image is downloaded at several times the size a phone draws it, for example slide1.jpg at 1,600 px wide, shown at 358 px. Resized copies would save about 399 KiB.

  • About 0.9 g of CO₂ per visit

    0.89 g

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

1 checks passed
  • Images load when needed

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

Accessibility

2 to fixGoogle 10098
  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (3 elements).

2 checks passed
  • Every image has alt text

    All 12 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 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 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 10088
  • robots.txt blocks all crawlers

    Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Open Graph partly set

    Open Graph is missing og:title and og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 38 internal links, 10 external

    The homepage links to 38 pages on ttbh.org and 10 external pages.

5 checks passed
  • Meta description: 143 characters

    Your meta description is 143 characters: “Tropical Texas Behavioral Health provides mental health, substance use disorder, and intellectual disability services t…”.

  • One H1 headline

    Your main headline reads: “Tropical Texas Behavioral Health – Behavioral Health Services You Can Trust”.

  • Title: 61 characters

    Your title is a healthy 61 characters: “Tropical Texas Behavioral Health | Behavioral Health Services”.

  • Structured data in place

    Structured data found: Organization.

  • XML sitemap found

    Your XML sitemap is reachable at https://ttbh.org/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.ttbh.org/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: 4 of 6 facts

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

  • Text is in the HTML

    Your server sends the page's text in the HTML (526 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 25 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

1 to fixGoogle 10093
  • 10 small tap targets

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix60
  • 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: 4 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

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

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

    The homepage carries about 342 words of visible text.

2 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Call Crisis Hotline”, “Learn more about IDD Services” and “Learn more about Integrated Primary Care”.

  • Direct contact links

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

Privacy and tracking

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

  • 2 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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

Upkeep, stack and company

Stack

Hosting
AWS

Hiring

Hiring
1 open role
Job board
careers page

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 14 issues on ttbh.org, including 2 speed issues, 2 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