kidstlc.org website review

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

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Other Google APIs/SDKs and Bootstrap CDN and others), adding 528 KiB and 371 ms of main-thread time.

About 211 KiB of JavaScript is downloaded but never used on this page.

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

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

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.

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

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

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

Your largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Residential”. Most of its time is resource load delay (3.8 s).

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

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

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

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

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

10 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-24, real Chrome visitors' largest content (lcp) went from 2.9 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

10 images (643 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.

9 images further down the page (510 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image is downloaded at several times the size a phone draws it, for example Happy-family-parallax-WEB.jpg at 1,500 px wide, shown at 390 px. Resized copies would save about 52 KiB.

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

Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

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

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

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

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

There are 2 <h1> headlines (“Because HOPE transforms lives” and “KidsTLC”). One clear main headline is easier for people and search engines.

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

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

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

The homepage links to 68 pages on kidstlc.org and 21 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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

robots.txt blocks CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

https://www.kidstlc.org/about-kidstlc/why-kidstlc, https://www.kidstlc.org/about-kidstlc/kidstlc-leadership-teams, https://www.kidstlc.org/about-kidstlc/board-members, https://www.kidstlc.org/services/support-and-respite, https://www.kidstlc.org/thriving-communities and https://www.kidstlc.org/stay-in-the-know have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.kidstlc.org/services, https://www.kidstlc.org/services/psychiatric-residential-treatment-facility-prtf, https://www.kidstlc.org/services/outpatient, https://www.kidstlc.org/services/intensive-outpatient-program, https://www.kidstlc.org/services/autism and https://www.kidstlc.org/services/support-and-respite and 5 others took over 3 s to send their HTML from our server.

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

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

1 image is served at too low a resolution for sharp phone screens.

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.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 527 words of visible text.

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.

Opening the homepage sets 2 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 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.