Tools & Wizards About Us
nami.exchange screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    43% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

nami.exchange

Buy/Sell Bitcoin, Ether and Altcoin | Safety Spot and Future Exchange | Nami Exchange

Page Load Speed

5.5 sec in total

First Response

328 ms

Resources Loaded

4.3 sec

Page Rendered

881 ms

nami.exchange screenshot

About Website

Visit nami.exchange now to see the best up-to-date Nami content for Vietnam and also check out these interesting facts you probably never knew about nami.exchange

Nami Cryptocurrency Exchange - The oldest exchange, with the largest bitcoin and altcoin trading volume in Vietnam

Visit nami.exchange

Key Findings

We analyzed Nami.exchange page load time and found that the first response time was 328 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

nami.exchange performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

10/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

27/100

25%

SI (Speed Index)

Value27.7 s

0/100

10%

TBT (Total Blocking Time)

Value63,370 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value82.5 s

0/100

10%

Network Requests Diagram

nami.exchange

328 ms

coolicons.css

298 ms

tv.js

316 ms

polyfills.js

268 ms

bundle.js

296 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 40% of them (34 requests) were addressed to the original Nami.exchange, 39% (33 requests) were made to Sgp1.digitaloceanspaces.com and 8% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.2 sec) relates to the external source Sgp1.digitaloceanspaces.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 154.6 kB (17%)

Content Size

902.6 kB

After Optimization

748.0 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Nami.exchange main page is 902.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 761.4 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 105.1 kB

  • Original 124.4 kB
  • After minification 123.8 kB
  • After compression 19.3 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 105.1 kB or 84% of the original size.

Image Optimization

-6%

Potential reduce by 49.2 kB

  • Original 761.4 kB
  • After minification 712.1 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Nami images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 252 B

  • Original 16.8 kB
  • After minification 16.8 kB
  • After compression 16.6 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 36 (47%)

Requests Now

76

After Optimization

40

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nami. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

nami.exchange

nami.exchange

328 ms

coolicons.css

coolicons.css

298 ms

tv.js

tv.js

316 ms

polyfills.js

polyfills.js

268 ms

bundle.js

bundle.js

296 ms

js

js

67 ms

1632df46e64a3b20.css

1632df46e64a3b20.css

43 ms

2a64b85d9f57fa54.css

2a64b85d9f57fa54.css

43 ms

polyfills-5cd94c89d3acac5f.js

polyfills-5cd94c89d3acac5f.js

64 ms

webpack-5ffbb8b14971e269.js

webpack-5ffbb8b14971e269.js

66 ms

framework-eeba1b405d308ec4.js

framework-eeba1b405d308ec4.js

95 ms

main-4226ca2477dce519.js

main-4226ca2477dce519.js

73 ms

_app-58654c1d1b3853a1.js

_app-58654c1d1b3853a1.js

109 ms

7206-38ca698efd152592.js

7206-38ca698efd152592.js

110 ms

7729-60fbcec44381bc51.js

7729-60fbcec44381bc51.js

121 ms

3925-4ba5ce645d03111a.js

3925-4ba5ce645d03111a.js

144 ms

5239-b3350f6992f2611f.js

5239-b3350f6992f2611f.js

146 ms

516-25783dc13b8a0036.js

516-25783dc13b8a0036.js

145 ms

6293-d46c9c785b6abac3.js

6293-d46c9c785b6abac3.js

146 ms

7333-12fe6cef030b1f15.js

7333-12fe6cef030b1f15.js

147 ms

5675-18f9d10081170f6e.js

5675-18f9d10081170f6e.js

154 ms

5536-51102cb36f2ca9ab.js

5536-51102cb36f2ca9ab.js

159 ms

5718-a1b057f99dc5208a.js

5718-a1b057f99dc5208a.js

161 ms

6158-a7fd759467af023f.js

6158-a7fd759467af023f.js

835 ms

6858-949a4b023aecaef8.js

6858-949a4b023aecaef8.js

181 ms

7818-836f46c30dbfeb57.js

7818-836f46c30dbfeb57.js

183 ms

9917-bd103f51b160ebce.js

9917-bd103f51b160ebce.js

197 ms

6662-d94b5f4900f36cfe.js

6662-d94b5f4900f36cfe.js

206 ms

4230-4c7474c3fe71df9c.js

4230-4c7474c3fe71df9c.js

837 ms

5162-b33c1620f36663a8.js

5162-b33c1620f36663a8.js

264 ms

6480-08684af6ac73b996.js

6480-08684af6ac73b996.js

835 ms

index-aec2904a8737412d.js

index-aec2904a8737412d.js

291 ms

_buildManifest.js

_buildManifest.js

847 ms

_ssgManifest.js

_ssgManifest.js

744 ms

_middlewareManifest.js

_middlewareManifest.js

743 ms

gtm.js

gtm.js

434 ms

fbevents.js

fbevents.js

545 ms

css2

css2

595 ms

ic_us_flag.png

ic_us_flag.png

2220 ms

download_app_store.png

download_app_store.png

1921 ms

download_play_store.png

download_play_store.png

1958 ms

nami_maldives.png

nami_maldives.png

1922 ms

ic_qr.png

ic_qr.png

1923 ms

banner_graphics.png

banner_graphics.png

2740 ms

ic_facebook.png

ic_facebook.png

1940 ms

ic_twitter.png

ic_twitter.png

1923 ms

ic_telegram.png

ic_telegram.png

1965 ms

maxium_performance.png

maxium_performance.png

1968 ms

master_revenue.png

master_revenue.png

2060 ms

token_saving_cost.png

token_saving_cost.png

2283 ms

crypto_knowledge.png

crypto_knowledge.png

2191 ms

journey_graphics2.png

journey_graphics2.png

2663 ms

app_store_light.png

app_store_light.png

2206 ms

play_store_light.png

play_store_light.png

2290 ms

qr_light.png

qr_light.png

2427 ms

mobile_dual_ip_dark.png

mobile_dual_ip_dark.png

2446 ms

dual_ip_dark.png

dual_ip_dark.png

2525 ms

registered_people.png

registered_people.png

2517 ms

investment_diversity.png

investment_diversity.png

2660 ms

fee_saving.png

fee_saving.png

2918 ms

effective_support.png

effective_support.png

2748 ms

ic_reddit.png

ic_reddit.png

2759 ms

ic_globe.png

ic_globe.png

2893 ms

ic_coingecko.png

ic_coingecko.png

2896 ms

nami-logo.png

nami-logo.png

2990 ms

ic_footer_fb.png

ic_footer_fb.png

2974 ms

ic_footer_telegram.png

ic_footer_telegram.png

2985 ms

ic_footer_twitter.png

ic_footer_twitter.png

3126 ms

ic_footer_reddit.png

ic_footer_reddit.png

3136 ms

ic_footer_globe.png

ic_footer_globe.png

3157 ms

ic_footer_coingecko.png

ic_footer_coingecko.png

3185 ms

conversion_async.js

conversion_async.js

563 ms

152788662016500

152788662016500

426 ms

7cHqv4kjgoGqM7E3_-gc4w.woff

7cHqv4kjgoGqM7E3_-gc4w.woff

235 ms

7cHpv4kjgoGqM7EPCA.woff

7cHpv4kjgoGqM7EPCA.woff

538 ms

7cHqv4kjgoGqM7E3p-kc4w.woff

7cHqv4kjgoGqM7E3p-kc4w.woff

811 ms

7cHqv4kjgoGqM7E3w-oc4w.woff

7cHqv4kjgoGqM7E3w-oc4w.woff

911 ms

7cHrv4kjgoGqM7E3b8s_.woff

7cHrv4kjgoGqM7E3b8s_.woff

911 ms

7cHqv4kjgoGqM7E30-8c4w.woff

7cHqv4kjgoGqM7E30-8c4w.woff

912 ms

7cHqv4kjgoGqM7E3t-4c4w.woff

7cHqv4kjgoGqM7E3t-4c4w.woff

912 ms

1183 ms

155 ms

1010 ms

41 ms

Accessibility Review

nami.exchange accessibility score

79

Accessibility Issues

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best Practices

nami.exchange best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

nami.exchange SEO score

77

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nami.exchange can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Nami.exchange main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

nami.exchange

Open Graph description is not detected on the main page of Nami. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: