Tools & Wizards About Us
ekort.ru screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

ekort.ru

Магазин канцтовары, канцелярские товары для офиса, хозтовары, бумага для принтера купить бумагу в каталоге Экорт

Page Load Speed

4 sec in total

First Response

371 ms

Resources Loaded

3 sec

Page Rendered

683 ms

ekort.ru screenshot

About Website

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

Магазин товаров для офиса - канцтовары, бумага для принтера в нашем каталоге, офисные и канцелярские товары, хозтовары, купить бумагу, широкий ассортимент продукции

Visit ekort.ru

Key Findings

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

ekort.ru performance score

0

Network Requests Diagram

ekort.ru

371 ms

www.ekort.ru

775 ms

css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css

256 ms

css_2lFRtnqUn0K7j4LSadCJo3sRML-j_AcmGqU4wyxKsPc.css

257 ms

css_a2N7nR6ze5ixy4iz1xaiiiTcG-cQe9KPbj9P--JRE6A.css

381 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 71% of them (40 requests) were addressed to the original Ekort.ru, 9% (5 requests) were made to Mc.yandex.ru and 5% (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 Ekort.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 826.8 kB (59%)

Content Size

1.4 MB

After Optimization

575.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-83%

Potential reduce by 208.5 kB

  • Original 250.0 kB
  • After minification 247.5 kB
  • After compression 41.5 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 208.5 kB or 83% of the original size.

Image Optimization

-12%

Potential reduce by 43.7 kB

  • Original 375.7 kB
  • After minification 332.0 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. Obviously, Ekort needs image optimization as it can save up to 43.7 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

-71%

Potential reduce by 400.7 kB

  • Original 568.0 kB
  • After minification 506.2 kB
  • After compression 167.3 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 400.7 kB or 71% of the original size.

CSS Optimization

-83%

Potential reduce by 173.9 kB

  • Original 208.4 kB
  • After minification 203.0 kB
  • After compression 34.6 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. Ekort.ru needs all CSS files to be minified and compressed as it can save up to 173.9 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (47%)

Requests Now

53

After Optimization

28

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ekort.ru

ekort.ru

371 ms

www.ekort.ru

www.ekort.ru

775 ms

css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css

css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css

256 ms

css_2lFRtnqUn0K7j4LSadCJo3sRML-j_AcmGqU4wyxKsPc.css

css_2lFRtnqUn0K7j4LSadCJo3sRML-j_AcmGqU4wyxKsPc.css

257 ms

css_a2N7nR6ze5ixy4iz1xaiiiTcG-cQe9KPbj9P--JRE6A.css

css_a2N7nR6ze5ixy4iz1xaiiiTcG-cQe9KPbj9P--JRE6A.css

381 ms

css_8nMW9S8jou120LQWXXRX9z0C_FnFZVI5G5nBcJ1PLwI.css

css_8nMW9S8jou120LQWXXRX9z0C_FnFZVI5G5nBcJ1PLwI.css

518 ms

js_UWQINlriydSoeSiGQxToOUdv493zEa7dpsXC1OtYlZU.js

js_UWQINlriydSoeSiGQxToOUdv493zEa7dpsXC1OtYlZU.js

664 ms

js_nT-3TqmhkiIn30tHICx1inWtvQizOLtaBPI9cbRYVJE.js

js_nT-3TqmhkiIn30tHICx1inWtvQizOLtaBPI9cbRYVJE.js

507 ms

js_BnFCUje0JbP9ucG298Eia01rfEPInxn3m7rLD0b6xvw.js

js_BnFCUje0JbP9ucG298Eia01rfEPInxn3m7rLD0b6xvw.js

640 ms

js_DHPgUTqElGc3A2oidrZKh7qRsKxLTVOdJ-sd7T29t78.js

js_DHPgUTqElGc3A2oidrZKh7qRsKxLTVOdJ-sd7T29t78.js

761 ms

share.js

share.js

13 ms

3_1_FFFFFFFF_EFEFEFFF_0_pageviews

3_1_FFFFFFFF_EFEFEFFF_0_pageviews

516 ms

fon.png

fon.png

136 ms

wrapper-front.png

wrapper-front.png

132 ms

logo.png

logo.png

139 ms

header.png

header.png

136 ms

menu.png

menu.png

820 ms

seach_button.png

seach_button.png

130 ms

93db9e995024a348f17b2.jpg

93db9e995024a348f17b2.jpg

513 ms

032508b850249bc0de210.jpg

032508b850249bc0de210.jpg

511 ms

ekort_ofisnye_papki.jpg

ekort_ofisnye_papki.jpg

512 ms

ekort_suveniry.jpg

ekort_suveniry.jpg

512 ms

ekort_bumaga_ezhednevniki.jpg

ekort_bumaga_ezhednevniki.jpg

512 ms

562396586b5024a334e1850.jpg

562396586b5024a334e1850.jpg

585 ms

f921df13ff50249738ddd6d.jpg

f921df13ff50249738ddd6d.jpg

585 ms

8e6299985024968ac8fc1.jpg

8e6299985024968ac8fc1.jpg

586 ms

c8f5b711650249a6f7e723.jpg

c8f5b711650249a6f7e723.jpg

586 ms

95bf2c09502499b63c9be.jpg

95bf2c09502499b63c9be.jpg

582 ms

home1.png

home1.png

695 ms

contact1.png

contact1.png

698 ms

sitemap1.png

sitemap1.png

705 ms

actions3.png

actions3.png

1038 ms

catalog-little-image1.png

catalog-little-image1.png

654 ms

marker.png

marker.png

768 ms

usluhi-icon.png

usluhi-icon.png

770 ms

best-buy-icon1.png

best-buy-icon1.png

781 ms

pink.png

pink.png

785 ms

zakaz.png

zakaz.png

886 ms

h2.png

h2.png

892 ms

li-about.png

li-about.png

897 ms

ikonka_monetka.png

ikonka_monetka.png

907 ms

li.png

li.png

891 ms

ga.js

ga.js

300 ms

watch.js

watch.js

393 ms

plusone.js

plusone.js

366 ms

oms.js

oms.js

384 ms

b-share-icon.png

b-share-icon.png

74 ms

__utm.gif

__utm.gif

34 ms

__utm.gif

__utm.gif

26 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

13 ms

watch.js

watch.js

438 ms

sessions.js

sessions.js

180 ms

advert.gif

advert.gif

85 ms

1

1

86 ms

hotlog_redirects

hotlog_redirects

171 ms

26812653

26812653

86 ms

SEO Factors

ekort.ru SEO score

0

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

ekort.ru

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