Tools & Wizards About Us

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

uniris.io

Uniris - Be the only key to the next evolution of Internet

Page Load Speed

3.5 sec in total

First Response

560 ms

Resources Loaded

2.2 sec

Page Rendered

725 ms

About Website

Visit uniris.io now to see the best up-to-date Uniris content and also check out these interesting facts you probably never knew about uniris.io

To offer the Blockchain's proven trust for everyone, everywhere and everything in the world, through a limitless and Earth-friendly solution

Visit uniris.io

Key Findings

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

Performance Metrics

uniris.io performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value11.3 s

0/100

25%

SI (Speed Index)

Value6.6 s

37/100

10%

TBT (Total Blocking Time)

Value750 ms

39/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value13.4 s

11/100

10%

Network Requests Diagram

www.archethic.net

560 ms

css@3

29 ms

404.026c9327.css

197 ms

404.79b96e38.css

332 ms

404.5062a7f7.css

378 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Uniris.io, 8% (4 requests) were made to Unpkg.com and 6% (3 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 Archethic.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 56.7 kB (69%)

Content Size

81.9 kB

After Optimization

25.2 kB

  • HTML
  • JavaScript

In fact, the total size of Uniris.io main page is 81.9 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. 45% of websites need less resources to load. HTML takes 72.1 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 56.6 kB

  • Original 72.1 kB
  • After minification 54.6 kB
  • After compression 15.4 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 17.5 kB, which is 24% 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 56.6 kB or 79% of the original size.

JavaScript Optimization

-1%

Potential reduce by 52 B

  • Original 9.8 kB
  • After minification 9.8 kB
  • After compression 9.8 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 12 (33%)

Requests Now

36

After Optimization

24

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

uniris.io accessibility score

73

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

Form elements do not have associated labels

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

uniris.io best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

uniris.io SEO score

92

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

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Uniris.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 Uniris.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

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