Tools & Wizards About Us
hardwallet.status.im screenshot

Report Summary

  • 73

    Performance

    Renders faster than
    82% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

hardwallet.status.im

Keycard - Secure, Contactless, Open Source, Crypto Hardwallet

Page Load Speed

3.2 sec in total

First Response

599 ms

Resources Loaded

1.7 sec

Page Rendered

906 ms

hardwallet.status.im screenshot

About Website

Visit hardwallet.status.im now to see the best up-to-date Hardwallet Status content for India and also check out these interesting facts you probably never knew about hardwallet.status.im

Keycard is a new type of smartcard built with an open API for simple integration with crypto wallets and hardware. Designed to safely send, store, and receive cryptocurrencies in a seamless contactles...

Visit hardwallet.status.im

Key Findings

We analyzed Hardwallet.status.im page load time and found that the first response time was 599 ms and then it took 2.6 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

hardwallet.status.im performance score

73

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value4.5 s

36/100

25%

SI (Speed Index)

Value4.5 s

72/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.5 s

83/100

10%

Network Requests Diagram

keycard.tech

599 ms

application.css

113 ms

css

217 ms

dracula.min.css

452 ms

prism-atom-dark.css

265 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Hardwallet.status.im, 10% (2 requests) were made to Fonts.gstatic.com and 5% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (780 ms) relates to the external source Keycard.tech.

Page Optimization Overview & Recommendations

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

Content Size

809.3 kB

After Optimization

654.9 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Hardwallet.status.im main page is 809.3 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. 50% of websites need less resources to load. Images take 695.5 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 78.0 kB

  • Original 112.8 kB
  • After minification 106.7 kB
  • After compression 34.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. 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 78.0 kB or 69% of the original size.

Image Optimization

-11%

Potential reduce by 76.4 kB

  • Original 695.5 kB
  • After minification 619.1 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, Hardwallet Status needs image optimization as it can save up to 76.4 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 5 B

  • Original 1.0 kB
  • After minification 1.0 kB
  • After compression 1.0 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 3 (18%)

Requests Now

17

After Optimization

14

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

keycard.tech

keycard.tech

599 ms

application.css

application.css

113 ms

css

css

217 ms

dracula.min.css

dracula.min.css

452 ms

prism-atom-dark.css

prism-atom-dark.css

265 ms

adparam.js

adparam.js

272 ms

jquery-3.6.0.min.js

jquery-3.6.0.min.js

254 ms

card-dark.png

card-dark.png

780 ms

card-light.png

card-light.png

306 ms

card-colored.png

card-colored.png

770 ms

integration-status.png

integration-status.png

780 ms

integrate-keycard.png

integrate-keycard.png

770 ms

security-keyvisual.png

security-keyvisual.png

770 ms

branded-cards.png

branded-cards.png

778 ms

status-logo.svg

status-logo.svg

771 ms

keycard-logo.svg

keycard-logo.svg

361 ms

circles-background-dark.jpg

circles-background-dark.jpg

366 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

63 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

56 ms

tracker.js

tracker.js

61 ms

Accessibility Review

hardwallet.status.im accessibility score

79

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

hardwallet.status.im best practices score

92

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

SEO Factors

hardwallet.status.im SEO score

86

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

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 Hardwallet.status.im 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 Hardwallet.status.im 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

hardwallet.status.im

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