alpha.org website review

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

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

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

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

Polyfills for old browsers add 174 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 900 ms faster on a phone.

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

8 third-party services load with your homepage (Squarespace, Snapchat and ghostplugins.dev and others), adding 1.9 MB and 667 ms of main-thread time.

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

Squarespace costs a phone 397 ms of main-thread work and 1.3 MB 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.2 s on main-thread work while loading, 775 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

sqspcdn.com costs a phone 51 ms of main-thread work and 379 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.

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

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.

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 4.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

Your largest element takes 17.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

2 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' largest content (lcp) went from 4.1 s to 4.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.2 MB in 145 requests on a phone: scripts 1.7 MB (84), images 1.2 MB (18) and stylesheets 192 KiB (20). Under 2 MB keeps phones on slow connections fast.

Explore+faith+at+Alpha-04.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

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

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 21 characters: “Alpha — Explore Faith”. Between 30 and 65 characters leaves room to say what you do and for whom.

Structured data found (LocalBusiness and WebSite) but with 2 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/67e3e5a2f58ee67192a…”.

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

The homepage links to 72 pages on alpha.org and 9 external pages.

Your Organization JSON-LD is missing name, url, logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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.

/blog-summary-block/blog-post-title-one-zzrs8, /blog-summary-block/blog-post-title-two-nh9s9, /blog-summary-block/blog-post-title-three-5fmp9, /blog-summary-block/blog-post-title-four-jkajk and /donate are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/run, /run-alpha and /try-alpha have no meta description, so Google writes the search snippet from whatever text it finds.

/national-offices, /run, /what-is-alpha, /from-alpha, /get-involved and /run-alpha and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

/national-offices has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

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

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

1 link from your homepage to your own site is broken, for example https://www.alpha.org/cdn-cgi/content?id=iPGP_q0s57iQQ28JKB0PujXTULw.xIdgaHZJc5mMe2A-1793936292.6136081-1.2.1.1-nczHKhAPtNFAeShakH7NStr7bAAa8OI27i83efgnwCNKcWqddslKz0k6BugRM4dE (404).

No Content-Security-Policy header, the main browser-side defence against injected scripts.

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

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.

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

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

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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 form on the homepage, so every lead has to click through to another page first.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 649 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 Snap 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 6 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.