thecfr.org website review

About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.0 s faster on a phone.

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

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

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

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

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

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

YouTube costs a phone 376 ms of main-thread work and 966 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.

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

Google Tag Manager costs a phone 270 ms of main-thread work and 663 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.4 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

nxedge.io costs a phone 0 ms of main-thread work and 294 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.

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

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

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

Desktop scores 72 but mobile only 46. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

4 KiB could be saved by minifying CSS.

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

Your largest element takes 19.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Keeping children housed one family at a time.”.

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

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

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

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-17, real Chrome visitors' tap response (inp) went from 81 ms to 72 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.6 MB in 77 requests on a phone: images 2.3 MB (12), scripts 2.3 MB (28) and other files 352 KiB (8). Under 2 MB keeps phones on slow connections fast.

4 images are downloaded at several times the size a phone draws them, for example AdobeStock_439743929-1.jpeg at 1,688 px wide, shown at 340 px. Resized copies would save about 597 KiB.

CFR_Logos_Horz.svg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

4 images (812 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.

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

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

Links must have discernible text: 7 elements on the page fail this check, rated serious 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.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Your title is 67 characters, so Google will cut it off around 60: “Housing Insecurity in Cobb County | The Center for Family Resources”.

The homepage links to 31 pages on thecfr.org and 15 external pages.

There is no https://thecfr.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://thecfr.org/about, https://thecfr.org/about/our-board, https://thecfr.org/about/our-staff, https://thecfr.org/about/financials, https://thecfr.org/about/our-impact and https://thecfr.org/about/cobb-homeless-alliance and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://thecfr.org/wp-content/uploads/2026/08/cfr-family-journey_rev-1.html has no <h1> headline, so visitors and search engines get no clear main topic.

https://thecfr.org/about/our-staff, https://thecfr.org/about/cobb-homeless-alliance, https://thecfr.org/category/news-events, https://thecfr.org/housing-services and https://thecfr.org/the-family-cupboard took over 3 s to send their HTML from our server.

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

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

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

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 form on the homepage, so every lead has to click through to another page first.

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 292 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 3 cookies, 1 of them by other companies (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 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.