Website review, no card needed
palmpay.com website review
Visit site (opens in a new tab)Reviewed 30 October 202637 issues · 62 checks
This review found 37 issues worth fixing on palmpay.com, 18 of them high impact, across 62 checks. The most urgent: use efficient cache lifetimes. 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
55FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 7.4 s |
| May 16, 2026 | 7.4 s |
| May 23, 2026 | 5.9 s |
| May 30, 2026 | 5.9 s |
| Jun 6, 2026 | 5.9 s |
| Jun 13, 2026 | 6.0 s |
| Jun 20, 2026 | 7.5 s |
| Jun 27, 2026 | 7.3 s |
| Jul 4, 2026 | 7.1 s |
| Jul 11, 2026 | 7.2 s |
| Jul 18, 2026 | 6.8 s |
| Jul 25, 2026 | 6.2 s |
| Aug 1, 2026 | 6.5 s |
| Aug 8, 2026 | 6.5 s |
| Aug 15, 2026 | 6.6 s |
| Aug 22, 2026 | 7.1 s |
| Aug 29, 2026 | 6.5 s |
| Sep 5, 2026 | 6.7 s |
| Sep 12, 2026 | 6.7 s |
| Sep 19, 2026 | 6.5 s |
| Sep 26, 2026 | 7.1 s |
| Oct 3, 2026 | 6.9 s |
| Oct 10, 2026 | 7.0 s |
| Oct 17, 2026 | 7.1 s |
| Oct 24, 2026 | 7.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 429 ms |
| May 16, 2026 | 417 ms |
| May 23, 2026 | 319 ms |
| May 30, 2026 | 287 ms |
| Jun 6, 2026 | 295 ms |
| Jun 13, 2026 | 301 ms |
| Jun 20, 2026 | 363 ms |
| Jun 27, 2026 | 383 ms |
| Jul 4, 2026 | 378 ms |
| Jul 11, 2026 | 384 ms |
| Jul 18, 2026 | 370 ms |
| Jul 25, 2026 | 353 ms |
| Aug 1, 2026 | 362 ms |
| Aug 8, 2026 | 358 ms |
| Aug 15, 2026 | 365 ms |
| Aug 22, 2026 | 374 ms |
| Aug 29, 2026 | 365 ms |
| Sep 5, 2026 | 381 ms |
| Sep 12, 2026 | 369 ms |
| Sep 19, 2026 | 356 ms |
| Sep 26, 2026 | 355 ms |
| Oct 3, 2026 | 348 ms |
| Oct 10, 2026 | 356 ms |
| Oct 17, 2026 | 372 ms |
| Oct 24, 2026 | 374 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
Speed
Use efficient cache lifetimes
4.3 s · 2.0 MB51 files are served with short cache lifetimes, so returning visitors download them again (2.0 MB).
Mobile performance score: 51
51/100Your mobile performance score is 51. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
802 KiB5 images could be 802 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Render-blocking requests
500 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 500 ms.
3 third-party services on the page
3 third-party services load with your homepage (Google Fonts, Ipify and chuanyinet.com), adding 1.8 MB and 1 ms of main-thread time.
chuanyinet.com adds 0 ms
0 mschuanyinet.com costs a phone 0 ms of main-thread work and 1.8 MB 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
160 ms · 25 KiBAbout 25 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 160 ms faster on a phone.
Legacy JavaScript
14 KiBPolyfills for old browsers add 14 KiB JavaScript that modern phones do not need.
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: 0.5 s
A phone's processor spends 0.5 s on main-thread work while loading, 227 ms of it running JavaScript. That is comfortably low.
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: 7.4 s
7.4 sReal visitors wait 7.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.91
0.91For real visitors the layout shifts by 0.91 (75th percentile). Good is under 0.1.
Real-user FCP: 5.4 s
5.4 sReal visitors see the first content after 5.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.2 s
2.2 sReal visitors wait 2.2 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 8.0 s
8.0 sYour largest element takes 8.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Banking the next billion From smartphone ownership to full-…”.
Cumulative Layout Shift: 0.931
0.931The layout shifts by 0.931 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Time to Interactive: 8.1 s
8.1 sThe page becomes fully interactive after 8.1 s. Good is under 3.8 s.
Real-user INP: 359 ms
359 msReal visitors wait 359 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest content (LCP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 7.4 s to 7.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Tap response (INP) got 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 429 ms to 374 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 2.4 s
2.4 sVisually, the page fills in at 2.4 s (Speed Index), inside the 3.4 s “good” threshold.
First Contentful Paint: 0.8 s
0.8 sThe first text or image appears after 0.8 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.2 MB in 62 requests
2.2 MBYour homepage downloads 2.2 MB in 62 requests on a phone: images 1.8 MB (22), scripts 275 KiB (20) and fonts 78 KiB (6). Under 2 MB keeps phones on slow connections fast.
About 0.6 g of CO₂ per visit
0.61 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.61 g of CO₂e: 73.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
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.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
1 checks passed
35 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 39 WCAG 2.2 A/AA and best-practice rules on the phone render: 35 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No page title
Your page has no <title>, so Google has to invent the blue link in search results.
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
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.
Only 0 internal links
The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.
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.
2 checks passed
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.palmpay.com/sitemap.xml.
AI search readiness
Most text only appears after JavaScript runs
0%A phone browser shows 849 words, but the HTML your server sends has only 0. 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://palmpay.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.
1 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.
Best practices
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
13 of 14 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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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.
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 849 words of copy
The homepage carries about 849 words of visible text.
Privacy and tracking
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.
4 other companies contacted
Loading the homepage contacts 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 palmpay.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
- Next.js
- Hosting
- Cloudflare
Company
- Founded
- 2019
- Headquarters
- Lagos
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on palmpay.com, including 15 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.