Website review, no card needed
interswitchgroup.com website review
Visit site (opens in a new tab)Reviewed 18 November 202642 issues · 85 checks
This review found 42 issues worth fixing on interswitchgroup.com, 20 of them high impact, across 85 checks. The most urgent: page weight: 73.1 MB in 98 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
72CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 4.7 s |
| Jun 6, 2026 | 5.0 s |
| Jun 13, 2026 | 5.5 s |
| Jun 20, 2026 | 5.6 s |
| Jun 27, 2026 | 5.6 s |
| Jul 4, 2026 | 5.4 s |
| Jul 11, 2026 | 5.2 s |
| Jul 18, 2026 | 5.1 s |
| Jul 25, 2026 | 5.1 s |
| Aug 1, 2026 | 5.2 s |
| Aug 8, 2026 | 5.4 s |
| Aug 15, 2026 | 5.4 s |
| Aug 22, 2026 | 5.5 s |
| Aug 29, 2026 | 5.7 s |
| Sep 5, 2026 | 5.8 s |
| Sep 12, 2026 | 5.8 s |
| Sep 19, 2026 | 5.8 s |
| Sep 26, 2026 | 5.7 s |
| Oct 3, 2026 | 5.5 s |
| Oct 10, 2026 | 5.7 s |
| Oct 17, 2026 | 5.8 s |
| Oct 24, 2026 | 5.9 s |
| Oct 31, 2026 | 6.1 s |
| Nov 7, 2026 | 6.2 s |
| Nov 14, 2026 | 6.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 373 ms |
| Jun 6, 2026 | 367 ms |
| Jun 13, 2026 | 375 ms |
| Jun 20, 2026 | 377 ms |
| Jun 27, 2026 | 367 ms |
| Jul 4, 2026 | 377 ms |
| Jul 11, 2026 | 362 ms |
| Jul 18, 2026 | 363 ms |
| Jul 25, 2026 | 364 ms |
| Aug 1, 2026 | 352 ms |
| Aug 8, 2026 | 338 ms |
| Aug 15, 2026 | 314 ms |
| Aug 22, 2026 | 305 ms |
| Aug 29, 2026 | 313 ms |
| Sep 5, 2026 | 308 ms |
| Sep 12, 2026 | 324 ms |
| Sep 19, 2026 | 346 ms |
| Sep 26, 2026 | 339 ms |
| Oct 3, 2026 | 376 ms |
| Oct 10, 2026 | 411 ms |
| Oct 17, 2026 | 410 ms |
| Oct 24, 2026 | 427 ms |
| Oct 31, 2026 | 427 ms |
| Nov 7, 2026 | 424 ms |
| Nov 14, 2026 | 424 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.6 s
1.2 s
1.8 s
2.3 s
2.9 s
3.5 s
4.1 s
4.7 s
Speed
Document request latency
2.0 sThe HTML itself could arrive about 2.0 s sooner: redirects, a slow server response or missing compression delay everything after it.
Reduce initial server response time
2.0 sReduce initial server response time. Google estimates savings of 2.0 s on a phone.
Render-blocking requests
1.4 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Main-thread work: 7.6 s
A phone's processor spends 7.6 s on main-thread work while loading, 4.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Server response: 2.1 s
2.1 sYour server takes 2.1 s to send the HTML. Google recommends under 600 ms; everything else waits for it.
Use efficient cache lifetimes
62.0 MB31 files are served with short cache lifetimes, so returning visitors download them again (62.0 MB).
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Optanon and others), adding 1.0 MB and 1.2 s of main-thread time.
Mobile performance score: 54
54/100Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 675 ms. During a long task the page ignores taps.
Google Tag Manager adds 621 ms
621 msGoogle Tag Manager costs a phone 621 ms of main-thread work and 519 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.
Reduce unused JavaScript
394 KiBAbout 394 KiB of JavaScript is downloaded but never used on this page.
Improve image delivery
365 KiB4 images could be 365 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Facebook adds 302 ms
302 msFacebook costs a phone 302 ms of main-thread work and 246 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.
1,681 HTML elements
The page has 1,681 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused CSS
250 ms · 123 KiBAbout 123 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 250 ms faster on a phone.
Legacy JavaScript
20 KiBPolyfills for old browsers add 20 KiB JavaScript that modern phones do not need.
Minify CSS
9 KiB9 KiB could be saved by minifying CSS.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Core Web Vitals
Fails Core Web Vitals for real visitors
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-user LCP: 6.5 s
6.5 sReal visitors wait 6.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 520 ms
520 msReal visitors wait 520 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 6.1 s
6.1 sReal visitors see the first content after 6.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.5 s
2.5 sReal visitors wait 2.5 s for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 17.2 s
17.2 sVisually, the page fills in at 17.2 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 34.6 s
34.6 sThe page becomes fully interactive after 34.6 s. Good is under 3.8 s.
Total Blocking Time: 1.4 s
1.4 sScripts block taps and scrolling for 1.4 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
Largest content (LCP) got 27% slower for real visitors
+27%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 4.7 s to 6.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest Contentful Paint: 3.0 s
3.0 sYour largest element takes 3.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Sustaining technology ecosystems that help commerce evolve,…”. Most of its time is time to first byte (2.1 s).
Tap response (INP) got 15% slower for real visitors
+15%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 373 ms to 424 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 73.1 MB in 98 requests
73.1 MBYour homepage downloads 73.1 MB in 98 requests on a phone: media 56.6 MB (8), images 13.3 MB (26) and scripts 1.1 MB (22). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 4.0 MB together. On a phone connection a single image that size takes seconds.
7 images far larger than shown
3.7 MB7 images are downloaded at several times the size a phone draws them, for example 7kYh19v5iJDGfKlS6zVn56--M12.png at 1,676 px wide, shown at 220 px. Resized copies would save about 3.7 MB.
8 images below the first screen load straight away
8 images further down the page (5.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 20.7 g of CO₂ per visit
20.72 gBy the Sustainable Web Design model, a visit to your homepage emits about 20.72 g of CO₂e: 2486.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
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.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
8 links without text
8 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 26 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 3 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
96 internal links, 9 external
The homepage links to 96 pages on interswitchgroup.com and 9 external pages.
7 checks passed
Meta description: 147 characters
Your meta description is 147 characters: “Interswitch is a leading pan-African digital payments and commerce company, enabling secure, reliable transactions acro…”.
One H1 headline
Your main headline reads: “Building the Rails of Africa’s Digital Future”.
Title: 53 characters
Your title is a healthy 53 characters: “Interswitch | Powering Digital Payments Across Africa”.
Canonical URL set
The canonical URL is https://interswitchgroup.com/.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://interswitchgroup.com/sitemap-index.xml.
AI search readiness
No Organization structured data
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.
No llms.txt
There is no https://interswitchgroup.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.
2 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (972 words), so crawlers that don't run JavaScript still read it.
Other pages
3 pages share a title
https://interswitchgroup.com/company, https://interswitchgroup.com/company/leadership and https://interswitchgroup.com/company/brands all use the title “Interswitch | Company”. Search engines can't tell which page to show for a search, so each competes with the others.
12 pages share a meta description
https://interswitchgroup.com/solutions/wellness, https://interswitchgroup.com/solutions/energy, https://interswitchgroup.com/solutions/real-estate, https://interswitchgroup.com/solutions/mobility, https://interswitchgroup.com/solutions/social and https://interswitchgroup.com/products/individual and 6 others use the same meta description. A description written for each page earns more clicks.
10 pages slow to respond
https://interswitchgroup.com/solutions/wellness, https://interswitchgroup.com/solutions/energy, https://interswitchgroup.com/solutions/real-estate, https://interswitchgroup.com/solutions/mobility, https://interswitchgroup.com/solutions/social and https://interswitchgroup.com/products/individual and 4 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 41 found) and read each the way a search engine does.
6 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 14 pages that loaded have a meta description.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
11 of 11 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 406 words of copy
The homepage carries about 406 words of visible text.
2 checks passed
1 call to action
The homepage has 1 call to action, for example “Contact Us”.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
11 cookies set on arrival
11Opening the homepage sets 11 cookies (measured from a US location before any click).
20 other companies contacted
Loading the homepage contacts 20 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at interswitchgroup.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Astro
- Analytics
- Google Tag Manager
- Hosting
- Ipartners Limited Ipartners Limited
Company
- Founded
- 2002
- Headquarters
- Lagos
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on interswitchgroup.com, including 25 speed issues, 1 SEO issue and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.