careaccess.com website review

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

YouTube costs a phone 2.2 s of main-thread work and 6.7 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

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

8 third-party services load with your homepage (YouTube, localizecdn.com and Google Tag Manager and others), adding 7.8 MB and 2.9 s of main-thread time.

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

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

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

The page has 1,546 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

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.

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

Your largest element takes 39.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Gabriel, a clinical research participant”.

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

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

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

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

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

Your homepage downloads 9.4 MB in 169 requests on a phone: scripts 6.9 MB (46), images 888 KiB (43) and fonts 593 KiB (14). Under 2 MB keeps phones on slow connections fast.

5 images are downloaded at several times the size a phone draws them, for example michelle.jpg at 1,500 px wide, shown at 313 px. Resized copies would save about 435 KiB.

3 images (383 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 (157 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 2.65 g of CO₂e: 318.0 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”.

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

Some lists contain elements other than list items, which screen readers announce wrongly.

1 image has no alt text, which hurts accessibility and image search.

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

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

Your title is 67 characters, so Google will cut it off around 60: “Care Access | Let's Accelerate the Future of Medicine for Everyone.”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

1 link has no real href, so search engines can't follow it.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 83 pages on careaccess.com and 50 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 /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.

/, /research-sponsors, /participate/how-research-works, /participate/clinical-research-overview, /participate/research-studies-open-for-enrollment and /friends-lpa and 1 other all use the title “Care Access | Let's Accelerate the Future of Medicine for Everyone.”. Search engines can't tell which page to show for a search, so each competes with the others.

/participate/health-screening, /participate/all-health-screenings, /participate/how-research-works, /participate/clinical-research-overview, /participate/research-studies-open-for-enrollment and /friends-lpa and 3 others use the same meta description. A description written for each page earns more clicks.

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

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

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.

HSTS is set, but max-age is 180 days; one year is the recommended minimum.

1 link go through two or more redirects, for example https://careaccessresearch.sharepoint.com/.

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

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

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

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

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.

There is no form on the homepage, so every lead has to click through to another page first.

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 1,339 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, Google Tag Manager, HubSpot and LinkedIn Insight and 1 more (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 9 cookies, 1 of them by other companies (measured from a US location before any click).

Loading the homepage contacts 26 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.