Tools & Wizards About Us
xinfin.io screenshot

Report Summary

  • 68

    Performance

    Renders faster than
    80% of other websites

  • 43

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

xinfin.io

Decentralized Smart Contracts Platform

Page Load Speed

2.5 sec in total

First Response

50 ms

Resources Loaded

1.9 sec

Page Rendered

537 ms

xinfin.io screenshot

About Website

Visit xinfin.io now to see the best up-to-date Xinfin content for United States and also check out these interesting facts you probably never knew about xinfin.io

The Decentralized and Open Source Smart Contract Platform, Driven by Community for Seamless Execution of Enterprise-Friendly Use Cases such as Trade Finance and Payment.

Visit xinfin.io

Key Findings

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

Performance Metrics

xinfin.io performance score

68

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

33/100

25%

SI (Speed Index)

Value4.0 s

80/100

10%

TBT (Total Blocking Time)

Value170 ms

93/100

30%

CLS (Cumulative Layout Shift)

Value0.02

100/100

15%

TTI (Time to Interactive)

Value6.0 s

64/100

10%

Network Requests Diagram

xinfin.io

50 ms

www.xinfin.org

358 ms

js

68 ms

bootstrap.css

46 ms

metismenu.css

65 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Xinfin.io, 71% (54 requests) were made to Xinfin.org and 13% (10 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Xinfin.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 157.5 kB (22%)

Content Size

704.8 kB

After Optimization

547.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Xinfin.io main page is 704.8 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. 80% 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 534.2 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 39.2 kB

  • Original 46.9 kB
  • After minification 46.8 kB
  • After compression 7.7 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 39.2 kB or 84% of the original size.

Image Optimization

-18%

Potential reduce by 95.1 kB

  • Original 534.2 kB
  • After minification 439.0 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, Xinfin needs image optimization as it can save up to 95.1 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-14%

Potential reduce by 12.3 kB

  • Original 86.4 kB
  • After minification 86.4 kB
  • After compression 74.2 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 12.3 kB or 14% of the original size.

CSS Optimization

-29%

Potential reduce by 10.9 kB

  • Original 37.3 kB
  • After minification 26.4 kB
  • After compression 26.4 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. Xinfin.io needs all CSS files to be minified and compressed as it can save up to 10.9 kB or 29% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (27%)

Requests Now

56

After Optimization

41

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

xinfin.io

xinfin.io

50 ms

www.xinfin.org

www.xinfin.org

358 ms

js

js

68 ms

bootstrap.css

bootstrap.css

46 ms

metismenu.css

metismenu.css

65 ms

custom.css

custom.css

82 ms

all.min.css

all.min.css

39 ms

all.min.css

all.min.css

58 ms

jquery-1.12.4.min.js

jquery-1.12.4.min.js

80 ms

popper.min.js

popper.min.js

79 ms

bootstrap.js

bootstrap.js

79 ms

jquery.counterup.min.js

jquery.counterup.min.js

78 ms

jquery.waypoints.min.js

jquery.waypoints.min.js

80 ms

metismenu.js

metismenu.js

83 ms

progresscircle.js

progresscircle.js

82 ms

custom.js

custom.js

89 ms

js.cookie.js

js.cookie.js

89 ms

jquery.style.switcher.js

jquery.style.switcher.js

89 ms

css2

css2

37 ms

xdc-network-logo-white.svg

xdc-network-logo-white.svg

241 ms

api-light.png

api-light.png

236 ms

api.png

api.png

212 ms

iso-light.png

iso-light.png

227 ms

iso.png

iso.png

230 ms

smc-light.png

smc-light.png

258 ms

smc.png

smc.png

260 ms

copper-logoL.png

copper-logoL.png

227 ms

copper-logoD.png

copper-logoD.png

418 ms

r3-logoL.png

r3-logoL.png

424 ms

r3-logoD.png

r3-logoD.png

429 ms

sotatek-logoL.png

sotatek-logoL.png

417 ms

sotatek-logoD.png

sotatek-logoD.png

433 ms

adgm-logoL.png

adgm-logoL.png

424 ms

adgm-logoD.png

adgm-logoD.png

615 ms

circle-logoL.png

circle-logoL.png

623 ms

circle-logoD.png

circle-logoD.png

620 ms

big-logoL.png

big-logoL.png

622 ms

big-logoD.png

big-logoD.png

621 ms

ramco-logoL.png

ramco-logoL.png

637 ms

ramco-logoD.png

ramco-logoD.png

811 ms

indsoft-logoL.png

indsoft-logoL.png

829 ms

indsoft-logoD.png

indsoft-logoD.png

817 ms

assocham-logoL.png

assocham-logoL.png

828 ms

assocham-logoD.png

assocham-logoD.png

829 ms

nanyang-logoL.png

nanyang-logoL.png

836 ms

nanyang-logoD.png

nanyang-logoD.png

1004 ms

aix-logoL.png

aix-logoL.png

1007 ms

aix-logoD.png

aix-logoD.png

1031 ms

integrations-all.png

integrations-all.png

1023 ms

integrations-all_dark.png

integrations-all_dark.png

1030 ms

networkImage.png

networkImage.png

1046 ms

transactions.png

transactions.png

1199 ms

contracts.png

contracts.png

1201 ms

validators-nodes.png

validators-nodes.png

1230 ms

walletsImage.png

walletsImage.png

1232 ms

xdc-network-logo.svg

xdc-network-logo.svg

18 ms

bg-curved.png

bg-curved.png

198 ms

integrations-left.png

integrations-left.png

294 ms

integrations-right.png

integrations-right.png

315 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuGKYMZhrib2Au-0.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuGKYMZhrib2Au-0.ttf

110 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuFuYMZhrib2Au-0.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuFuYMZhrib2Au-0.ttf

156 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuDyYMZhrib2Au-0.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuDyYMZhrib2Au-0.ttf

258 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuBWYMZhrib2Au-0.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuBWYMZhrib2Au-0.ttf

258 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuI6fMZhrib2Au-0.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuI6fMZhrib2Au-0.ttf

223 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyfMZhrib2Au-0.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyfMZhrib2Au-0.ttf

255 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuOKfMZhrib2Au-0.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuOKfMZhrib2Au-0.ttf

256 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuDyfMZhrib2Au-0.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuDyfMZhrib2Au-0.ttf

196 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyeMZhrib2Au-0.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyeMZhrib2Au-0.ttf

292 ms

fa-brands-400.ttf

fa-brands-400.ttf

27 ms

fa-brands-400.ttf

fa-brands-400.ttf

41 ms

fa-solid-900.ttf

fa-solid-900.ttf

42 ms

fa-solid-900.ttf

fa-solid-900.ttf

106 ms

fa-regular-400.ttf

fa-regular-400.ttf

39 ms

fa-regular-400.ttf

fa-regular-400.ttf

41 ms

fa-v4compatibility.ttf

fa-v4compatibility.ttf

105 ms

fa-v4compatibility.ttf

fa-v4compatibility.ttf

107 ms

Accessibility Review

xinfin.io accessibility score

43

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

xinfin.io SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Xinfin.io can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Xinfin.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

xinfin.io

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