Tools & Wizards About Us
riocatalog.ru screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

riocatalog.ru

Page Load Speed

5.9 sec in total

First Response

623 ms

Resources Loaded

4.6 sec

Page Rendered

630 ms

riocatalog.ru screenshot

About Website

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

Журнал "Каталог качества "РИО" - Рекламно-Информационное Обозрение рынка товаров и услуг для дома и офиса

Visit riocatalog.ru

Key Findings

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

riocatalog.ru performance score

0

Network Requests Diagram

riocatalog.ru

623 ms

it.css

158 ms

rio_screen.css

301 ms

default.css

294 ms

jquery.js

525 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 71% of them (45 requests) were addressed to the original Riocatalog.ru, 5% (3 requests) were made to Vk.com and 5% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Riocatalog.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 196.9 kB (14%)

Content Size

1.4 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-83%

Potential reduce by 105.8 kB

  • Original 127.2 kB
  • After minification 115.2 kB
  • After compression 21.4 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 105.8 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 2.3 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. Riocatalog images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 63.4 kB

  • Original 96.3 kB
  • After minification 93.7 kB
  • After compression 32.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 63.4 kB or 66% of the original size.

CSS Optimization

-76%

Potential reduce by 25.4 kB

  • Original 33.2 kB
  • After minification 26.3 kB
  • After compression 7.8 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. Riocatalog.ru needs all CSS files to be minified and compressed as it can save up to 25.4 kB or 76% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (45%)

Requests Now

60

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

riocatalog.ru

riocatalog.ru

623 ms

it.css

it.css

158 ms

rio_screen.css

rio_screen.css

301 ms

default.css

default.css

294 ms

jquery.js

jquery.js

525 ms

mobilyslider.js

mobilyslider.js

1353 ms

init.js

init.js

302 ms

jquery.fancybox.css

jquery.fancybox.css

363 ms

jquery.fancybox-buttons.css

jquery.fancybox-buttons.css

444 ms

share.js

share.js

292 ms

top100.jcn

top100.jcn

439 ms

watch.js

watch.js

1 ms

rio2.png

rio2.png

145 ms

slogan.png

slogan.png

153 ms

bg_icon.gif

bg_icon.gif

142 ms

GARAGE.jpg

GARAGE.jpg

702 ms

PLACES.jpg

PLACES.jpg

908 ms

SCIENCE.jpg

SCIENCE.jpg

593 ms

zagorodom_15_200x250-exib.gif

zagorodom_15_200x250-exib.gif

561 ms

1005.jpg

1005.jpg

484 ms

1004.jpg

1004.jpg

481 ms

1003.jpg

1003.jpg

766 ms

1002.jpg

1002.jpg

907 ms

1001.jpg

1001.jpg

848 ms

1000.jpg

1000.jpg

762 ms

999.jpg

999.jpg

850 ms

998.jpg

998.jpg

909 ms

997.jpg

997.jpg

1072 ms

996.jpg

996.jpg

1011 ms

995.jpg

995.jpg

1194 ms

994.jpg

994.jpg

1064 ms

993.jpg

993.jpg

1230 ms

rio_001.p1.pdf.r150.jpg

rio_001.p1.pdf.r150.jpg

1893 ms

astok.gif

astok.gif

1192 ms

itstudio.gif

itstudio.gif

1237 ms

share.php

share.php

148 ms

share_logo.png

share_logo.png

263 ms

widgets.js

widgets.js

30 ms

ico_mail.gif

ico_mail.gif

1209 ms

ico_map.gif

ico_map.gif

1286 ms

ico_home.gif

ico_home.gif

1286 ms

bg_gradient.gif

bg_gradient.gif

1355 ms

bg.png

bg.png

1348 ms

bg_menu.gif

bg_menu.gif

1363 ms

arrow_red.gif

arrow_red.gif

1514 ms

separator.gif

separator.gif

1512 ms

context.js

context.js

244 ms

context_static_r1084.js

context_static_r1084.js

386 ms

57004

57004

721 ms

y90

y90

222 ms

masmeb.ru

masmeb.ru

311 ms

label_green.jpg

label_green.jpg

165 ms

hit

hit

271 ms

top100.scn

top100.scn

132 ms

bg_bottom.gif

bg_bottom.gif

142 ms

button.71000885400e222c3c0eec823f8f93f0.js

button.71000885400e222c3c0eec823f8f93f0.js

112 ms

bullets.png

bullets.png

140 ms

prev_next.png

prev_next.png

139 ms

tweet_button.fd774b599f565016d763dd860cb31c79.en.html

tweet_button.fd774b599f565016d763dd860cb31c79.en.html

34 ms

hit

hit

141 ms

jot

jot

205 ms

rio_print.css

rio_print.css

167 ms

hotlog_redirects

hotlog_redirects

212 ms

SEO Factors

riocatalog.ru SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    WINDOWS-1251

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

riocatalog.ru

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