Website review, no card needed

Taptap Send logo

taptapsend.com website review

Visit site (opens in a new tab)Reviewed 4 November 202624 issues · 84 checks

This review found 24 issues worth fixing on taptapsend.com, 5 of them high impact, across 84 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

Read the full growth playbook for Taptap Send

  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
2.1 s2.0 sMay 16Oct 312.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.1 s
May 23, 20262.1 s
May 30, 20262.1 s
Jun 6, 20262.1 s
Jun 13, 20262.1 s
Jun 20, 20262.1 s
Jun 27, 20262.1 s
Jul 4, 20262.1 s
Jul 11, 20262.1 s
Jul 18, 20262.1 s
Jul 25, 20262.1 s
Aug 1, 20262.1 s
Aug 8, 20262.0 s
Aug 15, 20262.0 s
Aug 22, 20262.0 s
Aug 29, 20262.0 s
Sep 5, 20262.0 s
Sep 12, 20262.0 s
Sep 19, 20262.0 s
Sep 26, 20262.0 s
Oct 3, 20262.1 s
Oct 10, 20262.1 s
Oct 17, 20262.1 s
Oct 24, 20262.1 s
Oct 31, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
157 ms141 msMay 16Oct 31155 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026147 ms
May 23, 2026147 ms
May 30, 2026146 ms
Jun 6, 2026146 ms
Jun 13, 2026145 ms
Jun 20, 2026145 ms
Jun 27, 2026144 ms
Jul 4, 2026144 ms
Jul 11, 2026144 ms
Jul 18, 2026143 ms
Jul 25, 2026145 ms
Aug 1, 2026147 ms
Aug 8, 2026150 ms
Aug 15, 2026151 ms
Aug 22, 2026152 ms
Aug 29, 2026151 ms
Sep 5, 2026151 ms
Sep 12, 2026151 ms
Sep 19, 2026150 ms
Sep 26, 2026152 ms
Oct 3, 2026153 ms
Oct 10, 2026154 ms
Oct 17, 2026155 ms
Oct 24, 2026155 ms
Oct 31, 2026155 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 taptapsend.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

7 to fix69
  • Render-blocking requests

    1.0 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and website-files.com and others), adding 1.8 MB and 1.0 s of main-thread time.

  • Mobile performance score: 69

    69/100

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

  • Google Tag Manager adds 484 ms

    484 ms

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

    327 KiB

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

  • Use efficient cache lifetimes

    251 KiB

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

  • website-files.com adds 107 ms

    107 ms

    website-files.com costs a phone 107 ms of main-thread work and 922 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.

  • Font display

    250 ms

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

  • 10 long tasks on the main thread

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

  • Reduce unused CSS

    150 ms · 24 KiB

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

  • Improve image delivery

    30 KiB

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

  • Legacy JavaScript

    21 KiB

    Polyfills for old browsers add 21 KiB JavaScript that modern phones do not need.

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

2 checks passed
  • Main-thread work: 2.0 s

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

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

4 to fix100
  • Time to Interactive: 13.9 s

    13.9 s

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

  • Largest Contentful Paint: 4.5 s

    4.5 s

    Your largest element takes 4.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Send money internationally. Fast delivery, zero hassle”.

  • 79 images without width and height

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

  • Total Blocking Time: 473 ms

    473 ms

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

  • Tap response (INP) held steady for real visitors

    +5%

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

  • Largest content (LCP) held steady for real visitors

    0%

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

9 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 2.1 s

    2.1 s

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

  • Real-user INP: 170 ms

    170 ms

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

  • Real-user CLS: 0.02

    0.02

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

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Real-user TTFB: 718 ms

    718 ms

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

  • Speed Index: 3.3 s

    3.3 s

    Visually, the page fills in at 3.3 s (Speed Index), inside the 3.4 s “good” threshold.

  • First Contentful Paint: 1.7 s

    1.7 s

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

  • Cumulative Layout Shift: 0.085

    0.085

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

Images and page weight

1 to fix85
  • Page weight: 2.1 MB in 171 requests

    2.1 MB

    Your homepage downloads 2.1 MB in 171 requests on a phone: scripts 1.1 MB (36), fonts 473 KiB (18) and images 428 KiB (94). Under 2 MB keeps phones on slow connections fast.

  • About 0.6 g of CO₂ per visit

    0.59 g

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

3 checks passed
  • 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

5 to fixGoogle 8394
  • Unlabelled dropdowns

    2 dropdowns have no label.

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

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

  • Zoom is disabled

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

  • 4 form fields without a label

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

2 checks passed
  • Every image has alt text

    All 84 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

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

SEO

Google 100100
  • 35 internal links, 8 external

    The homepage links to 35 pages on taptapsend.com and 8 external pages.

8 checks passed
  • Meta description: 159 characters

    Your meta description is 159 characters: “Send money to Africa, Asia and Latin America in minutes. Competitive exchange rates, no fees on most transfers, and tru…”.

  • One H1 headline

    Your main headline reads: “Send money internationally. Fast delivery, zero hassle”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “Taptap Send | Send Money to Africa, Asia and Latin America”.

  • Canonical URL set

    The canonical URL is https://www.taptapsend.com/en.

  • Structured data in place

    Structured data found: FinancialService, MobileApplication, Organization and WebSite.

  • 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://www.taptapsend.com/sitemap.xml.

AI search readiness

100
4 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.

  • Organization data: 5 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.taptapsend.com/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix93
  • 2 pages share a title

    https://www.taptapsend.com/en and https://www.taptapsend.com/es-us all use the title “Taptap Send | Send Money to Africa, Asia and Latin America”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

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

Best practices

2 to fixGoogle 9291
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “($.empty , availableCorridors) is not iterable”.

  • 2 distorted images

    2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

2 checks passed
  • Tap targets are thumb-sized

    11 of 13 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • 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 phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 726 words of visible text.

5 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Join our team” and “Contact us”.

  • 2 short forms

    2 short forms (4 fields at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 13 testimonial or review blocks, a star rating and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 23 other companies contacted

    Loading the homepage contacts 23 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 taptapsend.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
Webflow
Framework
Bootstrap
Analytics
Google Analytics | Google Tag Manager
Hosting
Webflow

Hiring

Hiring
27 open roles
Teams
Markets (6), Engineering (4), Finance (4), Customer Experience (2)
Job board
ashby

Company

Founded
2018

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 24 issues on taptapsend.com, including 11 speed issues 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

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