Website review, no card needed
coinex.com website review
Visit site (opens in a new tab)Reviewed 4 November 202626 issues · 72 checks
This review found 26 issues worth fixing on coinex.com, 5 of them high impact, across 72 checks. The most urgent: fails Core Web Vitals for real visitors. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
79CClosest competitors among SaaS websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 5.4 s |
| May 23, 2026 | 5.7 s |
| May 30, 2026 | 6.2 s |
| Jun 6, 2026 | 6.7 s |
| Jun 13, 2026 | 7.0 s |
| Jun 20, 2026 | 7.1 s |
| Jun 27, 2026 | 7.0 s |
| Jul 4, 2026 | 6.8 s |
| Jul 11, 2026 | 6.7 s |
| Jul 18, 2026 | 6.4 s |
| Jul 25, 2026 | 5.8 s |
| Aug 1, 2026 | 5.3 s |
| Aug 8, 2026 | 5.2 s |
| Aug 15, 2026 | 5.1 s |
| Aug 22, 2026 | 5.1 s |
| Aug 29, 2026 | 5.0 s |
| Sep 5, 2026 | 4.9 s |
| Sep 12, 2026 | 5.0 s |
| Sep 19, 2026 | 5.1 s |
| Sep 26, 2026 | 5.2 s |
| Oct 3, 2026 | 5.3 s |
| Oct 10, 2026 | 5.3 s |
| Oct 17, 2026 | 5.4 s |
| Oct 24, 2026 | 5.2 s |
| Oct 31, 2026 | 5.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 194 ms |
| May 23, 2026 | 189 ms |
| May 30, 2026 | 181 ms |
| Jun 6, 2026 | 180 ms |
| Jun 13, 2026 | 180 ms |
| Jun 20, 2026 | 187 ms |
| Jun 27, 2026 | 179 ms |
| Jul 4, 2026 | 175 ms |
| Jul 11, 2026 | 169 ms |
| Jul 18, 2026 | 161 ms |
| Jul 25, 2026 | 160 ms |
| Aug 1, 2026 | 157 ms |
| Aug 8, 2026 | 159 ms |
| Aug 15, 2026 | 160 ms |
| Aug 22, 2026 | 162 ms |
| Aug 29, 2026 | 161 ms |
| Sep 5, 2026 | 158 ms |
| Sep 12, 2026 | 155 ms |
| Sep 19, 2026 | 143 ms |
| Sep 26, 2026 | 143 ms |
| Oct 3, 2026 | 144 ms |
| Oct 10, 2026 | 143 ms |
| Oct 17, 2026 | 150 ms |
| Oct 24, 2026 | 148 ms |
| Oct 31, 2026 | 148 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
Speed
Mobile performance score: 89
89/100Your mobile performance score is 89. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
550 ms9 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.
Reduce unused JavaScript
530 KiBAbout 530 KiB of JavaScript is downloaded but never used on this page.
ZenDesk adds 225 ms
225 msZenDesk costs a phone 225 ms of main-thread work and 389 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.
1 third-party service on the page
1 third-party service load with your homepage (ZenDesk), adding 389 KiB and 225 ms of main-thread time.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 168 ms. During a long task the page ignores taps.
Reduce unused CSS
76 KiBAbout 76 KiB of CSS is downloaded but never applied on this page.
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.
2 checks passed
Main-thread work: 1.8 s
A phone's processor spends 1.8 s on main-thread work while loading, 937 ms of it running JavaScript. That is comfortably low.
Server response: 12 ms
12 msYour server sent the HTML in 12 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.1 s
5.1 sReal visitors wait 5.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.7 s
4.7 sReal visitors see the first content after 4.7 s (75th percentile). Good is under 1.8 s.
Time to Interactive: 9.3 s
9.3 sThe page becomes fully interactive after 9.3 s. Good is under 3.8 s.
Real-user CLS: 0.12
0.12For real visitors the layout shifts by 0.12 (75th percentile). Good is under 0.1.
Real-user TTFB: 1.7 s
1.7 sReal visitors wait 1.7 s for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 5.3 s
5.3 sVisually, the page fills in at 5.3 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 308 ms
308 msScripts block taps and scrolling for 308 ms in total while the page loads. Good is under 200 ms.
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 5.4 s to 5.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user INP: 184 ms
184 msReal visitors wait 184 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 23% faster for real visitors
-23%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 194 ms to 148 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.3 s
1.3 sThe first text or image appears after 1.3 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Largest Contentful Paint: 1.3 s
1.3 sYour largest element renders in 1.3 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Due to regulatory requirements from relevant authorities re…”.
Images and page weight
About 0.5 g of CO₂ per visit
0.48 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.48 g of CO₂e: 57.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Page weight: 1.7 MB in 91 requests
1.7 MBYour homepage downloads 1.7 MB in 91 requests on a phone: scripts 1.0 MB (29), other files 332 KiB (40) and fonts 190 KiB (5). That is a lean page.
Accessibility
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
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.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links look like plain text
2 links inside paragraphs rely on colour alone to stand out.
Headings skip levels
Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 13 images in the HTML carry an alt attribute.
10 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 12 WCAG 2.2 A/AA and best-practice rules on the phone render: 10 passed and 2 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (96 characters)
Your title is 96 characters, so Google will cut it off around 60: “CoinEx Website - Cryptocurrency Exchange | Buy and Sell Bitcoin (BTC), Ethereum (ETH) & A…”.
Meta description is long (239 characters)
Your meta description is 239 characters; Google truncates after about 160, so the end of your pitch is cut.
46 internal links, 2 external
The homepage links to 46 pages on coinex.com and 2 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Your Crypto Trading Expert”.
Canonical URL set
The canonical URL is https://www.coinex.com/en.
Structured data in place
Structured data found: Organization 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.coinex.com/sitemap.xml.
AI search readiness
Opted out of AI training for 1 crawler
robots.txt blocks CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.
3 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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
llms.txt published
The site publishes https://www.coinex.com/llms.txt (5 KiB, 47 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
https://www.coinex.com/en and / all use the title “CoinEx Website - Cryptocurrency Exchange | Buy and Sell Bitcoin (BTC)…”. Search engines can't tell which page to show for a search, so each competes with the others.
15 links to non-canonical URLs
Your homepage links to 15 pages by a URL that isn't their canonical one, for example /, whose canonical is https://www.coinex.com/en. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
8 pages without an H1
https://www.coinex.com/novice, https://www.coinex.com/markets/coin, https://www.coinex.com/aboutus/contact, https://www.coinex.com/service, https://www.coinex.com/privacy and https://www.coinex.com/disclaimer and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages with very little text
https://www.coinex.com/markets/coin, https://www.coinex.com/price/eth and https://www.coinex.com/price/sol 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.
5 pages slow to respond
/, https://www.coinex.com/novice, https://www.coinex.com/markets/coin, https://www.coinex.com/insight and https://www.coinex.com/price/sol took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 41 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has a meta description
All 15 pages that loaded have a meta description.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Executing inline event handler violates the following Content Security Policy directive 'script-src www.google-analytic…”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Thin social proof
Social proof on the homepage: “trusted by 10M+ users”. Pairing it with named testimonials or customer logos makes it far more convincing.
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 184 words
The homepage has only about 184 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.
2 checks passed
16 calls to action
The homepage has 16 calls to action, for example “Sign Up”, “Contact Us” and “Join Us”.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie (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.
2 other companies contacted
Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 coinex.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Nuxt
- Analytics
- Google Analytics
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 26 issues on coinex.com, including 12 speed issues, 2 SEO issues and 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.