all.org website review

About 509 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.7 s faster on a phone.

8 images could be 779 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.1 s faster on a phone.

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

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

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

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

7 third-party services load with your homepage (givecloud.co, Google Tag Manager and New Relic and others), adding 1.1 MB and 483 ms of main-thread time.

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

givecloud.co costs a phone 290 ms of main-thread work and 518 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.0 s on main-thread work while loading, 686 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

pantheonsite.io costs a phone 0 ms of main-thread work and 338 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 23 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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.

5 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 1.3 s for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

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

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

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

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

Your homepage downloads 3.1 MB in 66 requests on a phone: images 1.4 MB (10), scripts 1.1 MB (23) and fonts 366 KiB (13). Under 2 MB keeps phones on slow connections fast.

7 images (1.1 MB) 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.

7 images further down the page (1.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

5 images are downloaded at several times the size a phone draws them, for example CLSPblog_FamilyTeaching_930x620.jpg at 930 px wide, shown at 306 px. Resized copies would save about 73 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 0.87 g of CO₂e: 104.2 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: 12 elements on the page fail this check, rated serious by axe-core.

Headings should not be empty: 4 elements on the page fail this check, rated minor by axe-core.

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

There are 2 <h1> headlines (“American Life League” and “MORE PRO-LIFE MEDIA”). One clear main headline is easier for people and search engines.

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

The homepage links to 87 pages on all.org and 22 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.

/wednesday-stopp-report, /learn, /stopp and /clsp have no meta description, so Google writes the search snippet from whatever text it finds.

/category/guest-commentary, /category/pro-life-this-week, /category/interviews and /category/press-releases use the same meta description. A description written for each page earns more clicks.

/judie-brown-commentary has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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 0 days; one year is the recommended minimum.

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

1 link go through two or more redirects, for example http://www.campusforlife.org/.

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.

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

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

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.

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

The homepage shows no opening hours. If customers visit or call, show when.

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

DMARC is set to p=none, so mail pretending to be all.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 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 (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 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.