abcf.org website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, FontAwesome CDN and Facebook and others), adding 1.3 MB and 911 ms of main-thread time.

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

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

Google Tag Manager costs a phone 512 ms of main-thread work and 529 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 397 KiB of JavaScript is downloaded but never used on this page.

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

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

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

Polyfills for old browsers add 55 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.

3 KiB could be saved by minifying CSS.

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 2.0 s for your server to start answering (75th percentile). Good is under 800 ms.

Your largest element takes 9.4 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 12.8 s. Good is under 3.8 s.

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

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

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

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

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

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

Your homepage downloads 6.0 MB in 134 requests on a phone: images 4.0 MB (38), scripts 1.1 MB (47) and fonts 530 KiB (12). Under 2 MB keeps phones on slow connections fast.

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

1 image (400 KiB) is 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.

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

Elements must only use permitted ARIA attributes: 5 elements on the page fail this check, rated serious by axe-core.

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

1 link inside paragraphs relies on colour alone to stand out.

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

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

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

Headings skip levels (h1 → h5, h3 → h5 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 are 2 <h1> headlines (“start your prevention era” and “start your prevention era”). One clear main headline is easier for people and search engines.

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

The homepage links to 94 pages on abcf.org and 28 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.

/breast-cancer-assistance-program and /our-programs/breast-cancer-assistance-program all use the title “Breast Cancer Assistance Program - American Breast Cancer Foundation”. Search engines can't tell which page to show for a search, so each competes with the others.

/donate, /breast-cancer-assistance-program, /from-awareness-to-access, /our-programs/breast-cancer-assistance-program, /our-programs/education-patient-advocacy-program and /our-programs/community-partnership-program and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /breast-cancer-assistance-program, whose canonical is /our-programs/breast-cancer-assistance-program. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/donate, /breast-cancer-assistance-program, /our-programs/breast-cancer-assistance-program, /our-programs/education-patient-advocacy-program, /our-programs/community-partnership-program and /stories took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 34 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 ()”.

2 links to other sites are dead, for example https://cfccharities.opm.gov/ (503).

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.

2 links go through two or more redirects, for example https://www.facebook.com/pages/American-Breast-Cancer-Foundation/329029404062.

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.

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

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

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.

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

DMARC is set to p=none, so mail pretending to be abcf.org is still delivered. Add a report address, check the reports, then move to quarantine.

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