Tools & Wizards About Us
ehouse.ru screenshot

Report Summary

  • 56

    Performance

    Renders faster than
    72% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

ehouse.ru

ADT Web Solutions - разработка, поддержка и сопровождение веб-сайтов; продвижение web сайтов, услуг или товаров в сети интернет; веб-программирование

Page Load Speed

2.1 sec in total

First Response

450 ms

Resources Loaded

1.5 sec

Page Rendered

144 ms

ehouse.ru screenshot

About Website

Welcome to ehouse.ru homepage info - get ready to check Ehouse best content right away, or after learning these important things about ehouse.ru

ADT Web Solutions - один из первых российских Интернет- разработчиков. Основной специализацией компании является разработка, поддержка и сопровождение веб-сайтов, продвижение web сайтов, услуг или тов...

Visit ehouse.ru

Key Findings

We analyzed Ehouse.ru page load time and found that the first response time was 450 ms and then it took 1.6 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

ehouse.ru performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value5.3 s

58/100

10%

TBT (Total Blocking Time)

Value160 ms

93/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.4 s

48/100

10%

Network Requests Diagram

ehouse.ru

450 ms

swfobject.js

96 ms

jquery.ui.all.css

196 ms

adt.css

199 ms

jquery.js

296 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 87% of them (39 requests) were addressed to the original Ehouse.ru, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Mc.yandex.ru. The less responsive or slowest element that took the longest time to load (459 ms) belongs to the original domain Ehouse.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 53.1 kB (10%)

Content Size

517.6 kB

After Optimization

464.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ehouse.ru main page is 517.6 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. 30% of websites need less resources to load. Images take 386.5 kB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 7.3 kB

  • Original 10.8 kB
  • After minification 9.4 kB
  • After compression 3.5 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.3 kB, which is 12% 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 7.3 kB or 68% of the original size.

Image Optimization

-11%

Potential reduce by 40.6 kB

  • Original 386.5 kB
  • After minification 345.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. Obviously, Ehouse needs image optimization as it can save up to 40.6 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

-1%

Potential reduce by 1.3 kB

  • Original 108.2 kB
  • After minification 108.2 kB
  • After compression 106.9 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

-32%

Potential reduce by 3.8 kB

  • Original 12.1 kB
  • After minification 11.6 kB
  • After compression 8.3 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.ru needs all CSS files to be minified and compressed as it can save up to 3.8 kB or 32% of the original size.

Requests Breakdown

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

Requests Now

43

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ehouse.ru

ehouse.ru

450 ms

swfobject.js

swfobject.js

96 ms

jquery.ui.all.css

jquery.ui.all.css

196 ms

adt.css

adt.css

199 ms

jquery.js

jquery.js

296 ms

jquery-ui.js

jquery-ui.js

393 ms

modalpopup.js

modalpopup.js

197 ms

jquery.ui.base.css

jquery.ui.base.css

97 ms

jquery.ui.theme.css

jquery.ui.theme.css

103 ms

jquery.ui.core.css

jquery.ui.core.css

97 ms

jquery.ui.resizable.css

jquery.ui.resizable.css

96 ms

jquery.ui.selectable.css

jquery.ui.selectable.css

98 ms

jquery.ui.accordion.css

jquery.ui.accordion.css

98 ms

jquery.ui.autocomplete.css

jquery.ui.autocomplete.css

100 ms

jquery.ui.button.css

jquery.ui.button.css

193 ms

jquery.ui.dialog.css

jquery.ui.dialog.css

194 ms

jquery.ui.slider.css

jquery.ui.slider.css

196 ms

jquery.ui.tabs.css

jquery.ui.tabs.css

195 ms

jquery.ui.datepicker.css

jquery.ui.datepicker.css

195 ms

jquery.ui.progressbar.css

jquery.ui.progressbar.css

196 ms

top_grad.jpg

top_grad.jpg

97 ms

light_glow.jpg

light_glow.jpg

285 ms

toy_left.png

toy_left.png

379 ms

toy_right.png

toy_right.png

101 ms

bottom_grad.jpg

bottom_grad.jpg

100 ms

menu_bg.gif

menu_bg.gif

99 ms

border.gif

border.gif

200 ms

logo_big.gif

logo_big.gif

201 ms

flash.png

flash.png

288 ms

list.png

list.png

200 ms

fone.png

fone.png

282 ms

umi.png

umi.png

379 ms

classtoy_3.jpg

classtoy_3.jpg

287 ms

3_toner.jpg

3_toner.jpg

376 ms

none.gif

none.gif

378 ms

hot_dog.jpg

hot_dog.jpg

383 ms

foot_grad.jpg

foot_grad.jpg

370 ms

mail.gif

mail.gif

459 ms

map.gif

map.gif

459 ms

watch.js

watch.js

3 ms

analytics.js

analytics.js

9 ms

collect

collect

26 ms

collect

collect

30 ms

js

js

63 ms

ga-audiences

ga-audiences

103 ms

Accessibility Review

ehouse.ru accessibility score

93

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

ehouse.ru 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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

ehouse.ru SEO score

77

Search Engine Optimization Advices

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

ehouse.ru

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: