Tools & Wizards About Us
e-katalog.ru screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

e-katalog.ru

e-Katalog - каталог товаров, сравнение цен в интернет-магазинах России

Page Load Speed

3.7 sec in total

First Response

374 ms

Resources Loaded

3 sec

Page Rendered

295 ms

e-katalog.ru screenshot

About Website

Click here to check amazing E Katalog content for Russia. Otherwise, check out these important facts you probably never knew about e-katalog.ru

Каталог товаров E-Katalog >

Visit e-katalog.ru

Key Findings

We analyzed E-katalog.ru page load time and found that the first response time was 374 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

e-katalog.ru performance score

0

Network Requests Diagram

e-katalog.ru

374 ms

www.e-katalog.ru

551 ms

ek-template_min.css

393 ms

prettyPhoto.css

258 ms

ek-start.css

260 ms

Our browser made a total of 123 requests to load all elements on the main page. We found that 54% of them (67 requests) were addressed to the original E-katalog.ru, 9% (11 requests) were made to Apis.google.com and 2% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain E-katalog.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 740.7 kB (35%)

Content Size

2.1 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-81%

Potential reduce by 87.4 kB

  • Original 108.1 kB
  • After minification 95.5 kB
  • After compression 20.7 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 12.6 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 87.4 kB or 81% of the original size.

Image Optimization

-12%

Potential reduce by 164.5 kB

  • Original 1.4 MB
  • After minification 1.2 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, E Katalog needs image optimization as it can save up to 164.5 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-68%

Potential reduce by 268.4 kB

  • Original 392.2 kB
  • After minification 319.9 kB
  • After compression 123.8 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 268.4 kB or 68% of the original size.

CSS Optimization

-80%

Potential reduce by 220.3 kB

  • Original 275.6 kB
  • After minification 262.9 kB
  • After compression 55.2 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. E-katalog.ru needs all CSS files to be minified and compressed as it can save up to 220.3 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 48 (42%)

Requests Now

113

After Optimization

65

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

e-katalog.ru

e-katalog.ru

374 ms

www.e-katalog.ru

www.e-katalog.ru

551 ms

ek-template_min.css

ek-template_min.css

393 ms

prettyPhoto.css

prettyPhoto.css

258 ms

ek-start.css

ek-start.css

260 ms

ek-bottom-goods-toolbar.css

ek-bottom-goods-toolbar.css

263 ms

jquery.min.js

jquery.min.js

67 ms

ek_lib.min.js

ek_lib.min.js

389 ms

mp_slider.js

mp_slider.js

263 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

266 ms

goods_toolbar.js

goods_toolbar.js

265 ms

preload.gif

preload.gif

130 ms

one-pixel-ico.gif

one-pixel-ico.gif

131 ms

52855.jpg

52855.jpg

134 ms

92555.jpg

92555.jpg

136 ms

188406.jpg

188406.jpg

139 ms

697826.jpg

697826.jpg

136 ms

311531.jpg

311531.jpg

257 ms

555038.jpg

555038.jpg

265 ms

233253.jpg

233253.jpg

263 ms

581260.jpg

581260.jpg

265 ms

medium_pic.jpg

medium_pic.jpg

392 ms

medium_pic.jpg

medium_pic.jpg

262 ms

medium_pic.jpg

medium_pic.jpg

386 ms

medium_pic.jpg

medium_pic.jpg

551 ms

medium_pic.jpg

medium_pic.jpg

409 ms

small_pic.jpg

small_pic.jpg

389 ms

small_pic.jpg

small_pic.jpg

393 ms

small_pic.jpg

small_pic.jpg

547 ms

small_pic.jpg

small_pic.jpg

547 ms

analytics.js

analytics.js

7 ms

ek-logo.png

ek-logo.png

542 ms

ecommerce.js

ecommerce.js

7 ms

collect

collect

19 ms

top-icons.png

top-icons.png

530 ms

images_20.png

images_20.png

531 ms

collect

collect

62 ms

slider-1-1.jpg

slider-1-1.jpg

650 ms

slider-1-2.jpg

slider-1-2.jpg

647 ms

slider-1-5.jpg

slider-1-5.jpg

639 ms

slider-1-6.jpg

slider-1-6.jpg

643 ms

slider-1-3.jpg

slider-1-3.jpg

765 ms

slider-1-4.jpg

slider-1-4.jpg

648 ms

slider-3-3.jpg

slider-3-3.jpg

768 ms

slider-3-4.jpg

slider-3-4.jpg

772 ms

slider-3-6.jpg

slider-3-6.jpg

778 ms

slider-3-1.jpg

slider-3-1.jpg

778 ms

slider-3-2.jpg

slider-3-2.jpg

781 ms

slider-3-5.jpg

slider-3-5.jpg

1028 ms

slider-4-1.jpg

slider-4-1.jpg

1027 ms

slider-4-2.jpg

slider-4-2.jpg

901 ms

ga-audiences

ga-audiences

40 ms

slider-4-3.jpg

slider-4-3.jpg

819 ms

slider-4-4.jpg

slider-4-4.jpg

821 ms

slider-4-5.jpg

slider-4-5.jpg

820 ms

slider-4-6.jpg

slider-4-6.jpg

938 ms

slider-2-5.jpg

slider-2-5.jpg

939 ms

slider-2-6.jpg

slider-2-6.jpg

942 ms

client:plusone.js

client:plusone.js

57 ms

watch.js

watch.js

480 ms

platform.js

platform.js

121 ms

gtm.js

gtm.js

32 ms

ld.js

ld.js

41 ms

tags

tags

253 ms

ek_ga-events.js

ek_ga-events.js

826 ms

slider-2-4.jpg

slider-2-4.jpg

951 ms

slider-2-1.jpg

slider-2-1.jpg

944 ms

slider-2-2.jpg

slider-2-2.jpg

948 ms

slider-2-3.jpg

slider-2-3.jpg

949 ms

event

event

23 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

18 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

11 ms

page

page

106 ms

event

event

243 ms

counter2

counter2

233 ms

postmessageRelay

postmessageRelay

42 ms

api.js

api.js

50 ms

core:rpc:shindig.random:shindig.sha1.js

core:rpc:shindig.random:shindig.sha1.js

193 ms

2536007149-postmessagerelay.js

2536007149-postmessagerelay.js

119 ms

slider-arrows-1.png

slider-arrows-1.png

827 ms

cat-icons.png

cat-icons.png

958 ms

s-about-icon.png

s-about-icon.png

945 ms

ic-phone-b.gif

ic-phone-b.gif

947 ms

rs=AGLTcCOldiz7BxP14VvzYLiKh1pcAfK41A

rs=AGLTcCOldiz7BxP14VvzYLiKh1pcAfK41A

21 ms

rs=AGLTcCPhDrHY2vagSjsLFOxeufqSzVU3ow

rs=AGLTcCPhDrHY2vagSjsLFOxeufqSzVU3ow

31 ms

rs=AGLTcCPFN_cQ2HhSgaAgWeOeoqFC7kk9dw

rs=AGLTcCPFN_cQ2HhSgaAgWeOeoqFC7kk9dw

54 ms

bg-bottom-menu-1.gif

bg-bottom-menu-1.gif

934 ms

photo.jpg

photo.jpg

211 ms

rs=AGLTcCPFN_cQ2HhSgaAgWeOeoqFC7kk9dw

rs=AGLTcCPFN_cQ2HhSgaAgWeOeoqFC7kk9dw

62 ms

UserMatch.ashx

UserMatch.ashx

88 ms

pixel

pixel

268 ms

pixel

pixel

88 ms

135 ms

RtbHouse

RtbHouse

258 ms

tagging

tagging

110 ms

Pug

Pug

83 ms

sync.cgi

sync.cgi

298 ms

sync3.302

sync3.302

285 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

133 ms

dtpHsbgPEm2lVWciJZ0P-A.ttf

dtpHsbgPEm2lVWciJZ0P-A.ttf

135 ms

bdHGHleUa-ndQCOrdpfxfw.ttf

bdHGHleUa-ndQCOrdpfxfw.ttf

144 ms

bottom-bar-sprite.5.png

bottom-bar-sprite.5.png

793 ms

bottom-bar-sprite.12.png

bottom-bar-sprite.12.png

794 ms

scroll-bg.png

scroll-bg.png

924 ms

544812.jpg

544812.jpg

923 ms

rs=AGLTcCPFN_cQ2HhSgaAgWeOeoqFC7kk9dw

rs=AGLTcCPFN_cQ2HhSgaAgWeOeoqFC7kk9dw

46 ms

match

match

42 ms

tap.php

tap.php

41 ms

sd

sd

29 ms

cm

cm

99 ms

advert.gif

advert.gif

85 ms

1by1.png

1by1.png

6 ms

1

1

84 ms

cm

cm

94 ms

all.js

all.js

268 ms

pix_st_v2.php

pix_st_v2.php

362 ms

pix_st.php

pix_st.php

394 ms

openapi.js

openapi.js

395 ms

46 ms

xd_arbiter.php

xd_arbiter.php

219 ms

xd_arbiter.php

xd_arbiter.php

426 ms

dis.aspx

dis.aspx

182 ms

xd_arbiter.php

xd_arbiter.php

198 ms

SEO Factors

e-katalog.ru SEO score

0

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise E-katalog.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 E-katalog.ru main page’s claimed encoding is iso-8859-1. 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

e-katalog.ru

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