Tools & Wizards About Us
tradle.io screenshot

Report Summary

  • 54

    Performance

    Renders faster than
    71% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

tradle.io

Tradle. Trust provisioning on blockchain.

Page Load Speed

4.8 sec in total

First Response

10 ms

Resources Loaded

4.4 sec

Page Rendered

386 ms

tradle.io screenshot

About Website

Click here to check amazing Tradle content for United States. Otherwise, check out these important facts you probably never knew about tradle.io

Tradle is the award winning pioneer for KYC on blockchain enabling portability across borders.

Visit tradle.io

Key Findings

We analyzed Tradle.io page load time and found that the first response time was 10 ms and then it took 4.8 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

tradle.io performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

56/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

46/100

25%

SI (Speed Index)

Value5.0 s

64/100

10%

TBT (Total Blocking Time)

Value280 ms

81/100

30%

CLS (Cumulative Layout Shift)

Value0.509

16/100

15%

TTI (Time to Interactive)

Value8.0 s

42/100

10%

Network Requests Diagram

tradle.io

10 ms

tradle.io

353 ms

js

83 ms

jquery.min.js

37 ms

css

50 ms

Our browser made a total of 105 requests to load all elements on the main page. We found that 88% of them (92 requests) were addressed to the original Tradle.io, 3% (3 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Tradle.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 261.6 kB (19%)

Content Size

1.4 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tradle.io main page is 1.4 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 23.7 kB

  • Original 30.5 kB
  • After minification 26.8 kB
  • After compression 6.8 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. This page needs HTML code to be minified as it can gain 3.6 kB, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 23.7 kB or 78% of the original size.

Image Optimization

-17%

Potential reduce by 197.0 kB

  • Original 1.2 MB
  • After minification 959.8 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. Obviously, Tradle needs image optimization as it can save up to 197.0 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-23%

Potential reduce by 40.1 kB

  • Original 176.5 kB
  • After minification 176.4 kB
  • After compression 136.4 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 40.1 kB or 23% of the original size.

CSS Optimization

-15%

Potential reduce by 771 B

  • Original 5.2 kB
  • After minification 5.2 kB
  • After compression 4.5 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Tradle.io needs all CSS files to be minified and compressed as it can save up to 771 B or 15% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (19%)

Requests Now

100

After Optimization

81

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tradle.io

tradle.io

10 ms

tradle.io

tradle.io

353 ms

js

js

83 ms

jquery.min.js

jquery.min.js

37 ms

css

css

50 ms

reset.css

reset.css

336 ms

grid.css

grid.css

356 ms

style.css

style.css

366 ms

cookieconsent.min.css

cookieconsent.min.css

47 ms

prototype.js

prototype.js

363 ms

scriptaculous.js

scriptaculous.js

432 ms

sizzle.js

sizzle.js

360 ms

jquery.easing.js

jquery.easing.js

662 ms

jquery.scrollTo.min.js

jquery.scrollTo.min.js

47 ms

jquery.localscroll.min.js

jquery.localscroll.min.js

687 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

691 ms

waypoints.min.js

waypoints.min.js

713 ms

notifications.js

notifications.js

700 ms

init.js

init.js

707 ms

cookieconsent.min.js

cookieconsent.min.js

55 ms

firebase-app.js

firebase-app.js

45 ms

firebase-analytics.js

firebase-analytics.js

56 ms

analytics.js

analytics.js

78 ms

mobile-nav.png

mobile-nav.png

299 ms

logo.png

logo.png

636 ms

share.png

share.png

650 ms

computer.png

computer.png

673 ms

business.png

business.png

332 ms

law.png

law.png

338 ms

bot-small.png

bot-small.png

662 ms

bot-big.png

bot-big.png

689 ms

more.png

more.png

667 ms

macbook-ipad-black.png

macbook-ipad-black.png

967 ms

static-phone3.png

static-phone3.png

654 ms

android.png

android.png

992 ms

apple.png

apple.png

995 ms

chrome.png

chrome.png

997 ms

safari.png

safari.png

1031 ms

firefox.png

firefox.png

1024 ms

edge.png

edge.png

970 ms

opera.png

opera.png

976 ms

open-source.png

open-source.png

1325 ms

integration.png

integration.png

1314 ms

model.png

model.png

1003 ms

wired.png

wired.png

1334 ms

wall-street-journal.png

wall-street-journal.png

1007 ms

telegraph.png

telegraph.png

1336 ms

ibtimes.png

ibtimes.png

1398 ms

coindesk.png

coindesk.png

1359 ms

finextra.png

finextra.png

1648 ms

fintechconnect.png

fintechconnect.png

1419 ms

nasdaq.png

nasdaq.png

1595 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

23 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

39 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

40 ms

fintech-singapore.png

fintech-singapore.png

1606 ms

collect

collect

24 ms

banker.png

banker.png

1077 ms

blochchain-news.png

blochchain-news.png

1385 ms

NZTech.png

NZTech.png

1093 ms

financial-times.jpg

financial-times.jpg

1092 ms

ltplogo.png

ltplogo.png

1418 ms

logo-nzls.png

logo-nzls.png

1417 ms

JuniperResearch.jpg

JuniperResearch.jpg

1648 ms

pcm.png

pcm.png

1325 ms

BEG.png

BEG.png

1659 ms

ctmfile.png

ctmfile.png

1367 ms

nikkei.png

nikkei.png

1370 ms

mit-horizon.jpeg

mit-horizon.jpeg

1433 ms

citibank.png

citibank.png

1417 ms

mckinsey.png

mckinsey.png

1651 ms

fintechcity.png

fintechcity.png

1655 ms

kpmg.png

kpmg.png

1644 ms

fintecheurope2017.png

fintecheurope2017.png

1058 ms

finsum.png

finsum.png

1387 ms

Clifford-Chance.png

Clifford-Chance.png

1435 ms

fcv.png

fcv.png

1426 ms

celent-ubs.png

celent-ubs.png

1325 ms

pwm-ubs.png

pwm-ubs.png

1661 ms

medici.png

medici.png

1651 ms

finastra.png

finastra.png

1656 ms

FCA.png

FCA.png

1335 ms

LM.png

LM.png

1667 ms

rabobank.jpg

rabobank.jpg

1416 ms

abeam.png

abeam.png

1094 ms

aia.png

aia.png

1421 ms

Clifford-Chance-small.png

Clifford-Chance-small.png

1654 ms

perpetual-guardian.png

perpetual-guardian.png

1632 ms

R3.png

R3.png

1305 ms

Canonical.png

Canonical.png

1600 ms

regula-cropped-logo.png

regula-cropped-logo.png

1626 ms

lacchain.png

lacchain.png

1884 ms

CraigHamer.png

CraigHamer.png

1336 ms

linkedin1.png

linkedin1.png

1110 ms

BobTrojan.png

BobTrojan.png

1431 ms

michael.png

michael.png

1659 ms

jeanstephane.png

jeanstephane.png

1660 ms

genen.png

genen.png

1647 ms

alice.png

alice.png

1288 ms

kirk.png

kirk.png

1617 ms

barnaby.png

barnaby.png

1439 ms

jim.png

jim.png

1631 ms

twitter.png

twitter.png

1656 ms

linkedin.png

linkedin.png

1646 ms

github.png

github.png

1635 ms

Accessibility Review

tradle.io accessibility score

87

Accessibility Issues

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.

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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

tradle.io 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

tradle.io SEO score

85

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

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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 Tradle.io 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 Tradle.io 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

tradle.io

Open Graph description is not detected on the main page of Tradle. 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: