Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 39% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

hebe.cc

Hebe Wallet - The first decentralized multi-chain wallet that supports Ethereum Classic

Page Load Speed

8.5 sec in total

First Response

544 ms

Resources Loaded

7.1 sec

Page Rendered

837 ms

hebe.cc screenshot

About Website

Welcome to hebe.cc homepage info - get ready to check Hebe best content right away, or after learning these important things about hebe.cc

Secure cryptocurrency wallet for Ethereum Classic, Bitcoin, Ethereum, Ripple, Litecoin, Stellar,Nxt,Ardor and over 100+ main chains

Visit hebe.cc

Key Findings

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

Performance Metrics

hebe.cc performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

9/100

25%

SI (Speed Index)

Value8.7 s

16/100

10%

TBT (Total Blocking Time)

Value730 ms

40/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value14.3 s

9/100

10%

Network Requests Diagram

hebe.cc

544 ms

www.hebe.cc

1291 ms

css

33 ms

swiper.min.css

29 ms

animate.min.css

43 ms

Our browser made a total of 161 requests to load all elements on the main page. We found that 83% of them (134 requests) were addressed to the original Hebe.cc, 6% (10 requests) were made to Cdn.jsdelivr.net and 5% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Hebe.cc.

Page Optimization Overview & Recommendations

Page size can be reduced by 121.3 kB (8%)

Content Size

1.5 MB

After Optimization

1.4 MB

In fact, the total size of Hebe.cc main page is 1.5 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. 65% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 67.5 kB

  • Original 76.3 kB
  • After minification 44.5 kB
  • After compression 8.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. This page needs HTML code to be minified as it can gain 31.7 kB, which is 42% 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 67.5 kB or 88% of the original size.

Image Optimization

-0%

Potential reduce by 2.8 kB

  • Original 1.1 MB
  • After minification 1.1 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. Hebe images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 11.8 kB

  • Original 266.1 kB
  • After minification 264.8 kB
  • After compression 254.3 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.

CSS Optimization

-83%

Potential reduce by 39.3 kB

  • Original 47.2 kB
  • After minification 41.4 kB
  • After compression 7.9 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. Hebe.cc needs all CSS files to be minified and compressed as it can save up to 39.3 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

150

After Optimization

125

The browser has sent 150 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hebe. 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 9 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

hebe.cc 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

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

hebe.cc 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

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

hebe.cc SEO score

91

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

High

Tap targets are not sized appropriately

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 Hebe.cc 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 Hebe.cc 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 Hebe. 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: