Website review, no card needed

simfy.africa logo

simfy.africa website review

Visit site (opens in a new tab)Reviewed 31 October 202628 issues · 65 checks

This review found 28 issues worth fixing on simfy.africa, 7 of them high impact, across 65 checks. The most urgent: 1 text element with low contrast. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
5.1 s4.8 sJul 18Aug 155.1 s
Show as table
DateReal-visitor load time (LCP)
Jul 18, 20264.9 s
Jul 25, 20265.0 s
Aug 1, 20264.8 s
Aug 8, 20264.9 s
Aug 15, 20265.1 s

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

Full-page screenshot of simfy.africa (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. simfy.africa at 0.4 s0.4 s
  2. simfy.africa at 0.8 s0.8 s
  3. simfy.africa at 1.1 s1.1 s
  4. simfy.africa at 1.5 s1.5 s
  5. simfy.africa at 1.9 s1.9 s
  6. simfy.africa at 2.3 s2.3 s
  7. simfy.africa at 2.6 s2.6 s
  8. simfy.africa at 3.0 s3.0 s

Speed

4 to fix51
  • Mobile performance score: 51

    51/100

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

  • Improve image delivery

    750 ms · 150 KiB

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

  • Render-blocking requests

    550 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 550 ms.

  • Reduce unused CSS

    450 ms · 86 KiB

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

  • Font display

    200 ms

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

  • Reduce unused JavaScript

    150 ms · 49 KiB

    About 49 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Legacy JavaScript

    150 ms · 12 KiB

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

  • 4 long tasks on the main thread

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Main-thread work: 1.5 s

    A phone's processor spends 1.5 s on main-thread work while loading, 893 ms of it running JavaScript. That is comfortably low.

Core Web Vitals

4 to fix39
  • Largest Contentful Paint: 6.8 s

    6.8 s

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

  • Cumulative Layout Shift: 0.651

    0.651

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

  • Time to Interactive: 6.8 s

    6.8 s

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

  • Speed Index: 4.4 s

    4.4 s

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

  • Largest content (LCP) held steady for real visitors

    +1%

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • First Contentful Paint: 0.8 s

    0.8 s

    The first text or image appears after 0.8 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 51 ms

    51 ms

    Scripts block the page for only 51 ms while loading. Good is under 200 ms.

Images and page weight

100
  • About 0.3 g of CO₂ per visit

    0.35 g

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

4 checks passed
  • Page weight: 1.2 MB in 38 requests

    1.2 MB

    Your homepage downloads 1.2 MB in 38 requests on a phone: images 470 KiB (9), fonts 447 KiB (3) and scripts 187 KiB (13). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

1 to fixGoogle 9697
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

2 checks passed
  • Every image has alt text

    All 7 images in the HTML carry an alt attribute.

  • 33 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 34 WCAG 2.2 A/AA and best-practice rules on the phone render: 33 passed and 1 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

8 to fixGoogle 10062
  • No H1 headline

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

  • Title is short (12 characters)

    Your title is only 12 characters: “Simfy Africa”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://simfy.africa/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at simfy.africa/robots.txt, the first file search crawlers ask for.

  • No favicon declared

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

  • No X (Twitter) card tag

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

  • 14 internal links, 6 external

    The homepage links to 14 pages on simfy.africa and 6 external pages.

1 checks passed
  • Meta description: 88 characters

    Your meta description is 88 characters: “Official Simfy Africa website for company information, jobs and contact form for queries”.

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    18%

    A phone browser shows 247 words, but the HTML your server sends has only 45. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

  • 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://simfy.africa/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.

1 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

Other pages

2 to fix90
  • 7 pages share a title

    /, https://simfy.africa/home, https://simfy.africa/work-with-us, https://simfy.africa/contact-us, https://simfy.africa/mtn-digital-services and https://simfy.africa/terms-and-conditions and 1 other all use the title “Simfy Africa”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 6 pages share a meta description

    https://simfy.africa/home, https://simfy.africa/work-with-us, https://simfy.africa/contact-us, https://simfy.africa/mtn-digital-services, https://simfy.africa/terms-and-conditions and https://simfy.africa/privacy-policy use the same meta description. A description written for each page earns more clicks.

  • 2 pages with very little text

    https://simfy.africa/contact-us and https://simfy.africa/mtn-digital-services have 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.

  • 6 internal pages checked

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

6 checks passed
  • Linked pages load

    All 6 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 6 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 6 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 6 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix42
  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

  • Only about 247 words

    The homepage has only about 247 words of visible text; thin pages give Google and first-time buyers little to go on.

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

1 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact and Partnership”.

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (measured from a US location before any click).

  • No consent tool detected

    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.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 simfy.africa, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Next.js
Hosting
AWS

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on simfy.africa, including 8 speed issues, 8 SEO issues and 5 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25