Tools & Wizards About Us
trezor.io screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

trezor.io

Trezor Hardware Wallet (Official) | Bitcoin & Crypto Security

Page Load Speed

1.8 sec in total

First Response

25 ms

Resources Loaded

782 ms

Page Rendered

951 ms

trezor.io screenshot

About Website

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

The safest cold storage wallets for crypto security and financial independence. Easily use, store, and protect Bitcoins.

Visit trezor.io

Key Findings

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

Performance Metrics

trezor.io performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

92/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

43/100

25%

SI (Speed Index)

Value4.9 s

66/100

10%

TBT (Total Blocking Time)

Value2,340 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.9 s

21/100

10%

Network Requests Diagram

trezor.io

25 ms

trezor.io

52 ms

fa4be87f44f6aca2.css

22 ms

e030e8e0ec0db1cd.css

32 ms

fd9d1056-87221ab141ca0102.js

35 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that all of those requests were addressed to Trezor.io and no external sources were called. The less responsive or slowest element that took the longest time to load (583 ms) belongs to the original domain Trezor.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 105.9 kB (13%)

Content Size

818.7 kB

After Optimization

712.8 kB

  • HTML
  • Images

In fact, the total size of Trezor.io main page is 818.7 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. 65% of websites need less resources to load. Images take 686.8 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 105.0 kB

  • Original 131.9 kB
  • After minification 131.9 kB
  • After compression 26.9 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.0 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 901 B

  • Original 686.8 kB
  • After minification 685.9 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. Trezor images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 25 (51%)

Requests Now

49

After Optimization

24

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

trezor.io

trezor.io

25 ms

trezor.io

trezor.io

52 ms

fa4be87f44f6aca2.css

fa4be87f44f6aca2.css

22 ms

e030e8e0ec0db1cd.css

e030e8e0ec0db1cd.css

32 ms

fd9d1056-87221ab141ca0102.js

fd9d1056-87221ab141ca0102.js

35 ms

1608-722f805b970a2a35.js

1608-722f805b970a2a35.js

41 ms

main-app-c67b20bafe8e45db.js

main-app-c67b20bafe8e45db.js

30 ms

2645-cd64a268b02ae9c9.js

2645-cd64a268b02ae9c9.js

30 ms

7701-634493fd8c4279b8.js

7701-634493fd8c4279b8.js

42 ms

7668-8f86aea41f42bc7e.js

7668-8f86aea41f42bc7e.js

41 ms

8056-5402748fe1df26cd.js

8056-5402748fe1df26cd.js

50 ms

6648-bae8f5522e3a46bb.js

6648-bae8f5522e3a46bb.js

49 ms

3580-6a573596114c090f.js

3580-6a573596114c090f.js

51 ms

8882-2c187588a0c28cc2.js

8882-2c187588a0c28cc2.js

50 ms

1852-9bb27ae7c9bab8c9.js

1852-9bb27ae7c9bab8c9.js

50 ms

4903-b8fadd6abdf36e10.js

4903-b8fadd6abdf36e10.js

61 ms

8761-871a5290a186943f.js

8761-871a5290a186943f.js

88 ms

layout-39df3e4b2ff98d3b.js

layout-39df3e4b2ff98d3b.js

61 ms

542ea986-73dd2e53ce3f2415.js

542ea986-73dd2e53ce3f2415.js

77 ms

7907-4b304e8b972afbf6.js

7907-4b304e8b972afbf6.js

59 ms

135-ecb85ca6074aeb42.js

135-ecb85ca6074aeb42.js

67 ms

2520-4d573bd6fca85f0d.js

2520-4d573bd6fca85f0d.js

72 ms

8425-cde49bd195218989.js

8425-cde49bd195218989.js

90 ms

2470-3d1d7b448f1b5700.js

2470-3d1d7b448f1b5700.js

76 ms

page-5f2463734854af75.js

page-5f2463734854af75.js

88 ms

layout-7d996a656b7d8eef.js

layout-7d996a656b7d8eef.js

88 ms

not-found-dae2f2357fe826d3.js

not-found-dae2f2357fe826d3.js

93 ms

global-error-32d357abd8eca954.js

global-error-32d357abd8eca954.js

93 ms

polyfills-78c92fac7aa8fdd8.js

polyfills-78c92fac7aa8fdd8.js

96 ms

webpack-39726948563c9ec7.js

webpack-39726948563c9ec7.js

90 ms

ts5.png

ts5.png

22 ms

ts3.png

ts3.png

21 ms

t-one.png

t-one.png

19 ms

image

image

398 ms

image

image

489 ms

desktop.jpg

desktop.jpg

15 ms

underline.svg

underline.svg

169 ms

ts5.jpg

ts5.jpg

38 ms

image

image

583 ms

hand.jpg

hand.jpg

38 ms

big.png

big.png

170 ms

wallet-backup.svg

wallet-backup.svg

53 ms

open-source.svg

open-source.svg

70 ms

device-protection.svg

device-protection.svg

82 ms

history.jpg

history.jpg

99 ms

hand.4af4efa9.svg

hand.4af4efa9.svg

117 ms

trezor-safe5.5ae51826.svg

trezor-safe5.5ae51826.svg

166 ms

btc.546c5dc7.svg

btc.546c5dc7.svg

169 ms

eth.9dd99ade.svg

eth.9dd99ade.svg

172 ms

shield.a9a67058.svg

shield.a9a67058.svg

173 ms

trezor-safe3.c524f428.svg

trezor-safe3.c524f428.svg

175 ms

Accessibility Review

trezor.io accessibility score

84

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

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

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

trezor.io SEO score

100

Search Engine Optimization Advices

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

trezor.io

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