Tools & Wizards About Us
linoleum.ru screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

linoleum.ru

Линолеум - от производителя со склада в Москве, Санкт-Петербурге с доставкой по России

Page Load Speed

4.7 sec in total

First Response

839 ms

Resources Loaded

3.3 sec

Page Rendered

547 ms

linoleum.ru screenshot

About Website

Welcome to linoleum.ru homepage info - get ready to check Linoleum best content for Russia right away, or after learning these important things about linoleum.ru

Линолеум с доставкой по России. Линолеум всех видов от производителя. Производим и реализуем линолеум под заказ любого размера и количества.

Visit linoleum.ru

Key Findings

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

linoleum.ru performance score

0

Network Requests Diagram

linoleum.ru

839 ms

screen.css

272 ms

essencials.css

281 ms

css

68 ms

jquery-1.11.0.min.js

421 ms

Our browser made a total of 87 requests to load all elements on the main page. We found that 77% of them (67 requests) were addressed to the original Linoleum.ru, 6% (5 requests) were made to Widgets.livetex.ru and 5% (4 requests) were made to Mc.yandex.ru. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Linoleum.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 566.4 kB (20%)

Content Size

2.9 MB

After Optimization

2.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Linoleum.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. 55% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 274.0 kB

  • Original 320.5 kB
  • After minification 318.4 kB
  • After compression 46.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 274.0 kB or 85% of the original size.

Image Optimization

-4%

Potential reduce by 88.3 kB

  • Original 2.3 MB
  • After minification 2.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. Linoleum images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 139.3 kB

  • Original 211.6 kB
  • After minification 204.5 kB
  • After compression 72.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 139.3 kB or 66% of the original size.

CSS Optimization

-85%

Potential reduce by 64.8 kB

  • Original 76.3 kB
  • After minification 58.5 kB
  • After compression 11.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. Linoleum.ru needs all CSS files to be minified and compressed as it can save up to 64.8 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (40%)

Requests Now

81

After Optimization

49

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 81 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Linoleum. 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 from 9 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

linoleum.ru

linoleum.ru

839 ms

screen.css

screen.css

272 ms

essencials.css

essencials.css

281 ms

css

css

68 ms

jquery-1.11.0.min.js

jquery-1.11.0.min.js

421 ms

jquery.nouislider.min.js

jquery.nouislider.min.js

283 ms

jquery.nouislider.css

jquery.nouislider.css

284 ms

jquery.fancybox.css

jquery.fancybox.css

283 ms

jquery.fancybox.pack.js

jquery.fancybox.pack.js

403 ms

jquery.counter-analog.css

jquery.counter-analog.css

402 ms

jquery.counter.js

jquery.counter.js

416 ms

common.js

common.js

441 ms

slider.css

slider.css

446 ms

53f4e7de4ee7217e1ecdd6157b4b1603.jpg

53f4e7de4ee7217e1ecdd6157b4b1603.jpg

445 ms

513c22331b0745a11c0209ce3c681fba.png

513c22331b0745a11c0209ce3c681fba.png

670 ms

7ecd53bc368417d2d3a6043fd23055a7.jpg

7ecd53bc368417d2d3a6043fd23055a7.jpg

305 ms

0bd0b20c002b3d3d6136bcc2746e3760_tn.jpg

0bd0b20c002b3d3d6136bcc2746e3760_tn.jpg

537 ms

4078e9aa8a39e86d998f19944261abef_tn.jpg

4078e9aa8a39e86d998f19944261abef_tn.jpg

284 ms

044a468c06f6f5b17fc41716c5265b43_tn.jpg

044a468c06f6f5b17fc41716c5265b43_tn.jpg

286 ms

c40c78faa085f85c2a0654bf49a7bfbf_tn.jpg

c40c78faa085f85c2a0654bf49a7bfbf_tn.jpg

711 ms

9d0b4bcc06bed3716261cd5f0f1cf038_tn.jpg

9d0b4bcc06bed3716261cd5f0f1cf038_tn.jpg

711 ms

3aee62682aac63aea0caa5142f22dc18_tn.jpg

3aee62682aac63aea0caa5142f22dc18_tn.jpg

725 ms

contest3.gif

contest3.gif

296 ms

top-bar-search-icon.png

top-bar-search-icon.png

427 ms

top-bar-warehouses.png

top-bar-warehouses.png

564 ms

top-bar-email.png

top-bar-email.png

569 ms

logo.png

logo.png

658 ms

icon-multi-line.png

icon-multi-line.png

701 ms

icon-wholesale.png

icon-wholesale.png

710 ms

icon-managers.png

icon-managers.png

789 ms

accordion-closed.png

accordion-closed.png

789 ms

recent-news-left.png

recent-news-left.png

829 ms

recent-news-right.png

recent-news-right.png

836 ms

900_400-.jpg

900_400-.jpg

1254 ms

900_400-5.jpg

900_400-5.jpg

1173 ms

bann_tornado.jpg

bann_tornado.jpg

1197 ms

900_400-9.jpg

900_400-9.jpg

1323 ms

6e9916a3620673cc02fda058ae863bb6.png

6e9916a3620673cc02fda058ae863bb6.png

968 ms

900_400_s.jpg

900_400_s.jpg

979 ms

900_400-5_s.jpg

900_400-5_s.jpg

1108 ms

bann_tornado_s.jpg

bann_tornado_s.jpg

1121 ms

900_400-9_s.jpg

900_400-9_s.jpg

1249 ms

arrow-left.png

arrow-left.png

1262 ms

arrow-right.png

arrow-right.png

1312 ms

8b3a0165f1c85bd73b2598b3a457b0ac_tn.jpg

8b3a0165f1c85bd73b2598b3a457b0ac_tn.jpg

1335 ms

5416750d84e9f878b1207a4666f85d86_tn.jpg

5416750d84e9f878b1207a4666f85d86_tn.jpg

1667 ms

8fc027df3b333acd6e195e29e1af600f_tn.jpg

8fc027df3b333acd6e195e29e1af600f_tn.jpg

1400 ms

a85423a8528dcfdf695bafd50ec397e4_tn.jpg

a85423a8528dcfdf695bafd50ec397e4_tn.jpg

1559 ms

f0eb7a29de141312fd856943b04d2e8b_tn.jpg

f0eb7a29de141312fd856943b04d2e8b_tn.jpg

1454 ms

e8baf7db5240e4ab224010f8c0c6d4f8_tn.jpg

e8baf7db5240e4ab224010f8c0c6d4f8_tn.jpg

1458 ms

watch.js

watch.js

188 ms

95e7bacc53c69390be23b8f8b7ceca10_tn.jpg

95e7bacc53c69390be23b8f8b7ceca10_tn.jpg

1434 ms

isZ-wbCXNKAbnjo6_TwHTqCWcynf_cDxXwCLxiixG1c.ttf

isZ-wbCXNKAbnjo6_TwHTqCWcynf_cDxXwCLxiixG1c.ttf

107 ms

oHi30kwQWvpCWqAhzHcCSKCWcynf_cDxXwCLxiixG1c.ttf

oHi30kwQWvpCWqAhzHcCSKCWcynf_cDxXwCLxiixG1c.ttf

127 ms

B85vmdvDILX92ray16e-1g.ttf

B85vmdvDILX92ray16e-1g.ttf

127 ms

hit

hit

281 ms

counter.php

counter.php

306 ms

client.js

client.js

248 ms

watch.js

watch.js

438 ms

4fdf720b928ead768ecf862f0f3ec784_tn.jpg

4fdf720b928ead768ecf862f0f3ec784_tn.jpg

1292 ms

231446bf0f8f08201a906f97fa8f79b6_tn.jpg

231446bf0f8f08201a906f97fa8f79b6_tn.jpg

1333 ms

6c263f635947af19b8a33cb0298f8186_tn.jpg

6c263f635947af19b8a33cb0298f8186_tn.jpg

1312 ms

hit

hit

128 ms

e19a0c302cf9c5648e008d9674f69828_tn.jpg

e19a0c302cf9c5648e008d9674f69828_tn.jpg

1187 ms

760bb0a9fc1902d09823e963ffb8dbe1.png

760bb0a9fc1902d09823e963ffb8dbe1.png

1668 ms

more-icon.png

more-icon.png

1174 ms

app3.js

app3.js

587 ms

1fcad3b78edccac3378ce7758f810355.jpg

1fcad3b78edccac3378ce7758f810355.jpg

1178 ms

8fc027df3b333acd6e195e29e1af600f_m.jpg

8fc027df3b333acd6e195e29e1af600f_m.jpg

1319 ms

5416750d84e9f878b1207a4666f85d86_m.jpg

5416750d84e9f878b1207a4666f85d86_m.jpg

1103 ms

9ac4847dbf288cc0bf04ccab7839a1c9.png

9ac4847dbf288cc0bf04ccab7839a1c9.png

1154 ms

advert.gif

advert.gif

85 ms

4ab28220724ea023af420b83e46f1bdf.png

4ab28220724ea023af420b83e46f1bdf.png

1176 ms

93061353441f0f2e5d0044651019e880.png

93061353441f0f2e5d0044651019e880.png

1176 ms

hram.png

hram.png

1194 ms

social-lj.png

social-lj.png

1242 ms

social-vk.png

social-vk.png

1184 ms

social-fb.png

social-fb.png

1217 ms

social-tw.png

social-tw.png

1201 ms

social-ok.png

social-ok.png

1192 ms

1

1

84 ms

jquery.counter-analog-i.png

jquery.counter-analog-i.png

1125 ms

31354.js

31354.js

121 ms

widget-ui-3.js

widget-ui-3.js

237 ms

Roboto:400,700,500,300,100&subset=cyrillic,latin

Roboto:400,700,500,300,100&subset=cyrillic,latin

118 ms

31354.css

31354.css

129 ms

119 ms

SEO Factors

linoleum.ru SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Linoleum.ru can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Linoleum.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

linoleum.ru

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