onafriq.com website review

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

8 third-party services load with your homepage (Google Tag Manager, iubenda and Facebook and others), adding 1.5 MB and 902 ms of main-thread time.

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

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

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

About 489 KiB of JavaScript is downloaded but never used on this page.

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

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

9 KiB could be saved by minifying JavaScript.

1 image could be 5 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

By the Sustainable Web Design model, a visit to your homepage emits about 0.54 g of CO₂e: 64.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

7 buttons have no accessible name, so screen readers announce just “button”.

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

All page content should be contained by landmarks: 9 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

3 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.

There are 2 <h1> headlines (“The access you need to scale your business” and “1B”). One clear main headline is easier for people and search engines.

Structured data found (WebSite) but with 1 problem, for example “WebSite: potentialAction.target is not an absolute URL ("{search_term_string}")”.

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

The homepage links to 33 pages on onafriq.com and 46 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 https://onafriq.com/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.

https://onafriq.com/services/card-issuance-and-processing, https://onafriq.com/services/treasury, https://onafriq.com/article/-able-and-onafriq-collaborate-with-visa-to-expand-access-to-credit-through-visa-flex-credential and https://onafriq.com/article/-able-et-onafriq-sassocient-a-visa-pour-elargir-lacces-au-credit-grace-au-visa-flex-credential have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://onafriq.com/article/modernising-settlement-with-stablecoins-shouldnt-require-rebuilding-payment-infrastructure-that-already-works, whose canonical is https://onafriq.com/insights/article/modernising-settlement-with-stablecoins-shouldnt-require-rebuilding-payment-infrastructure-that-already-works. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

We fetched 12 pages linked from your homepage and read each the way a search engine does.

1 error was logged to the browser console while the page loaded, for example “Identifier 'showOnPx' has already been declared”.

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.

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: 39 customer or partner logos. 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 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 632 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 1 more (measured from a US location before any click). A consent tool (iubenda) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 6 cookies (measured from a US location before any click).

Loading the homepage contacts 20 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.