Website review, no card needed

bhwcares.com logo

bhwcares.com website review

Visit site (opens in a new tab)Reviewed 29 October 202639 issues · 88 checks

This review found 39 issues worth fixing on bhwcares.com, 11 of them high impact, across 88 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
2.6 s1.8 sMay 9Oct 242.3 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.9 s
May 16, 20261.9 s
May 23, 20262.0 s
May 30, 20262.1 s
Jun 6, 20262.0 s
Jun 13, 20262.0 s
Jun 20, 20261.9 s
Jun 27, 20262.0 s
Jul 4, 20262.0 s
Jul 11, 20262.2 s
Jul 18, 20262.2 s
Jul 25, 20262.3 s
Aug 1, 20262.5 s
Aug 8, 20262.4 s
Aug 15, 20262.4 s
Aug 22, 20262.3 s
Aug 29, 20262.2 s
Sep 5, 20262.3 s
Sep 12, 20262.4 s
Sep 19, 20262.5 s
Sep 26, 20262.5 s
Oct 3, 20262.5 s
Oct 10, 20262.3 s
Oct 17, 20262.4 s
Oct 24, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
80 ms69 msMay 9Oct 2471 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202671 ms
May 16, 202676 ms
May 23, 202675 ms
May 30, 202679 ms
Jun 20, 202671 ms
Jun 27, 202675 ms
Jul 4, 202677 ms
Jul 11, 202672 ms
Jul 18, 202679 ms
Jul 25, 202670 ms
Aug 1, 202671 ms
Aug 8, 202671 ms
Aug 15, 202677 ms
Aug 22, 202677 ms
Aug 29, 202674 ms
Sep 5, 202677 ms
Sep 12, 202674 ms
Sep 19, 202670 ms
Sep 26, 202671 ms
Oct 3, 202671 ms
Oct 10, 202671 ms
Oct 17, 202679 ms
Oct 24, 202671 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 bhwcares.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. bhwcares.com at 0.5 s0.5 s
  2. bhwcares.com at 1.0 s1.0 s
  3. bhwcares.com at 1.5 s1.5 s
  4. bhwcares.com at 2.0 s2.0 s
  5. bhwcares.com at 2.5 s2.5 s
  6. bhwcares.com at 3.0 s3.0 s
  7. bhwcares.com at 3.5 s3.5 s
  8. bhwcares.com at 4.0 s4.0 s

Speed

8 to fix56
  • Reduce unused JavaScript

    4.4 s · 624 KiB

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

  • Render-blocking requests

    3.6 s

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

  • Use efficient cache lifetimes

    900 ms · 171 KiB

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

  • Mobile performance score: 56

    56/100

    Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, Google Tag Manager and Facebook and others), adding 1.5 MB and 809 ms of main-thread time.

  • Reduce unused CSS

    610 ms · 145 KiB

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

  • Google CDN adds 414 ms

    414 ms

    Google CDN costs a phone 414 ms of main-thread work and 736 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: 2.6 s

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

  • Legacy JavaScript

    200 ms · 40 KiB

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

  • Improve image delivery

    150 ms · 10 KiB

    2 images could be 10 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.

  • 9 long tasks on the main thread

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

  • Font display

    150 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).

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

    22 ms

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

Core Web Vitals

7 to fix100
  • Largest Contentful Paint: 14.5 s

    14.5 s

    Your largest element takes 14.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Time to Interactive: 16.4 s

    16.4 s

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

  • First Contentful Paint: 3.5 s

    3.5 s

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

  • Speed Index: 6.9 s

    6.9 s

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

  • Largest content (LCP) got 24% slower for real visitors

    +24%

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

  • Total Blocking Time: 287 ms

    287 ms

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

  • 2 images without width and height

    2 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    +2%

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

7 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: 2.3 s

    2.3 s

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

  • Real-user INP: 71 ms

    71 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 1.7 s

    1.7 s

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

  • Real-user TTFB: 778 ms

    778 ms

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

  • Cumulative Layout Shift: 0.025

    0.025

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

Images and page weight

1 to fix85
  • Page weight: 2.9 MB in 108 requests

    2.9 MB

    Your homepage downloads 2.9 MB in 108 requests on a phone: scripts 1.5 MB (44), fonts 547 KiB (6) and other files 383 KiB (12). Under 2 MB keeps phones on slow connections fast.

  • About 0.8 g of CO₂ per visit

    0.81 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.81 g of CO₂e: 97.4 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

7 to fixGoogle 8990
  • 13 text elements with low contrast

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

  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

    ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (4 elements)

    All page content should be contained by landmarks: 4 elements on the page fail 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.

  • 5 links without text

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

  • 4 form fields without a label

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

  • Headings skip levels

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

1 checks passed
  • 44 automated accessibility rules passed

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

SEO

6 to fixGoogle 8578
  • Title is long (66 characters)

    Your title is 66 characters, so Google will cut it off around 60: “Behavioral Health Works | Treatment for Autism & Related Disorders”.

  • Meta description is long (169 characters)

    Your meta description is 169 characters; Google truncates after about 160, so the end of your pitch is cut.

  • Structured data has 2 problems

    Structured data found (BreadcrumbList, ChildCare, WebPage and WebSite) but with 2 problems, for example “ChildCare: url is not an absolute URL ("[site_url_secure]/")”.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 5 links with vague text

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

  • 3 links crawlers can't follow

    3 links have no real href, so search engines can't follow them.

  • No X (Twitter) card tag

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

  • 31 internal links, 14 external

    The homepage links to 31 pages on bhwcares.com and 14 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “Behavioral Health Works (BHW)”.

  • Canonical URL set

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

  • 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.bhwcares.com/sitemap_index.xml.

AI search readiness

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

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

  • No llms.txt

    There is no https://www.bhwcares.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 (270 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix76
  • 2 pages point its canonical at the homepage

    https://www.bhwcares.com/care-team and https://www.bhwcares.com/partners declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

  • 3 pages share a title

    /, https://www.bhwcares.com/care-team and https://www.bhwcares.com/partners all use the title “Behavioral Health Works | Treatment for Autism & Related Disorders”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 7 pages share a meta description

    https://www.bhwcares.com/care-team and https://www.bhwcares.com/partners use the same meta description. A description written for each page earns more clicks.

  • 4 pages without an H1

    https://www.bhwcares.com/new-jersey, https://www.bhwcares.com/california, https://www.bhwcares.com/massachusetts and https://www.bhwcares.com/maryland 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 and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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 7387
  • 8 small tap targets

    8 of 19 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 “Mixed Content: The page at 'https://www.bhwcares.com/' was loaded over HTTPS, but requested an insecure stylesheet 'htt…”.

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • No social proof

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

  • Only about 228 words

    The homepage has only about 228 words of visible text; thin pages give Google and first-time buyers little to go on.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Get Started” and “Learn More”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Contact”, “Contact Us” and “Get Started”.

  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Analytics and Meta Pixel.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage.

  • 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 Analytics, Google Tag Manager and Meta 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.

  • 4 cookies set on arrival

    4

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

  • 11 other companies contacted

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

Upkeep, stack and company

  • The footer still says © 2021.

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics
Hosting
Hetzner

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on bhwcares.com, including 15 speed issues, 6 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