amac.us website review

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

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

6 third-party services load with your homepage (posthog.com, Google Tag Manager and Facebook and others), adding 920 KiB and 1.0 s of main-thread time.

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

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

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

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

posthog.com costs a phone 400 ms of main-thread work and 207 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 39 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

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

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

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

5 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

About 12 KiB of CSS is downloaded but never applied on this page.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 14.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “FAITH, FAMILY, FREEDOM Join the Strength of Millions One vo…”.

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

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

Scripts block taps and scrolling for 462 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.

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

Your homepage downloads 4.8 MB in 69 requests on a phone: images 3.4 MB (11), scripts 1.0 MB (40) and fonts 204 KiB (3). Under 2 MB keeps phones on slow connections fast.

AEP-Countdown.png weighs 2.4 MB. On a phone connection a single image that size takes seconds.

1 image is downloaded at several times the size a phone draws it, for example AEP-Countdown.png at 1,672 px wide, shown at 139 px. Resized copies would save about 2.2 MB.

1 image (2.4 MB) 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.35 g of CO₂e: 161.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

The homepage links to 243 pages on amac.us and 14 external pages.

Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.

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

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://facebook.com/AMACforAmerica/.

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.

amac.us 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.

Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

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

The homepage carries about 1,961 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 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 5 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.