Website review, no card needed

utrust.com logo

utrust.com website review

Visit site (opens in a new tab)Reviewed 6 November 202630 issues · 97 checks

This review found 30 issues worth fixing on utrust.com, 7 of them high impact, across 97 checks. The most urgent: 1 linked page is broken. 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
1.9 s995 msMay 16Oct 311.8 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.3 s
May 23, 20261.3 s
May 30, 20261.5 s
Jun 6, 20261.6 s
Jun 13, 20261.6 s
Jun 20, 20261.6 s
Jun 27, 20261.5 s
Jul 4, 20261.2 s
Jul 11, 20261.1 s
Jul 18, 20261.1 s
Jul 25, 20261.1 s
Aug 1, 20261.3 s
Aug 8, 20261.4 s
Aug 15, 20261.4 s
Aug 22, 20261.4 s
Aug 29, 20261.7 s
Sep 5, 20261.7 s
Sep 12, 20261.7 s
Sep 19, 20261.7 s
Sep 26, 20261.7 s
Oct 3, 20261.8 s
Oct 10, 20261.8 s
Oct 17, 20261.8 s
Oct 24, 20261.8 s
Oct 31, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
136 ms76 msMay 16Oct 31129 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202692 ms
May 23, 202691 ms
May 30, 2026101 ms
Jun 6, 2026106 ms
Jun 13, 2026106 ms
Jun 20, 2026107 ms
Jun 27, 2026100 ms
Jul 4, 202685 ms
Jul 11, 202684 ms
Jul 18, 202684 ms
Jul 25, 202683 ms
Aug 1, 202691 ms
Aug 8, 202697 ms
Aug 15, 2026102 ms
Aug 22, 2026101 ms
Aug 29, 2026111 ms
Sep 5, 2026115 ms
Sep 12, 2026114 ms
Sep 19, 2026117 ms
Sep 26, 2026117 ms
Oct 3, 2026116 ms
Oct 10, 2026124 ms
Oct 17, 2026127 ms
Oct 24, 2026129 ms
Oct 31, 2026129 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 utrust.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

utrust.com does not allow embedding, so this is Google's rendering of the page.

Speed

7 to fix62
  • Improve image delivery

    900 ms · 214 KiB

    8 images could be 214 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, website-files.com and Clarity and others), adding 1.6 MB and 899 ms of main-thread time.

  • Mobile performance score: 62

    62/100

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

  • Reduce unused JavaScript

    300 ms · 458 KiB

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

  • Google Tag Manager adds 639 ms

    639 ms

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

  • Use efficient cache lifetimes

    300 ms · 91 KiB

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

  • website-files.com adds 138 ms

    138 ms

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

  • 8 long tasks on the main thread

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

  • Reduce unused CSS

    150 ms · 11 KiB

    About 11 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.

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

2 checks passed
  • Main-thread work: 1.8 s

    A phone's processor spends 1.8 s on main-thread work while loading, 905 ms 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

8 to fix100
  • Largest Contentful Paint: 5.9 s

    5.9 s

    Your largest element takes 5.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Empower your business in the digital economy with a financi…”.

  • Time to Interactive: 12.3 s

    12.3 s

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

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

    +41%

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

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

    +37%

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

  • Total Blocking Time: 429 ms

    429 ms

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

  • Speed Index: 3.9 s

    3.9 s

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

  • Cumulative Layout Shift: 0.111

    0.111

    The layout shifts by 0.111 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 1 image without width and height

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

7 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: 119 ms

    119 ms

    Real visitors wait 119 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.7 s

    1.7 s

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

  • Real-user TTFB: 733 ms

    733 ms

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

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

Images and page weight

1 to fix90
  • 1 image far larger than shown

    61 KiB

    1 image is downloaded at several times the size a phone draws it, for example 67e2afa7b9054076a529401f_dda1009436fbaf9ebb2de44ee2484260_he at 1,550 px wide, shown at 377 px. Resized copies would save about 61 KiB.

  • 4 images below the first screen load straight away

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

  • About 0.5 g of CO₂ per visit

    0.50 g

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

2 checks passed
  • Page weight: 1.8 MB in 84 requests

    1.8 MB

    Your homepage downloads 1.8 MB in 84 requests on a phone: scripts 1.2 MB (44), images 474 KiB (20) and fonts 75 KiB (4). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

4 to fixGoogle 9393
  • 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.

  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 43 images in the HTML carry an alt attribute.

  • 41 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: 41 passed and 4 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 10093
  • Title is long (78 characters)

    Your title is 78 characters, so Google will cut it off around 60: “xMoney - The financial ecosystem empowering businesses in the digital economy.”.

  • 51 internal links, 23 external

    The homepage links to 51 pages on utrust.com and 23 external pages.

7 checks passed
  • Meta description: 96 characters

    Your meta description is 96 characters: “Accept payments globally, split transactions, manage finances, and issue cards—all in one place.”.

  • One H1 headline

    Your main headline reads: “Empower your business in the digital economy with a financial ecosystem.”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: FinancialProduct, Organization, WebPage 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.xmoney.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: 6 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes /llms.txt (7 KiB, 23 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix70
  • 1 linked page is broken

    Your homepage links to /products/payment-links, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 2 pages without a meta description

    /privacy-policy and /legal/cryptoasset-terms-of-service---cifralfabeto-unipessoal-lda have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

5 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • 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 14 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9671
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187128530&Ver=2&mid=11ca2b61-1cb5-44d7-b1c9-22bc39a8b7f0&bo=1&sid=f0d98b00d98111f1bea217cd6f14d5e2&vid=f0d9aec0d98111f1a923b7f7b146994a&vids=1&msclkid=N&pi=918639831&l.

  • 2 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “debounce is not defined”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Security and trust

2 to fix83
  • 1 broken link to your own pages

    1 link from your homepage to your own site is broken, for example https://www.xmoney.com/products/payment-links (503).

  • 1 broken external link

    1 link to other sites is dead, for example https://status.crypto.xmoney.com/status/main (503).

  • No X-Content-Type-Options

    X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

  • 2 redirects before the homepage

    Opening https://utrust.com goes through 2 redirects before the homepage loads.

  • No Referrer-Policy

    No Referrer-Policy header, so full URLs can leak to the sites you link to.

  • No Permissions-Policy

    No Permissions-Policy header to switch off camera, microphone and location for embedded content.

  • No security.txt

    There is no /.well-known/security.txt telling researchers how to report a security problem to you.

7 checks passed
  • Served over HTTPS

    The homepage is served over HTTPS (xmoney.com).

  • Valid certificate (36 days left)

    The certificate from Google Trust Services · WE1 verifies for utrust.com and is valid for another 36 days.

  • Protected from clickjacking

    X-Frame-Options or a frame-ancestors policy stops other sites framing yours.

  • Content-Security-Policy set

    A Content-Security-Policy is set, the main browser-side defence against injected scripts.

  • HSTS enabled

    Strict-Transport-Security is set, so browsers always use https.

  • http:// redirects to https

    http://utrust.com redirects to the secure version.

  • HTTP/2 and HTTP/3

    The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.

Domain and trust

  • No CAA record

    xmoney.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

  • DNSSEC is off

    xmoney.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

2 checks passed
  • Domain is 24 years old

    24 years

    xmoney.com was registered in Mar 2002 through NameCheap, Inc.. An established domain carries more trust with email providers and search engines.

  • Registered until Mar 2027

    xmoney.com is registered until Mar 2027.

Content and conversion

1 to fix92
  • 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.

  • About 952 words of copy

    The homepage carries about 952 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Start Now” and “Contact Sales”.

  • 13 calls to action

    The homepage has 13 calls to action, for example “Sign up”, “Start Now” and “Contact Sales”.

  • Social proof on the page

    Social proof on the homepage: 17 testimonial or review blocks, 22 customer or partner logos and “Over 5,000+ businesses”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Email authentication

100
  • Email authentication score: 100/100

    Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

3 checks passed
  • DMARC policy: reject

    DMARC tells receivers to reject mail that fails authentication, and sends you reports.

  • SPF with a strict ending (-all)

    An SPF record lists your sending servers and tells receivers to reject anything else: “v=spf1 include:_spf.google.com include:sendgrid.net include:spf.mailigen.com -all”.

  • DKIM signing found

    A DKIM key is published (selector “google”, “s1” and “s2”), so receivers can verify mail really came from you.

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, Microsoft Ads 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.

  • 8 cookies set on arrival

    8

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

  • 17 other companies contacted

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

Upkeep, stack and company

  • The footer still says © 2023.

Stack

CMS
Webflow
Analytics
Google Analytics | Google Tag Manager | Microsoft Clarity
Hosting
Cloudflare

Company

Headquarters
Braga

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on utrust.com, including 15 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