Website review, no card needed

conversebank.am logo

conversebank.am website review

Visit site (opens in a new tab)Reviewed 31 October 202661 issues · 84 checks

This review found 61 issues worth fixing on conversebank.am, 27 of them high impact, across 84 checks. The most urgent: use efficient cache lifetimes. 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
6.6 s753 msMay 9Oct 245.3 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.8 s
May 16, 20263.7 s
May 23, 20263.7 s
May 30, 20263.1 s
Jun 6, 20262.1 s
Jun 13, 20261.5 s
Jun 20, 20261.4 s
Jun 27, 20261.8 s
Jul 4, 20262.4 s
Jul 11, 20263.0 s
Jul 18, 20263.3 s
Jul 25, 20262.7 s
Aug 1, 20262.1 s
Aug 8, 20262.1 s
Aug 15, 20262.2 s
Aug 22, 20262.2 s
Aug 29, 20262.5 s
Sep 5, 20262.9 s
Sep 12, 20263.4 s
Sep 19, 20264.7 s
Sep 26, 20265.5 s
Oct 3, 20265.8 s
Oct 10, 20265.9 s
Oct 17, 20265.7 s
Oct 24, 20265.3 s
Real-visitor tap response (INP)75th percentile, phones
418 ms256 msMay 9Oct 24364 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026305 ms
May 16, 2026311 ms
May 23, 2026311 ms
May 30, 2026309 ms
Jun 6, 2026301 ms
Jun 13, 2026287 ms
Jun 20, 2026275 ms
Jun 27, 2026277 ms
Jul 4, 2026288 ms
Jul 11, 2026298 ms
Jul 18, 2026306 ms
Jul 25, 2026297 ms
Aug 1, 2026281 ms
Aug 8, 2026284 ms
Aug 15, 2026292 ms
Aug 22, 2026293 ms
Aug 29, 2026300 ms
Sep 5, 2026304 ms
Sep 12, 2026305 ms
Sep 19, 2026334 ms
Sep 26, 2026367 ms
Oct 3, 2026381 ms
Oct 10, 2026399 ms
Oct 17, 2026395 ms
Oct 24, 2026364 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 conversebank.am (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. conversebank.am at 1.2 s1.2 s
  2. conversebank.am at 2.4 s2.4 s
  3. conversebank.am at 3.7 s3.7 s
  4. conversebank.am at 4.9 s4.9 s
  5. conversebank.am at 6.1 s6.1 s
  6. conversebank.am at 7.3 s7.3 s
  7. conversebank.am at 8.5 s8.5 s
  8. conversebank.am at 9.7 s9.7 s

Speed

13 to fix32
  • Use efficient cache lifetimes

    23.4 s · 16.4 MB

    39 files are served with short cache lifetimes, so returning visitors download them again (16.4 MB).

  • Improve image delivery

    1.3 s · 11.2 MB

    8 images could be 11.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.3 s faster on a phone.

  • Reduce unused JavaScript

    10.7 s · 1.7 MB

    About 1.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 10.7 s faster on a phone.

  • Mobile performance score: 32

    32/100

    Your mobile performance score is 32. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 4.0 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Google CDN and Facebook and others), adding 2.1 MB and 1.2 s of main-thread time.

  • Reduce unused CSS

    910 ms · 186 KiB

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

  • Render-blocking requests

    750 ms

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

  • 15 long tasks on the main thread

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

  • Font display

    550 ms

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

  • Google Tag Manager adds 460 ms

    460 ms

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

  • Google CDN adds 391 ms

    391 ms

    Google CDN costs a phone 391 ms of main-thread work and 734 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.

  • LiveChat adds 67 ms

    67 ms

    LiveChat costs a phone 67 ms of main-thread work and 366 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.

  • Legacy JavaScript

    150 ms · 25 KiB

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

  • 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: 1 ms

    1 ms

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

Core Web Vitals

12 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 LCP: 5.7 s

    5.7 s

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

  • Real-user FCP: 3.1 s

    3.1 s

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

  • Largest Contentful Paint: 43.7 s

    43.7 s

    Your largest element takes 43.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Global Shopping Season”.

  • Speed Index: 15.7 s

    15.7 s

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

  • Time to Interactive: 44.2 s

    44.2 s

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

  • Total Blocking Time: 1.5 s

    1.5 s

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

  • First Contentful Paint: 3.9 s

    3.9 s

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

  • Real-user INP: 211 ms

    211 ms

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

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

    +23%

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

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

    +48%

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

  • 1 image without width and height

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

3 checks passed
  • 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 TTFB: 496 ms

    496 ms

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

  • Cumulative Layout Shift: 0.016

    0.016

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

Images and page weight

5 to fix18
  • Page weight: 18.7 MB in 105 requests

    18.7 MB

    Your homepage downloads 18.7 MB in 105 requests on a phone: images 11.8 MB (18), scripts 3.3 MB (35) and fonts 2.9 MB (11). Under 2 MB keeps phones on slow connections fast.

  • 4 images over 500 KB

    4 images weigh 11.0 MB together. On a phone connection a single image that size takes seconds.

  • 6 images far larger than shown

    11.0 MB

    6 images are downloaded at several times the size a phone draws them, for example 3840x2400-1_2.png at 3,840 px wide, shown at 315 px. Resized copies would save about 11.0 MB.

  • 7 images in older formats

    7 images (11.8 MB) 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.

  • 3 images below the first screen load straight away

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

  • About 5.3 g of CO₂ per visit

    5.29 g

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

Accessibility

14 to fixGoogle 6682
  • Images must have alternative text (4 elements)

    Images must have alternative text: 4 elements on the page fail this check, rated critical by axe-core.

  • 3 buttons without a name

    3 buttons have no accessible name, so screen readers announce just “button”.

  • 36 text elements with low contrast

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

  • Orphan list items

    Some list items are not inside a list.

  • Hidden but focusable

    9 elements hidden from screen readers can still receive keyboard focus.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • ARIA input fields must have an accessible name (1 element)

    ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Zoom is disabled

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

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

  • 10 links without text

    10 visible links have no text or label, so screen readers cannot say where they go.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • 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
  • 43 automated accessibility rules passed

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

SEO

8 to fixGoogle 9261
  • No H1 headline

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

  • Title is short (13 characters)

    Your title is only 13 characters: “CONVERSE BANK”. 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.

  • Meta description is short (25 characters)

    Your meta description is only 25 characters: “Converse Bank new website”. 70 to 160 characters is enough to sell the click.

  • 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://conversebank.am/sitemap.xml, so Google discovers your pages only by following links.

  • 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 X (Twitter) card tag

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

1 checks passed
  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix83
  • 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://conversebank.am/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

2 to fixGoogle 8891
  • 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 ()”.

  • 3 distorted images

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

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    50 of 53 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix33
  • 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 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 122 words

    The homepage has only about 122 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
  • Analytics in place

    Analytics detected: Google Tag Manager 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 Ads, Google Tag Manager, Meta Pixel and Yandex Metrica (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.

  • 16 cookies set on arrival

    16

    Opening the homepage sets 16 cookies, 4 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.

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

Upkeep, stack and company

Stack

Analytics
Google Tag Manager
Hosting
Cloudflare

Company

Founded
1993
Headquarters
Yerevan

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 61 issues on conversebank.am, including 25 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