amazima.org website review

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and fundraiseup.com and others), adding 1.5 MB and 1.4 s of main-thread time.

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

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

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

Facebook costs a phone 255 ms of main-thread work and 243 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.

5 images could be 111 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

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

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

4 KiB could be saved by minifying JavaScript.

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

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

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

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

Your largest element takes 18.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Making disciples of Jesus through authentic relationships, …”.

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

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

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

Real visitors wait 465 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 642 ms to 670 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 4.1 MB in 285 requests on a phone: scripts 2.2 MB (128), stylesheets 705 KiB (87) and images 610 KiB (20). Under 2 MB keeps phones on slow connections fast.

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

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

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

1 tap target is too small or too close together to hit reliably with a finger.

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

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

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

Your meta description is 273 characters; Google truncates after about 160, so the end of your pitch is cut.

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

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

2 links have no real href, so search engines can't follow them.

The homepage links to 100 pages on amazima.org and 8 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.

/our-story, /our-mission, /meet-our-team, /blog, /contact and /primary-school and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

/our-story, /impact, /meet-our-team, /blog, /primary-school and /secondary-school and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cloud.typography.com/7900512/7434392/css/fonts.css' from origin 'https://amazima.o…”.

1 link to other sites is dead, for example https://www.ecfa.org/MemberProfile.aspx?ID=36591 (404).

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.

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.

amazima.org is registered until Dec 2026. Make sure auto-renew is on and the card on file is current.

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

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

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.

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

The page uses urgency cues (a countdown or limited-time wording).

DMARC is set to p=none, so mail pretending to be amazima.org is still delivered. Reports are on, so moving to quarantine is the next step.

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