Website review, no card needed

meniga.com logo

meniga.com website review

Visit site (opens in a new tab)Reviewed 21 October 202629 issues · 79 checks

This review found 29 issues worth fixing on meniga.com, 9 of them high impact, across 79 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
4.2 s3.5 sMay 2Oct 174.0 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.6 s
May 9, 20263.6 s
May 16, 20263.6 s
May 23, 20263.7 s
May 30, 20263.7 s
Jun 6, 20263.8 s
Jun 13, 20263.8 s
Jun 20, 20263.7 s
Jun 27, 20263.7 s
Jul 4, 20263.8 s
Jul 11, 20263.7 s
Jul 18, 20263.8 s
Jul 25, 20263.7 s
Aug 1, 20263.7 s
Aug 8, 20263.7 s
Aug 15, 20263.6 s
Aug 22, 20263.8 s
Aug 29, 20263.7 s
Sep 5, 20263.7 s
Sep 12, 20263.8 s
Sep 19, 20263.9 s
Sep 26, 20264.0 s
Oct 3, 20264.1 s
Oct 10, 20264.0 s
Oct 17, 20264.0 s
Real-visitor tap response (INP)75th percentile, phones
194 ms144 msMay 2Oct 17182 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026165 ms
May 9, 2026167 ms
May 16, 2026171 ms
May 23, 2026174 ms
May 30, 2026173 ms
Jun 6, 2026169 ms
Jun 13, 2026164 ms
Jun 20, 2026156 ms
Jun 27, 2026158 ms
Jul 4, 2026153 ms
Jul 11, 2026150 ms
Jul 18, 2026153 ms
Jul 25, 2026152 ms
Aug 1, 2026153 ms
Aug 8, 2026154 ms
Aug 15, 2026158 ms
Aug 22, 2026160 ms
Aug 29, 2026164 ms
Sep 5, 2026171 ms
Sep 12, 2026171 ms
Sep 19, 2026178 ms
Sep 26, 2026182 ms
Oct 3, 2026181 ms
Oct 10, 2026188 ms
Oct 17, 2026182 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 meniga.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. meniga.com at 0.5 s0.5 s
  2. meniga.com at 1.0 s1.0 s
  3. meniga.com at 1.4 s1.4 s
  4. meniga.com at 1.9 s1.9 s
  5. meniga.com at 2.4 s2.4 s
  6. meniga.com at 2.9 s2.9 s
  7. meniga.com at 3.3 s3.3 s
  8. meniga.com at 3.8 s3.8 s

Speed

8 to fix66
  • Reduce unused JavaScript

    1.4 s · 174 KiB

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

  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 66

    66/100

    Your mobile performance score is 66 (desktop: 78). Pages that score under 90 lose visitors before the first paint.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Cookie-Script.com and Clarity and others), adding 513 KiB and 505 ms of main-thread time.

  • Reduce unused CSS

    300 ms · 65 KiB

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

  • Google Tag Manager adds 240 ms

    240 ms

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

  • Main-thread work: 2.0 s

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

  • 1,826 HTML elements

    The page has 1,826 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Use efficient cache lifetimes

    150 ms · 49 KiB

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

  • 7 long tasks on the main thread

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

  • Legacy JavaScript

    50 ms · 15 KiB

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

  • Improve image delivery

    43 KiB

    1 image could be 43 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Minify JavaScript

    13 KiB

    13 KiB could be saved by minifying JavaScript.

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

1 checks passed
  • Server response: 2 ms

    2 ms

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

Core Web Vitals

9 to fix67
  • 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: 4.0 s

    4.0 s

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

  • Real-user FCP: 3.3 s

    3.3 s

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

  • Largest Contentful Paint: 7.3 s

    7.3 s

    Your largest element takes 7.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “This website uses cookies to improve user experience. By us…”. Most of its time is element render delay (3.3 s).

  • Time to Interactive: 7.3 s

    7.3 s

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

  • Real-user TTFB: 1.5 s

    1.5 s

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

  • Speed Index: 5.1 s

    5.1 s

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

  • First Contentful Paint: 2.6 s

    2.6 s

    The first text or image appears after 2.6 s on a phone. Good is under 1.8 s.

  • 2 images without width and height

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

  • Tap response (INP) got 11% slower for real visitors

    +11%

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

  • Largest content (LCP) got 12% slower for real visitors

    +12%

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

4 checks passed
  • Real-user INP: 185 ms

    185 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Total Blocking Time: 179 ms

    179 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix68
  • Page weight: 3.3 MB in 100 requests

    3.3 MB

    Your homepage downloads 3.3 MB in 100 requests on a phone: images 2.6 MB (76), scripts 537 KiB (14) and stylesheets 68 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 34 images below the first screen load straight away

    34 images further down the page (2.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 1 image far larger than shown

    6 KiB

    1 image is downloaded at several times the size a phone draws it, for example transform.png.webp at 935 px wide, shown at 296 px. Resized copies would save about 6 KiB.

  • About 0.9 g of CO₂ per visit

    0.92 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.92 g of CO₂e: 110.7 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

3 to fixGoogle 9796
  • Links must have discernible text (3 elements)

    Links must have discernible text: 3 elements on the page fail this check, rated serious by axe-core.

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

    All page content should be contained by landmarks: 18 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.

2 checks passed
  • Every image has alt text

    All 102 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

SEO

1 to fixGoogle 9298
  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 121 internal links, 4 external

    The homepage links to 121 pages on meniga.com and 4 external pages.

8 checks passed
  • Meta description: 110 characters

    Your meta description is 110 characters: “Meniga is a global leader in digital banking solutions, serving over 100 million customers across 30 countries”.

  • One H1 headline

    Your main headline reads: “The Hyper-Personalised Banking Platform”.

  • Title: 47 characters

    Your title is a healthy 47 characters: “Personalised Digital Banking Solutions - Meniga”.

  • Canonical URL set

    The canonical URL is https://www.meniga.com/.

  • Structured data in place

    Structured data found: WebPage.

  • 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.meniga.com/sitemap.xml.

AI search readiness

2 to fix75
  • 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.

  • Some text only appears after JavaScript runs

    58%

    The HTML your server sends has 1,457 of the 2,514 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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.

  • llms.txt published

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

Other pages

1 to fix75
  • 9 linked pages are broken

    Your homepage links to https://www.meniga.com/products/cashflow-forecasting, https://www.meniga.com/products/open-banking, https://www.meniga.com/products/sustainability, https://www.meniga.com/solutions/agentic-banking, https://www.meniga.com/solutions/hyper-personalise-engagement and https://www.meniga.com/solutions/create-neobank-grade-customer-experiences and 3 others, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 15 internal pages checked

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

6 checks passed
  • 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.

  • Titles are unique

    Every page we checked has its own title.

  • 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

Google 100100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    29 of 32 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix90
  • 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 2,514 words of copy

    The homepage carries about 2,514 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 Us” and “Contact our team”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact Us”, “Contact our team” and “Get In Touch”.

  • Social proof on the page

    Social proof on the homepage: 9 customer or partner logos and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Microsoft Clarity, Hotjar and Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 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.

  • 15 other companies contacted

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on meniga.com, including 17 speed issues, 1 SEO issue 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