Tools & Wizards About Us
eedom.ru screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 87

    SEO

    Google-friendlier than
    65% of websites

eedom.ru

Остекление балконов, лоджий и окон. Пластиковые окна в Москве. Шкафы на заказ - Домашний Проект

Page Load Speed

6 sec in total

First Response

521 ms

Resources Loaded

5.3 sec

Page Rendered

182 ms

eedom.ru screenshot

About Website

Visit eedom.ru now to see the best up-to-date Eedom content for Russia and also check out these interesting facts you probably never knew about eedom.ru

Установка пластиковых окон. Остекление балконов и лоджий в домах любого типа. Продажа шкафов на заказ. Домашний Проект.

Visit eedom.ru

Key Findings

We analyzed Eedom.ru page load time and found that the first response time was 521 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

eedom.ru performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

78/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

31/100

25%

SI (Speed Index)

Value8.8 s

16/100

10%

TBT (Total Blocking Time)

Value1,180 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0.117

85/100

15%

TTI (Time to Interactive)

Value11.3 s

19/100

10%

Network Requests Diagram

eedom.ru

521 ms

www.eedom.ru

1248 ms

gtm.js

59 ms

body.bg.gif

153 ms

logo.png

261 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 72% of them (34 requests) were addressed to the original Eedom.ru, 4% (2 requests) were made to Googletagmanager.com and 4% (2 requests) were made to Code.jivosite.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Eedom.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 126.1 kB (22%)

Content Size

581.7 kB

After Optimization

455.7 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Eedom.ru main page is 581.7 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. 25% of websites need less resources to load. Javascripts take 262.2 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 117.6 kB

  • Original 143.8 kB
  • After minification 132.0 kB
  • After compression 26.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 117.6 kB or 82% of the original size.

Image Optimization

-3%

Potential reduce by 5.3 kB

  • Original 175.7 kB
  • After minification 170.4 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. Eedom images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 3.2 kB

  • Original 262.2 kB
  • After minification 262.2 kB
  • After compression 259.0 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.

Requests Breakdown

Number of requests can be reduced by 23 (51%)

Requests Now

45

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

eedom.ru

eedom.ru

521 ms

www.eedom.ru

www.eedom.ru

1248 ms

gtm.js

gtm.js

59 ms

body.bg.gif

body.bg.gif

153 ms

logo.png

logo.png

261 ms

sevice.bg.gif

sevice.bg.gif

365 ms

sevice.link.gif

sevice.link.gif

365 ms

top-menu-active.png

top-menu-active.png

378 ms

seach.gif

seach.gif

386 ms

b-action.jpg

b-action.jpg

770 ms

b_action_1.jpg

b_action_1.jpg

516 ms

b_action_3.jpg

b_action_3.jpg

846 ms

b_action_5.jpg

b_action_5.jpg

770 ms

sl-l.png

sl-l.png

503 ms

sl-r.png

sl-r.png

515 ms

plastikovye_okna_wm.png

plastikovye_okna_wm.png

877 ms

gradus.flat.png

gradus.flat.png

643 ms

gradus.home.png

gradus.home.png

644 ms

list.arrow.gif

list.arrow.gif

771 ms

balkony.png

balkony.png

773 ms

gradus.minus.png

gradus.minus.png

897 ms

gradus.plus.png

gradus.plus.png

889 ms

izgotovlenie_shkafov_wm.png

izgotovlenie_shkafov_wm.png

1153 ms

gradus.shkaf1.png

gradus.shkaf1.png

901 ms

gradus.shkaf2.png

gradus.shkaf2.png

967 ms

menu.bg.gif

menu.bg.gif

1001 ms

blinel1.png

blinel1.png

1011 ms

blinel2.png

blinel2.png

1024 ms

blinel3.png

blinel3.png

1028 ms

blinel4.png

blinel4.png

1087 ms

blinel5.png

blinel5.png

1126 ms

blinel6.png

blinel6.png

1131 ms

foot-bg.png

foot-bg.png

1152 ms

jquery-1.8.0.min.js

jquery-1.8.0.min.js

1420 ms

bundle.min11.js

bundle.min11.js

1708 ms

widget.js

widget.js

75 ms

js

js

57 ms

cookieconsent.min.css

cookieconsent.min.css

34 ms

cookieconsent.min.js

cookieconsent.min.js

43 ms

init.js

init.js

1009 ms

tag.js

tag.js

938 ms

ES7Gu9guyF

ES7Gu9guyF

213 ms

ES7Gu9guyF

ES7Gu9guyF

540 ms

openapi.c340c125c61ec5745ebb2a98626e46ab.js

openapi.c340c125c61ec5745ebb2a98626e46ab.js

209 ms

rtrg

rtrg

120 ms

advert.gif

advert.gif

690 ms

sync_cookie_image_decide

sync_cookie_image_decide

170 ms

Accessibility Review

eedom.ru accessibility score

85

Accessibility Issues

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.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

eedom.ru best practices score

67

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

eedom.ru SEO score

87

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

High

Tap targets are not sized appropriately

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

eedom.ru

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