Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

esmag.ru

ESMAG.RU в г.Екатеринбург магазин сантехники

Page Load Speed

11.3 sec in total

First Response

2.5 sec

Resources Loaded

8.4 sec

Page Rendered

338 ms

esmag.ru screenshot

About Website

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

Интернет-магазин сантехники ESMAG.RU в г.Екатеринбург Продажа: ванн, смесителей и мебели в ванную, кабин, унитазов и инсталляций. Сантехника с доставкой.

Visit esmag.ru

Key Findings

We analyzed Esmag.ru page load time and found that the first response time was 2.5 sec and then it took 8.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

esmag.ru performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value3.6 s

61/100

25%

SI (Speed Index)

Value9.0 s

14/100

10%

TBT (Total Blocking Time)

Value760 ms

39/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value13.7 s

11/100

10%

Network Requests Diagram

esmag.ru

2476 ms

normalize.css

300 ms

foundation.css

958 ms

default.css

764 ms

menu.css

309 ms

Our browser made a total of 137 requests to load all elements on the main page. We found that 84% of them (115 requests) were addressed to the original Esmag.ru, 3% (4 requests) were made to Mc.yandex.ru and 3% (4 requests) were made to Openstat.net. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Esmag.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.6 MB (52%)

Content Size

3.1 MB

After Optimization

1.5 MB

In fact, the total size of Esmag.ru main page is 3.1 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. 50% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 277.4 kB

  • Original 304.2 kB
  • After minification 234.3 kB
  • After compression 26.9 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 69.9 kB, which is 23% 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 277.4 kB or 91% of the original size.

Image Optimization

-3%

Potential reduce by 32.6 kB

  • Original 1.1 MB
  • After minification 1.1 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. ESMAG images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 847.4 kB

  • Original 1.2 MB
  • After minification 1.1 MB
  • After compression 310.6 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 847.4 kB or 73% of the original size.

CSS Optimization

-87%

Potential reduce by 474.2 kB

  • Original 546.0 kB
  • After minification 407.5 kB
  • After compression 71.9 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. Esmag.ru needs all CSS files to be minified and compressed as it can save up to 474.2 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 43 (33%)

Requests Now

130

After Optimization

87

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

Accessibility Review

esmag.ru accessibility score

72

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

Document doesn't have a <title> element

High

Links do not have a discernible name

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

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

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

esmag.ru SEO score

79

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

Document doesn't have a <title> element

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    WINDOWS-1251

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Esmag.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 Esmag.ru main page’s claimed encoding is windows-1251. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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