Website review, no card needed

flutterwave.com logo

flutterwave.com website review

Visit site (opens in a new tab)Reviewed 19 November 202643 issues · 88 checks

This review found 43 issues worth fixing on flutterwave.com, 11 of them high impact, across 88 checks. The most urgent: reduce unused JavaScript. 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.5 s3.9 sMay 30Nov 144.2 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20265.1 s
Jun 6, 20265.2 s
Jun 13, 20265.3 s
Jun 20, 20265.0 s
Jun 27, 20265.0 s
Jul 4, 20265.0 s
Jul 11, 20264.9 s
Jul 18, 20265.0 s
Jul 25, 20264.9 s
Aug 1, 20264.8 s
Aug 8, 20264.6 s
Aug 15, 20264.5 s
Aug 22, 20264.4 s
Aug 29, 20264.4 s
Sep 5, 20264.4 s
Sep 12, 20264.4 s
Sep 19, 20264.4 s
Sep 26, 20264.3 s
Oct 3, 20264.3 s
Oct 10, 20264.3 s
Oct 17, 20264.2 s
Oct 24, 20264.2 s
Oct 31, 20264.1 s
Nov 7, 20264.1 s
Nov 14, 20264.2 s
Real-visitor tap response (INP)75th percentile, phones
446 ms319 msMay 30Nov 14355 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026431 ms
Jun 6, 2026429 ms
Jun 13, 2026426 ms
Jun 20, 2026412 ms
Jun 27, 2026410 ms
Jul 4, 2026417 ms
Jul 11, 2026411 ms
Jul 18, 2026410 ms
Jul 25, 2026408 ms
Aug 1, 2026397 ms
Aug 8, 2026392 ms
Aug 15, 2026393 ms
Aug 22, 2026395 ms
Aug 29, 2026393 ms
Sep 5, 2026396 ms
Sep 12, 2026394 ms
Sep 19, 2026373 ms
Sep 26, 2026350 ms
Oct 3, 2026338 ms
Oct 10, 2026334 ms
Oct 17, 2026336 ms
Oct 24, 2026338 ms
Oct 31, 2026338 ms
Nov 7, 2026347 ms
Nov 14, 2026355 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

Full-page screenshot of flutterwave.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. flutterwave.com at 0.4 s0.4 s
  2. flutterwave.com at 0.8 s0.8 s
  3. flutterwave.com at 1.2 s1.2 s
  4. flutterwave.com at 1.6 s1.6 s
  5. flutterwave.com at 2.0 s2.0 s
  6. flutterwave.com at 2.4 s2.4 s
  7. flutterwave.com at 2.8 s2.8 s
  8. flutterwave.com at 3.2 s3.2 s

Speed

11 to fix66
  • Reduce unused JavaScript

    1.1 s · 458 KiB

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

  • Mobile performance score: 66

    66/100

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

  • Improve image delivery

    746 KiB

    4 images could be 746 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Render-blocking requests

    450 ms

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, uptrendsdata.com and Mixpanel and others), adding 1.4 MB and 302 ms of main-thread time.

  • Legacy JavaScript

    350 ms · 48 KiB

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

  • Use efficient cache lifetimes

    323 KiB

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

  • Main-thread work: 3.1 s

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

  • 6 long tasks on the main thread

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

  • Google Tag Manager adds 221 ms

    221 ms

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

  • myflutterwave.com adds 0 ms

    0 ms

    myflutterwave.com costs a phone 0 ms of main-thread work and 1,000 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 CSS

    113 KiB

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

  • Font display

    50 ms

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

  • Minify CSS

    15 KiB

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

1 checks passed
  • Server response: 86 ms

    86 ms

    Your server sent the HTML in 86 ms, well inside Google's 600 ms guideline.

Core Web Vitals

10 to fix33
  • 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 FCP: 3.0 s

    3.0 s

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

  • Real-user TTFB: 1.9 s

    1.9 s

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

  • Largest Contentful Paint: 6.9 s

    6.9 s

    Your largest element takes 6.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Endless possibilities for all”.

  • Time to Interactive: 13.7 s

    13.7 s

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

  • Real-user LCP: 3.7 s

    3.7 s

    Real visitors wait 3.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 384 ms

    384 ms

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

  • Speed Index: 4.7 s

    4.7 s

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

  • Total Blocking Time: 295 ms

    295 ms

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

  • 11 images without width and height

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

5 checks passed
  • Real-user CLS: 0.07

    0.07

    For real visitors the layout shifts by 0.07 (75th percentile). Good is under 0.1.

  • Tap response (INP) got 18% faster for real visitors

    -18%

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

  • Largest content (LCP) got 19% faster for real visitors

    -19%

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

  • First Contentful Paint: 1.5 s

    1.5 s

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

  • Cumulative Layout Shift: 0.04

    0.04

    The layout barely moves while loading (CLS 0.04, good is under 0.1).

Images and page weight

4 to fix50
  • 1 image over 500 KB

    2kjHjZXJTXsrsN7v5m9S weighs 630 KiB. On a phone connection a single image that size takes seconds.

  • Page weight: 3.1 MB in 63 requests

    3.1 MB

    Your homepage downloads 3.1 MB in 63 requests on a phone: scripts 1.3 MB (19), images 1.3 MB (35) and fonts 299 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 3 images in older formats

    3 images (788 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • 2 images far larger than shown

    110 KiB

    2 images are downloaded at several times the size a phone draws them, for example 2kjHjZXJTXsrsN7v5m9S at 1,100 px wide, shown at 350 px. Resized copies would save about 110 KiB.

  • 2 images below the first screen load straight away

    2 images further down the page (159 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.9 g of CO₂ per visit

    0.87 g

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

Accessibility

7 to fixGoogle 8390
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 9 text elements with low contrast

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

  • All page content should be contained by landmarks (3 elements)

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

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

  • Page should contain a level-one heading (1 element)

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

  • 2 form fields without a label

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 34 images in the HTML carry an alt attribute.

  • 35 automated accessibility rules passed

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

SEO

4 to fixGoogle 9180
  • No H1 headline

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

  • No canonical URL

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

  • No robots.txt

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

  • 6 links with vague text

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

  • 61 internal links, 28 external

    The homepage links to 61 pages on flutterwave.com and 28 external pages.

5 checks passed
  • Meta description: 127 characters

    Your meta description is 127 characters: “Unlocking boundless payment opportunities for enterprises, individuals, small businesses, emerging markets, and startup…”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “Endless possibilities for every business - Flutterwave”.

  • Structured data in place

    Structured data found: Organization.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • XML sitemap found

    Your XML sitemap is reachable at https://flutterwave.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://flutterwave.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.

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

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (924 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix86
  • 2 pages share a title

    https://flutterwave.com/us and / all use the title “Endless possibilities for every business - Flutterwave”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages share a meta description

    / and https://flutterwave.com/us/invoices use the same meta description. A description written for each page earns more clicks.

  • 13 pages without an H1

    https://flutterwave.com/us/collect-payments, https://flutterwave.com/us/send-money, https://flutterwave.com/us/swap, /, https://flutterwave.com/us/integrations and https://flutterwave.com/us/payment-links and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    13 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 13 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9278
  • 1 broken image

    1 image failed to load on a phone, for example https://rave-services.myflutterwave.com/v1/services/filestack/download/tijScS6SUSAi5ZTfIf9Q?resize=1&width=1200.

  • 2 small tap targets

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

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix90
  • Thin social proof

    Social proof on the homepage: 2 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 640 words of copy

    The homepage carries about 640 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact sales”.

  • 12 calls to action

    The homepage has 12 calls to action, for example “Download the mobile app”, “Download Send mobile app” and “Pricing”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Mixpanel (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.

  • 7 cookies set on arrival

    7

    Opening the homepage sets 7 cookies, 1 of them by other companies (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.

  • 5 other companies contacted

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

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

Upkeep, stack and company

Stack

CMS
WordPress
Framework
Nuxt
Analytics
Google Tag Manager
Hosting
Cloudflare

Company

Headquarters
San Francisco

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on flutterwave.com, including 21 speed issues, 4 SEO issues and 1 conversion gap. 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