Tools & Wizards About Us
ekrom.ru screenshot

Report Summary

  • 13

    Performance

    Renders faster than
    26% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

ekrom.ru

✔️ EKROM.RU | Интернет-магазин встраиваемой бытовой техники в Екатеринбурге

Page Load Speed

7.2 sec in total

First Response

618 ms

Resources Loaded

6.3 sec

Page Rendered

321 ms

ekrom.ru screenshot

About Website

Click here to check amazing EKROM content for Russia. Otherwise, check out these important facts you probably never knew about ekrom.ru

EKROM.RU - интернет-магазин встраиваемой бытовой техники в Екатеринбурге ⏫️ Официальный дистрибьютор ✅️ Скидки от 10% на БЫТОВУЮ ТЕХНИКУ ДЛЯ КУХНИ ⭐️ Возможность посмотреть товар до покупки!

Visit ekrom.ru

Key Findings

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

ekrom.ru performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

5/100

10%

LCP (Largest Contentful Paint)

Value14.6 s

0/100

25%

SI (Speed Index)

Value12.3 s

3/100

10%

TBT (Total Blocking Time)

Value3,370 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.155

74/100

15%

TTI (Time to Interactive)

Value26.2 s

0/100

10%

Network Requests Diagram

ekrom.ru

618 ms

www.ekrom.ru

934 ms

style.css

378 ms

conts.css

359 ms

extra.css

361 ms

Our browser made a total of 95 requests to load all elements on the main page. We found that 83% of them (79 requests) were addressed to the original Ekrom.ru, 5% (5 requests) were made to I3.ytimg.com and 2% (2 requests) were made to Counter.yadro.ru. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Ekrom.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (40%)

Content Size

2.9 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ekrom.ru main page is 2.9 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. 45% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 378.1 kB

  • Original 430.3 kB
  • After minification 408.9 kB
  • After compression 52.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 378.1 kB or 88% of the original size.

Image Optimization

-24%

Potential reduce by 501.0 kB

  • Original 2.1 MB
  • After minification 1.6 MB

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, EKROM needs image optimization as it can save up to 501.0 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-67%

Potential reduce by 177.7 kB

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

CSS Optimization

-81%

Potential reduce by 94.2 kB

  • Original 116.9 kB
  • After minification 92.9 kB
  • After compression 22.7 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. Ekrom.ru needs all CSS files to be minified and compressed as it can save up to 94.2 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 36 (41%)

Requests Now

88

After Optimization

52

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ekrom.ru

ekrom.ru

618 ms

www.ekrom.ru

www.ekrom.ru

934 ms

style.css

style.css

378 ms

conts.css

conts.css

359 ms

extra.css

extra.css

361 ms

dmodule.css

dmodule.css

368 ms

jquery.fancybox-1.3.4.css

jquery.fancybox-1.3.4.css

369 ms

tooltip.css

tooltip.css

383 ms

highslide.css

highslide.css

535 ms

jquery-1.7.2.min.js

jquery-1.7.2.min.js

905 ms

carousel.js

carousel.js

565 ms

highslide.js

highslide.js

753 ms

utils.js

utils.js

566 ms

all.js

all.js

779 ms

site.js

site.js

842 ms

dmodule.js

dmodule.js

846 ms

jquery.tooltip.min.js

jquery.tooltip.min.js

751 ms

jquery.anythingslider.js

jquery.anythingslider.js

1040 ms

jquery.fancybox-1.3.4.js

jquery.fancybox-1.3.4.js

1041 ms

tooltip.js

tooltip.js

1043 ms

fancybox.js

fancybox.js

1044 ms

mqdefault.jpg

mqdefault.jpg

205 ms

mqdefault.jpg

mqdefault.jpg

228 ms

mqdefault.jpg

mqdefault.jpg

230 ms

mqdefault.jpg

mqdefault.jpg

252 ms

mqdefault.jpg

mqdefault.jpg

206 ms

logo_ekrom.png

logo_ekrom.png

205 ms

triangle_arrow.png

triangle_arrow.png

201 ms

user_info_shadow.png

user_info_shadow.png

202 ms

tooltip.png

tooltip.png

199 ms

buttons_left.png

buttons_left.png

206 ms

buttons_right.png

buttons_right.png

226 ms

70_left_overflow.jpg

70_left_overflow.jpg

516 ms

70_right_overflow.jpg

70_right_overflow.jpg

519 ms

70_picture.jpg

70_picture.jpg

1715 ms

71_left_overflow.jpg

71_left_overflow.jpg

519 ms

71_right_overflow.jpg

71_right_overflow.jpg

1623 ms

71_picture.jpg

71_picture.jpg

3204 ms

72_left_overflow.jpg

72_left_overflow.jpg

860 ms

72_right_overflow.jpg

72_right_overflow.jpg

864 ms

72_picture.jpg

72_picture.jpg

1536 ms

64_left_overflow.jpg

64_left_overflow.jpg

1186 ms

64_right_overflow.jpg

64_right_overflow.jpg

1212 ms

64_picture.jpg

64_picture.jpg

2295 ms

26_left_overflow.jpg

26_left_overflow.jpg

1538 ms

26_right_overflow.jpg

26_right_overflow.jpg

1889 ms

26_picture.jpg

26_picture.jpg

2958 ms

slider_circle.png

slider_circle.png

1782 ms

picture_1994_face.jpg

picture_1994_face.jpg

2045 ms

lenta.png

lenta.png

1941 ms

icon.png

icon.png

2060 ms

stars.png

stars.png

2097 ms

basket_button.png

basket_button.png

2207 ms

picture_1987_face.jpg

picture_1987_face.jpg

2235 ms

picture_1584_face.jpg

picture_1584_face.jpg

2607 ms

picture_1734_face.jpg

picture_1734_face.jpg

2381 ms

picture_4513_face.jpg

picture_4513_face.jpg

2407 ms

hit

hit

957 ms

picture_3898_face.jpg

picture_3898_face.jpg

2553 ms

picture_3944_face.jpg

picture_3944_face.jpg

2665 ms

picture_4123_face.jpg

picture_4123_face.jpg

2520 ms

picture_4133_face.jpg

picture_4133_face.jpg

2720 ms

watch.js

watch.js

2 ms

picture_738_face.jpg

picture_738_face.jpg

2728 ms

client.js

client.js

780 ms

rtrg

rtrg

375 ms

watch.js

watch.js

3 ms

client.js

client.js

793 ms

analytics.js

analytics.js

120 ms

picture_1405_face.jpg

picture_1405_face.jpg

2609 ms

picture_4126_face.png

picture_4126_face.png

2702 ms

picture_4119_face.jpg

picture_4119_face.jpg

2799 ms

picture_4350_face.jpg

picture_4350_face.jpg

2783 ms

collect

collect

51 ms

picture_4374_face.jpg

picture_4374_face.jpg

3166 ms

picture_4325_face.jpg

picture_4325_face.jpg

3080 ms

collect

collect

281 ms

picture_4366_face.jpg

picture_4366_face.jpg

2635 ms

filter_shadow.png

filter_shadow.png

2651 ms

banner.gif

banner.gif

2688 ms

up_arrow.jpg

up_arrow.jpg

2508 ms

str.png

str.png

2510 ms

152 ms

hit

hit

137 ms

down_arrow.jpg

down_arrow.jpg

2203 ms

useful.png

useful.png

2185 ms

photogallery.png

photogallery.png

1937 ms

video.png

video.png

1993 ms

subscribe.png

subscribe.png

1911 ms

footer_shadow_ext.png

footer_shadow_ext.png

1851 ms

burusov.png

burusov.png

1777 ms

footer_shadow.png

footer_shadow.png

1673 ms

rounded-white.png

rounded-white.png

167 ms

zoomout.cur

zoomout.cur

165 ms

loader.white.gif

loader.white.gif

167 ms

Accessibility Review

ekrom.ru accessibility score

60

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

<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

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

ekrom.ru SEO score

79

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ekrom.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 Ekrom.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

ekrom.ru

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