ache.org website review

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

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

3 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.

8 third-party services load with your homepage (Google Tag Manager, Facebook and Clarity and others), adding 1.2 MB and 624 ms of main-thread time.

9 images could be 514 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.

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

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

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

18 KiB could be saved by minifying JavaScript.

6 long tasks block the main thread while loading, the longest for 120 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).

Polyfills for old browsers add 31 KiB JavaScript that modern phones do not need.

7 KiB could be saved by minifying CSS.

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.

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

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

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

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

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

Your largest element takes 3.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Where Healthcare Leaders Are Made”.

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

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

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

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

Your homepage downloads 2.7 MB in 98 requests on a phone: scripts 1.1 MB (18), images 1,000 KiB (27) and fonts 328 KiB (11). Under 2 MB keeps phones on slow connections fast.

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

7 images are downloaded at several times the size a phone draws them, for example MCUBRELXYLWRAYVCFBOHNPEJTXDQ at 700 px wide, shown at 142 px. Resized copies would save about 348 KiB.

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

1 frame has no title, so screen-reader users cannot tell what it contains.

1 visible link has no text or label, so screen readers cannot say where it goes.

Your title is 94 characters, so Google will cut it off around 60: “ACHE | The Professional Home of Healthcare Leaders | American College of Healthcare Execu…”.

Open Graph is missing og:description, so shared links fall back to guesses.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 146 pages on ache.org and 35 external pages.

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.

robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and 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.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

1 link go through two or more redirects, for example https://www.ache.org/Login.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

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

ache.org is registered until Dec 2026. Make sure auto-renew is on and the card on file is current.

ache.org 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.

ache.org'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.

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.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 134 words of visible text; thin pages give Google and first-time buyers little to go on.

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

DMARC is set to p=none, so mail pretending to be ache.org is still delivered. Reports are on, so moving to quarantine is the next step.

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, Google Tag Manager, LinkedIn Insight and Meta Pixel and 2 mores (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 11 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.