addus.com website review

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

Your mobile performance score is 67 (desktop: 86). Pages that score under 90 lose visitors before the first paint.

About 210 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 680 ms faster on a phone.

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

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

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

3 third-party services load with your homepage (Google Tag Manager, Google Analytics and Adobe TypeKit), adding 451 KiB and 217 ms of main-thread time.

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

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

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

14 KiB could be saved by minifying JavaScript.

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.

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

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

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

Your largest element takes 6.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We’re Here to Help You Maintain Your Health And Independenc…”.

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

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

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

27 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 94 ms to 94 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

12 images (606 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.

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

4 images are downloaded at several times the size a phone draws them, for example circle-of-excellence.png at 451 px wide, shown at 90 px. Resized copies would save about 158 KiB.

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

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

2 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 7 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.

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

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

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

The homepage links to 92 pages on addus.com and 27 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 /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.

/mission-and-values and /guide-model-for-dementia-care have no meta description, so Google writes the search snippet from whatever text it finds.

/locations has no <h1> headline, so visitors and search engines get no clear main topic.

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

2 of 8 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 “Unexpected token '<'”.

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

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

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

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

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

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.

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