Tools & Wizards About Us
datahouse.ru screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

datahouse.ru

ЦОД (Центр Обработки Данных) — цены на услуги дата-центра в Москве, Санкт-Петербурге и Екатеринбурге

Page Load Speed

8.5 sec in total

First Response

721 ms

Resources Loaded

6 sec

Page Rendered

1.8 sec

datahouse.ru screenshot

About Website

Click here to check amazing Datahouse content for Turkey. Otherwise, check out these important facts you probably never knew about datahouse.ru

Услуги дата-центра по аренде серверов и их расположению в DataHouse. Подробнее об услугах центра обработки данных в Москве, Санкт-Петербурге и Екатеринбурге по телефону: +7 (495) 363-05-42

Visit datahouse.ru

Key Findings

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

datahouse.ru performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

7/100

10%

LCP (Largest Contentful Paint)

Value10.8 s

0/100

25%

SI (Speed Index)

Value16.9 s

0/100

10%

TBT (Total Blocking Time)

Value28,460 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value40.3 s

0/100

10%

Network Requests Diagram

datahouse.ru

721 ms

www.datahouse.ru

1202 ms

node.css

260 ms

defaults.css

259 ms

system.css

262 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 78% of them (31 requests) were addressed to the original Datahouse.ru, 15% (6 requests) were made to Api-maps.yandex.ru and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Datahouse.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 273.0 kB (49%)

Content Size

559.8 kB

After Optimization

286.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Datahouse.ru main page is 559.8 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. 20% of websites need less resources to load. HTML takes 179.6 kB which makes up the majority of the site volume.

HTML Optimization

-63%

Potential reduce by 113.4 kB

  • Original 179.6 kB
  • After minification 177.7 kB
  • After compression 66.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 113.4 kB or 63% of the original size.

Image Optimization

-5%

Potential reduce by 8.0 kB

  • Original 172.3 kB
  • After minification 164.3 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. Datahouse images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 113.7 kB

  • Original 160.2 kB
  • After minification 105.4 kB
  • After compression 46.5 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 113.7 kB or 71% of the original size.

CSS Optimization

-79%

Potential reduce by 37.8 kB

  • Original 47.6 kB
  • After minification 35.0 kB
  • After compression 9.8 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. Datahouse.ru needs all CSS files to be minified and compressed as it can save up to 37.8 kB or 79% of the original size.

Requests Breakdown

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

Requests Now

33

After Optimization

16

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

datahouse.ru

datahouse.ru

721 ms

www.datahouse.ru

www.datahouse.ru

1202 ms

node.css

node.css

260 ms

defaults.css

defaults.css

259 ms

system.css

system.css

262 ms

system-menus.css

system-menus.css

263 ms

user.css

user.css

258 ms

content-module.css

content-module.css

315 ms

filefield.css

filefield.css

384 ms

extlink.css

extlink.css

389 ms

reset.css

reset.css

411 ms

style.css

style.css

539 ms

jquery.js

jquery.js

962 ms

drupal.js

drupal.js

442 ms

ru_b1668fb58aef8360249b240f71e827b6.js

ru_b1668fb58aef8360249b240f71e827b6.js

530 ms

extlink.js

extlink.js

526 ms

main.js

main.js

566 ms

callback.js

callback.js

597 ms

691 ms

combine.xml

combine.xml

2532 ms

signin.png

signin.png

157 ms

vkico.png

vkico.png

148 ms

fbico.png

fbico.png

147 ms

twitterico.png

twitterico.png

193 ms

logo.png

logo.png

186 ms

mainbanner.jpg

mainbanner.jpg

2677 ms

sprite_icons.gif

sprite_icons.gif

259 ms

list.gif

list.gif

273 ms

mastercardico.jpg

mastercardico.jpg

266 ms

visaico.jpg

visaico.jpg

274 ms

webmoneyico.jpg

webmoneyico.jpg

276 ms

yandexico.jpg

yandexico.jpg

403 ms

mailico.png

mailico.png

405 ms

watch.js

watch.js

54 ms

analytics.js

analytics.js

60 ms

collect

collect

18 ms

ef50ac9e93aaebe3299791c79f277f8e.cur

ef50ac9e93aaebe3299791c79f277f8e.cur

154 ms

3ce22e999d54bb9ca8150a59207f9d3e.cur

3ce22e999d54bb9ca8150a59207f9d3e.cur

190 ms

4965b66fe115b2f2ed500ece66514d86.cur

4965b66fe115b2f2ed500ece66514d86.cur

333 ms

77492cf358d8b12629399322926c93f2.cur

77492cf358d8b12629399322926c93f2.cur

481 ms

Accessibility Review

datahouse.ru accessibility score

61

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

Image elements do not have [alt] attributes

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.

Best Practices

datahouse.ru best practices score

75

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

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

datahouse.ru SEO score

93

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

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

    RU

  • Language Claimed

    RU

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Datahouse.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it matches the claimed language. Our system also found out that Datahouse.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

datahouse.ru

Open Graph description is not detected on the main page of Datahouse. 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: