Report Summary

  • 81

    Performance

    Renders faster than
    87% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

ehouse.by

ehouse.by Выставлен на продажу

Page Load Speed

4.4 sec in total

First Response

514 ms

Resources Loaded

3.6 sec

Page Rendered

200 ms

ehouse.by screenshot

About Website

Click here to check amazing Ehouse content. Otherwise, check out these important facts you probably never knew about ehouse.by

Hostfly

Visit ehouse.by

Key Findings

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

Performance Metrics

ehouse.by performance score

81

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

83/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

62/100

25%

SI (Speed Index)

Value2.9 s

95/100

10%

TBT (Total Blocking Time)

Value250 ms

84/100

30%

CLS (Cumulative Layout Shift)

Value0.024

100/100

15%

TTI (Time to Interactive)

Value4.8 s

79/100

10%

Network Requests Diagram

ehouse.by

514 ms

style.css

1202 ms

main.css

388 ms

jquery-1.11.1.min.js

650 ms

script.js

265 ms

Our browser made a total of 13 requests to load all elements on the main page. We found that 69% of them (9 requests) were addressed to the original Ehouse.by, 15% (2 requests) were made to Namehunter.ru and 15% (2 requests) were made to . The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Namehunter.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 424.2 kB (34%)

Content Size

1.3 MB

After Optimization

839.1 kB

In fact, the total size of Ehouse.by main page is 1.3 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. 20% of websites need less resources to load. CSS take 734.4 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 4.6 kB

  • Original 6.0 kB
  • After minification 4.1 kB
  • After compression 1.4 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 1.9 kB, which is 31% 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 4.6 kB or 76% of the original size.

Image Optimization

-1%

Potential reduce by 3.0 kB

  • Original 425.2 kB
  • After minification 422.2 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. Ehouse images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 63.6 kB

  • Original 97.7 kB
  • After minification 97.4 kB
  • After compression 34.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 63.6 kB or 65% of the original size.

CSS Optimization

-48%

Potential reduce by 353.0 kB

  • Original 734.4 kB
  • After minification 669.8 kB
  • After compression 381.4 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. Ehouse.by needs all CSS files to be minified and compressed as it can save up to 353.0 kB or 48% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

7

After Optimization

7

The browser has sent 7 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ehouse. According to our analytics all requests are already optimized.

Accessibility Review

ehouse.by accessibility score

98

Accessibility Issues

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

ehouse.by best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

ehouse.by SEO score

92

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

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 Ehouse.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 Ehouse.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 Ehouse. 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: