Tools & Wizards About Us
wetrust.io screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

wetrust.io

The Greatest Treasure in History

Page Load Speed

2.4 sec in total

First Response

273 ms

Resources Loaded

1.8 sec

Page Rendered

318 ms

wetrust.io screenshot

About Website

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

Embark on an epic quest to uncover the greatest treasure in history. Play now and enter the Titans!

Visit wetrust.io

Key Findings

We analyzed Wetrust.io page load time and found that the first response time was 273 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

wetrust.io performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

43/100

10%

LCP (Largest Contentful Paint)

Value14.8 s

0/100

25%

SI (Speed Index)

Value3.2 s

92/100

10%

TBT (Total Blocking Time)

Value830 ms

35/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.3 s

49/100

10%

Network Requests Diagram

www.wetrust.io

273 ms

xae3bme.css

490 ms

tlc-logo-876fa6cd3eac9c29e79860bb28b3a8f8.svg

174 ms

banner-tlc.svg

489 ms

email-decode.min.js

329 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 50% of them (13 requests) were addressed to the original Wetrust.io, 27% (7 requests) were made to Res.cloudinary.com and 19% (5 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (812 ms) relates to the external source Res.cloudinary.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 747.0 kB (35%)

Content Size

2.2 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wetrust.io main page is 2.2 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. 35% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 322.0 kB

  • Original 435.6 kB
  • After minification 435.5 kB
  • After compression 113.6 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 322.0 kB or 74% of the original size.

Image Optimization

-25%

Potential reduce by 425.0 kB

  • Original 1.7 MB
  • After minification 1.3 MB

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, Wetrust needs image optimization as it can save up to 425.0 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-3%

Potential reduce by 17 B

  • Original 655 B
  • After minification 655 B
  • After compression 638 B

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.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 5 B

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.

Requests Breakdown

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

Requests Now

21

After Optimization

17

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.wetrust.io

www.wetrust.io

273 ms

xae3bme.css

xae3bme.css

490 ms

tlc-logo-876fa6cd3eac9c29e79860bb28b3a8f8.svg

tlc-logo-876fa6cd3eac9c29e79860bb28b3a8f8.svg

174 ms

banner-tlc.svg

banner-tlc.svg

489 ms

email-decode.min.js

email-decode.min.js

329 ms

webpack-runtime-515f43b21a4d749e9d6c.js

webpack-runtime-515f43b21a4d749e9d6c.js

354 ms

app-f50b947e3439b857d056.js

app-f50b947e3439b857d056.js

569 ms

component---src-pages-index-tsx-b2863e831f3b2bf07d36.js

component---src-pages-index-tsx-b2863e831f3b2bf07d36.js

567 ms

5-eda2ac66c7440542614e.js

5-eda2ac66c7440542614e.js

577 ms

banner-spring.svg

banner-spring.svg

605 ms

banner-staking.svg

banner-staking.svg

636 ms

banner-cu.svg

banner-cu.svg

674 ms

banner-to.svg

banner-to.svg

812 ms

banner-grants.svg

banner-grants.svg

640 ms

banner-identity-logo.svg

banner-identity-logo.svg

687 ms

vision-1-588b526cf2777cdd373da2f283950f0d.png

vision-1-588b526cf2777cdd373da2f283950f0d.png

787 ms

vision-2-e89b8db5bc134f683e4b5f8686c952eb.png

vision-2-e89b8db5bc134f683e4b5f8686c952eb.png

583 ms

vision-3-360c86a42cd4ce6705816899c84db69c.png

vision-3-360c86a42cd4ce6705816899c84db69c.png

787 ms

biweeklyupdates-icon@3x-7b24a973aa80390ff353398fad0b0db0.png

biweeklyupdates-icon@3x-7b24a973aa80390ff353398fad0b0db0.png

772 ms

wetrustnanjingyoutube-icon-4d92205285da3ba2f7963f188aa32e80.svg

wetrustnanjingyoutube-icon-4d92205285da3ba2f7963f188aa32e80.svg

616 ms

mckinseyalum-icon-74049f525e5e804ee310e7dc19bcaee4.svg

mckinseyalum-icon-74049f525e5e804ee310e7dc19bcaee4.svg

673 ms

p.css

p.css

341 ms

d

d

22 ms

d

d

386 ms

d

d

528 ms

d

d

401 ms

Accessibility Review

wetrust.io accessibility score

72

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

button, link, and menuitem elements do not have accessible names.

High

[role] values are not valid

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

wetrust.io SEO score

75

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

    N/A

  • Encoding

    UTF-8

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

wetrust.io

Open Graph data is detected on the main page of Wetrust. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: