hi.com website review

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

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

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

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

YouTube costs a phone 491 ms of main-thread work and 1,011 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.

2 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.

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

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

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

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

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

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

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

Your largest element takes 26.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Easy-to-use Crypto Bank Super-App”.

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

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

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

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

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

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

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

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

Your homepage downloads 6.8 MB in 78 requests on a phone: images 3.2 MB (23), scripts 3.1 MB (32) and fonts 381 KiB (5). Under 2 MB keeps phones on slow connections fast.

content-1.png weighs 756 KiB. On a phone connection a single image that size takes seconds.

6 images (1.5 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.

4 images are downloaded at several times the size a phone draws them, for example content-1.png at 1,440 px wide, shown at 390 px. Resized copies would save about 389 KiB.

2 images further down the page (292 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 1.94 g of CO₂e: 232.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

19 images have no alt text, which hurts accessibility and image search.

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

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

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

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

Your hreflang tags are invalid, so Google may show the wrong language version.

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

The homepage links to 12 pages on hi.com and 17 external pages.

There is no /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.

/protect-yourself has no meta description, so Google writes the search snippet from whatever text it finds.

/products/membership and /support/privacy have no <h1> headline, so visitors and search engines get no clear main topic.

/learn/community, /about/people and /support/privacy have 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 10 pages linked from your homepage and read each the way a search engine does.

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://api3.binance.com/api/v3/ticker/24hr' from origin 'https://hi.com' has been blocked…”.

Chrome logged issues while loading the page (“Cookie”).

Large scripts ship without source maps.

2 links to other sites are dead, for example https://apps.apple.com/us/app/hi-buy-earn-send-crypto/id1583215766 (404).

No Content-Security-Policy header, the main browser-side defence against injected scripts.

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

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

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

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

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

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

The homepage has only about 197 words of visible text; thin pages give Google and first-time buyers little to go on.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

DMARC is set to p=none, so mail pretending to be hi.com is still delivered. Reports are on, so moving to quarantine is the next step.

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.

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

Opening the homepage sets 8 cookies, 1 of them by other companies (measured from a US location before any click).

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.

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