kucoin.com website review

staticimg.com costs a phone 1.7 s of main-thread work and 3.9 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

7 third-party services load with your homepage (staticimg.com, Optanon and Facebook and others), adding 4.4 MB and 2.0 s of main-thread time.

15 images could be 1.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

About 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 310 ms faster on a phone.

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

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

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

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

Polyfills for old browsers add 68 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.

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

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

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

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

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

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.

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

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

Your homepage downloads 4.8 MB in 210 requests on a phone: images 2.1 MB (44), scripts 2.0 MB (71) and other files 370 KiB (88). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example bg.f27499180cb26dd7.png at 2,208 px wide, shown at 320 px. Resized copies would save about 189 KiB.

1 image (233 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.

1 image further down the page (233 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

<dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements: 8 elements on the page fail this check, rated serious by axe-core.

3 tap targets are too small or too close together to hit reliably with a finger.

1 element hidden from screen readers can still receive keyboard focus.

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

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

Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

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

Elements with visible text labels do not have matching accessible names. (7 elements).

2 links have no real href, so search engines can't follow them.

The homepage links to 73 pages on kucoin.com and 9 external pages.

/ and https://www.kucoin.com/rewardshub all use the title “Crypto Exchange | Bitcoin Exchange | Bitcoin Trading | KuCoin”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.kucoin.com/rewardshub and https://www.kucoin.com/markets/rankings have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

6 errors were logged to the browser console while the page loaded, for example “Executing inline script violates the following Content Security Policy directive 'default-src 'unsafe-eval' 'nonce-n0zI…”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

Chrome logged issues while loading the page (“Content security policy”).

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.

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.

The homepage carries about 317 words of visible text.

Before a visitor clicks anything, the page loads Meta Pixel and Yandex Metrica (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

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

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