afrointroductions.com website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and TikTok and others), adding 1.1 MB and 1.2 s of main-thread time.

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

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

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

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

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

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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.

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

Your largest element takes 15.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Meet African Singles Join with Email”.

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

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

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

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

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

Real visitors wait 1.4 s 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.

Your homepage downloads 2.2 MB in 85 requests on a phone: scripts 1.8 MB (36), other files 151 KiB (32) and images 112 KiB (9). Under 2 MB keeps phones on slow connections fast.

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

Form elements should have a visible label: 4 elements on the page fail this check, rated serious by axe-core.

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

4 images have no alt text, which hurts accessibility and image search.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

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

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 71 pages on afrointroductions.com and 40 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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.

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

No viewport meta tag, so phones render the desktop layout zoomed out.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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 “Cannot read properties of undefined (reading 'register')”.

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

Large scripts ship without source maps.

http://afrointroductions.com does not redirect to https, so some visitors land on the insecure version.

HSTS is set, but max-age is 0 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.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

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

afrointroductions.com'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 longest form asks for 9 fields (5 required). Every extra field lowers completion.

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

afrointroductions.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

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, Hotjar and Meta Pixel and 2 mores (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 21 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.