ccbh.com website review

16 files are served with short cache lifetimes, so returning visitors download them again (1.6 MB).

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

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

About 383 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.5 s faster on a phone.

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

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

87 KiB could be saved by minifying CSS.

45 KiB could be saved by minifying JavaScript.

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

Google CDN costs a phone 91 ms of main-thread work and 349 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.

4 third-party services load with your homepage (Google CDN, piwik.pro and Other Google APIs/SDKs and others), adding 449 KiB and 136 ms of main-thread time.

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

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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.

Your largest element takes 10.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Community Care helps you get the behavioral health treatmen…”.

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

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

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

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

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

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

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

4 images are downloaded at several times the size a phone draws them, for example EQ100-RGB.jpg at 1,750 px wide, shown at 138 px. Resized copies would save about 708 KiB.

Your homepage downloads 2.0 MB in 23 requests on a phone: images 926 KiB (8), scripts 537 KiB (6) and stylesheets 396 KiB (3). Under 2 MB keeps phones on slow connections fast.

4 images (881 KiB) 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.

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

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

Some list items are not inside a list.

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

1 link inside paragraphs relies on colour alone to stand out.

Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

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 on the page fails this check, rated moderate by axe-core.

Your title is only 20 characters: “Home: Community Care”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

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

No XML sitemap at https://www.ccbh.com/sitemap.xml, so Google discovers your pages only by following links.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 13 pages on ccbh.com and 9 external pages.

There is no /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.

We fetched 10 pages linked from your homepage and read each the way a search engine does.

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

2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'classList')”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

3 images are served at too low a resolution for sharp phone screens.

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

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

HSTS is set, but max-age is 186 days; one year is the recommended minimum.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

Opening https://ccbh.com goes through 2 redirects before the homepage loads.

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

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

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

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

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

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

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

DMARC is set to p=none, so mail pretending to be ccbh.com is still delivered. Add a report address, check the reports, then move to quarantine.

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.

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

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.

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