6.6 sec in total
681 ms
5.5 sec
387 ms
Welcome to robek.ru homepage info - get ready to check Robek best content for Russia right away, or after learning these important things about robek.ru
В обувном интернет-магазине «Робек» Вы сможете купить обувь онлайн по выгодным ценам с доставкой по всей России
Visit robek.ruWe analyzed Robek.ru page load time and found that the first response time was 681 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
robek.ru performance score
name
value
score
weighting
Value7.5 s
1/100
10%
Value15.2 s
0/100
25%
Value13.0 s
2/100
10%
Value1,180 ms
21/100
30%
Value0.823
4/100
15%
Value20.7 s
2/100
10%
681 ms
197 ms
350 ms
501 ms
665 ms
Our browser made a total of 154 requests to load all elements on the main page. We found that 92% of them (142 requests) were addressed to the original Robek.ru, 2% (3 requests) were made to Top-fwz1.mail.ru and 1% (2 requests) were made to Counter.yadro.ru. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Robek.ru.
Page size can be reduced by 127.2 kB (8%)
1.6 MB
1.4 MB
In fact, the total size of Robek.ru main page is 1.6 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. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 61.6 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 61.6 kB or 83% of the original size.
Potential reduce by 57.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. Robek images are well optimized though.
Potential reduce by 8.7 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 8.7 kB or 19% of the original size.
Number of requests can be reduced by 35 (23%)
150
115
The browser has sent 150 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Robek. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
robek.ru
681 ms
css.php
197 ms
css.php
350 ms
js.php
501 ms
js.php
665 ms
js.php
354 ms
js.php
359 ms
js.php
360 ms
js.php
515 ms
js.php
515 ms
css.php
523 ms
css.php
644 ms
css.php
655 ms
css.php
715 ms
share.js
302 ms
js.php
714 ms
js.php
715 ms
js.php
794 ms
js.php
807 ms
js.php
807 ms
bg.jpg
216 ms
bg-foot.png
214 ms
load.gif
214 ms
1457326796.png
238 ms
icon-enter.png
282 ms
fancybox_sprite.png
275 ms
icon-phone-big.png
333 ms
load.gif
335 ms
icon-basket-big.png
334 ms
glass80white.png
386 ms
icon-search-big.png
427 ms
%D0%91%D0%B5%D0%B7%20%D0%B8%D0%BC%D0%B5%D0%BD%D0%B8-1.jpg
1038 ms
29+.jpg
1645 ms
30.jpg
1339 ms
slider.png
497 ms
img-delivery.png
534 ms
img-pickup.png
581 ms
img-money.png
658 ms
img-warranty.png
682 ms
1393397721.png
735 ms
1393397721.png
819 ms
1393400289.png
842 ms
1393400289.png
890 ms
1393400301.png
979 ms
1393400301.png
990 ms
1393400312.png
1043 ms
1393400312.png
1140 ms
1393401291.png
1137 ms
1393401291.png
1187 ms
1393401308.png
1197 ms
1393401308.png
1301 ms
1393401313.png
1305 ms
hit
258 ms
1393401313.png
1315 ms
watch.js
5 ms
RMWRoO87w6
189 ms
code.js
338 ms
ga.js
16 ms
__utm.gif
25 ms
1393401319.png
1263 ms
collect
130 ms
1393401319.png
1259 ms
1393401339.png
1272 ms
1393401339.png
1293 ms
1393401344.png
1282 ms
1393401344.png
1298 ms
widget_ru_RU.js
198 ms
1393402048.png
1370 ms
1393402048.png
1365 ms
1393402064.png
1366 ms
hit
129 ms
1393402064.png
1337 ms
1393402071.png
1332 ms
1393402071.png
1421 ms
counter
159 ms
1393402077.png
1416 ms
1393402077.png
1376 ms
1393402083.png
1300 ms
1393402083.png
1286 ms
1393402092.png
1252 ms
1393402092.png
1247 ms
1393402102.png
1267 ms
1393402102.png
1220 ms
1393402112.png
1148 ms
1393402112.png
1129 ms
1393402125.png
1104 ms
1393402125.png
1072 ms
1393402132.png
1121 ms
1393402132.png
1077 ms
1393402145.png
1086 ms
1393402145.png
990 ms
1393402153.png
1017 ms
1393402153.png
1015 ms
1393402162.png
1064 ms
1393402162.png
977 ms
1393402169.png
972 ms
1393402169.png
953 ms
1393402176.png
984 ms
1393402176.png
999 ms
1393402200.png
962 ms
1393402200.png
970 ms
1393402209.png
946 ms
1393402209.png
948 ms
1393402295.png
980 ms
1393402295.png
899 ms
1393402304.png
933 ms
1393402304.png
952 ms
1393402312.png
962 ms
1393402312.png
946 ms
1393402324.png
991 ms
1393402324.png
905 ms
1393402339.png
923 ms
1393402339.png
949 ms
1393402344.png
965 ms
1393402344.png
954 ms
1393402351.png
987 ms
1393402351.png
902 ms
1393402357.png
922 ms
1393402357.png
947 ms
1393402363.png
960 ms
1393402363.png
961 ms
1393402370.png
958 ms
1393402370.png
932 ms
1393402378.png
911 ms
1393402378.png
939 ms
1393402385.png
959 ms
1393402385.png
964 ms
1393402398.png
946 ms
1393402398.png
950 ms
1393402415.png
910 ms
1393402415.png
947 ms
1393402429.png
973 ms
1393402429.png
970 ms
1393402510.png
933 ms
1393402510.png
970 ms
1441023862.jpg
911 ms
1441023862.jpg
944 ms
%D0%BF%D0%B5%D1%80%D0%B2%D0%BE%D1%83%D1%80,%20%D0%B2%D0%B0%D1%82%D1%83%D1%82%D0%B8%D0%BD.jpg
1497 ms
0.jpg
959 ms
0.jpg
930 ms
0.jpg
984 ms
0.jpg
914 ms
0.jpg
945 ms
0.jpg
954 ms
break.gif
971 ms
arrow.png
984 ms
icons.png
996 ms
logo.png
973 ms
opinion.png
961 ms
bx_loader.gif
979 ms
pagination.png
1021 ms
pagination_arrow.png
1015 ms
carousel.png
1035 ms
tracker
164 ms
robek.ru accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
robek.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
robek.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Document uses legible font sizes
Tap targets are not sized appropriately
RU
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Robek.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 Robek.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.
robek.ru
Open Graph description is not detected on the main page of Robek. 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: