tangem.com website review

1 third-party service load with your homepage (Cloudflare), adding 10 KiB and 14 ms of main-thread time.

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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 visitors wait 1.9 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

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

1 image (121 KiB) is 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.

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

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

ARIA attributes must conform to valid values: 2 elements on the page fail this check, rated critical by axe-core.

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

Scrollable region must have keyboard access: 3 elements on the page fail this check, rated serious by axe-core.

All page content should be contained by landmarks: 2 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 on the page fails this check, rated moderate by axe-core.

4 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

Google's crawler is blocked from indexing this page.

The page answers with an error status, so search engines may drop it.

Your meta description is 176 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 89 pages on tangem.com and 48 external pages.

Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://tangem.com/en/cryptocurrencies, whose canonical is https://tangem.com/en/cryptocurrencies/page/1. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://tangem.com/en/academy has no <h1> headline, so visitors and search engines get no clear main topic.

https://tangem.com/en/help-center has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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

The homepage carries about 1,926 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Amplitude, Google Ads, Google Analytics, Google Tag Manager and Meta Pixel and 5 mores (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 31 cookies (measured from a US location before any click).

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