wtcsb.org website review

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

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

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

Your mobile performance score is 34. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

20 long tasks block the main thread while loading, the longest for 1.8 s. During a long task the page ignores taps.

8 third-party services load with your homepage (Google Tag Manager, Osano CMP and Facebook and others), adding 1.3 MB and 1.4 s of main-thread time.

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

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

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

Osano CMP costs a phone 299 ms of main-thread work and 85 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.

The page has 1,554 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

4 images could be 66 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.

36 KiB could be saved by minifying JavaScript.

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

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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 14.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Mental Health Services for Everybody FIRST TIME VISITS  24…”.

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

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

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

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

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

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

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

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

The layout shifts by 0.142 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

Your homepage downloads 4.4 MB in 158 requests on a phone: images 1.9 MB (51), scripts 1.8 MB (51) and fonts 401 KiB (10). Under 2 MB keeps phones on slow connections fast.

3 images (121 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.

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

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

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

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

All page content should be contained by landmarks: 18 elements on the page fail this check, rated moderate by axe-core.

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

3 elements hidden from screen readers can still receive keyboard focus.

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

Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

There are 3 <h1> headlines (“Mental Health”, “Services for Everybody” and “CONTACT FORM”). One clear main headline is easier for people and search engines.

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

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

The homepage links to 145 pages on wtcsb.org and 10 external pages.

There is no https://www.wtcsb.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.

https://www.wtcsb.org/request-medical-records is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.wtcsb.org/request-medical-records took over 3 s to send its HTML from our server.

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

3 images failed to load on a phone, for example https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fjelly.mdhv.io%2fv1%2fstar.gif%3fpid%3dueaXcpwLBd9zP35kz5sfZbNuVE21%26src%3dmh%26evt%3dhi&c=E,1,wVeiJdV9lcFBiIJUJKecsVyevlLHp-Ry3UWUv9H6Cx40DoFXwlFBi.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

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

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

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.

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

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

The homepage carries about 932 words of visible text.

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

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

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