Report Summary

  • 94

    Performance

    Renders faster than
    93% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 58

    SEO

    Google-friendlier than
    20% of websites

hx.by

hx.by

Page Load Speed

5.1 sec in total

First Response

704 ms

Resources Loaded

4.2 sec

Page Rendered

218 ms

hx.by screenshot

About Website

Welcome to hx.by homepage info - get ready to check Hx best content for Belarus right away, or after learning these important things about hx.by

Visit hx.by

Key Findings

We analyzed Hx.by page load time and found that the first response time was 704 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

hx.by performance score

94

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

86/100

10%

LCP (Largest Contentful Paint)

Value2.8 s

82/100

25%

SI (Speed Index)

Value2.4 s

98/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.8 s

97/100

10%

Network Requests Diagram

hx.by

704 ms

my.css

747 ms

base.css

467 ms

layer7.css

622 ms

jquery-1.7.2.js

940 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 9% of them (4 requests) were addressed to the original Hx.by, 17% (8 requests) were made to S44.ucoz.net and 15% (7 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Catalog.tut.by.

Page Optimization Overview & Recommendations

Page size can be reduced by 385.6 kB (62%)

Content Size

622.0 kB

After Optimization

236.3 kB

In fact, the total size of Hx.by main page is 622.0 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. Javascripts take 457.5 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 74.1 kB

  • Original 86.3 kB
  • After minification 84.9 kB
  • After compression 12.2 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 74.1 kB or 86% of the original size.

Image Optimization

-14%

Potential reduce by 3.5 kB

  • Original 24.6 kB
  • After minification 21.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, Hx needs image optimization as it can save up to 3.5 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-58%

Potential reduce by 265.4 kB

  • Original 457.5 kB
  • After minification 457.3 kB
  • After compression 192.1 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 265.4 kB or 58% of the original size.

CSS Optimization

-80%

Potential reduce by 42.6 kB

  • Original 53.6 kB
  • After minification 45.8 kB
  • After compression 11.0 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. Hx.by needs all CSS files to be minified and compressed as it can save up to 42.6 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (63%)

Requests Now

41

After Optimization

15

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

Accessibility Review

hx.by accessibility score

100

Accessibility Issues

Best Practices

hx.by 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

SEO Factors

hx.by SEO score

58

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hx.by can be misinterpreted by Google and other search engines. Our service has detected that Russian 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 Hx.by 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 Hx. 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: