supportiveconcepts.org website review

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

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

About 129 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 45 (desktop: 67). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

16 KiB could be saved by minifying CSS.

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

31 KiB could be saved by minifying JavaScript.

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

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

3 third-party services load with your homepage (Google Tag Manager, Google Fonts and Google Analytics), adding 618 KiB and 462 ms of main-thread time.

2 images could be 189 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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.

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

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

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

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 3.1 MB in 125 requests on a phone: images 1.6 MB (30), scripts 988 KiB (53) and stylesheets 243 KiB (33). Under 2 MB keeps phones on slow connections fast.

8 images (754 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 (22 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 0.87 g of CO₂e: 104.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 button has no accessible name, so screen readers announce just “button”.

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

The homepage links to 39 pages on supportiveconcepts.org and 8 external pages.

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

There is no https://www.supportiveconcepts.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.supportiveconcepts.org/about-us and https://www.supportiveconcepts.org/faqs all use the title “About Us - Supportive Concepts for Families”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.supportiveconcepts.org/contact, https://www.supportiveconcepts.org/about-us, https://www.supportiveconcepts.org/leadership, https://www.supportiveconcepts.org/residential-services, https://www.supportiveconcepts.org/day-programs and https://www.supportiveconcepts.org/community-programs and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.supportiveconcepts.org/project/habilitation, whose canonical is https://www.supportiveconcepts.org/project/residential-habilitation-and-supported-living. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.supportiveconcepts.org/residential-services, https://www.supportiveconcepts.org/day-programs, https://www.supportiveconcepts.org/community-programs, https://www.supportiveconcepts.org/mental-health-services, https://www.supportiveconcepts.org/behavioral-health and https://www.supportiveconcepts.org/project/what-we-believe-about-behavioral-supportive-services and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.supportiveconcepts.org/contact, https://www.supportiveconcepts.org/day-programs, https://www.supportiveconcepts.org/community-programs, https://www.supportiveconcepts.org/behavioral-health, https://www.supportiveconcepts.org/project/habilitation and https://www.supportiveconcepts.org/faqs took over 3 s to send their HTML from our server.

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

2 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://www.supportiveconcepts.org/wp-content/themes/purehearts/style.min.css?ver=7.1.3' b…”.

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

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.

Social proof on the homepage: 11 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads 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 11 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 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.