4.1 sec in total
874 ms
3.1 sec
180 ms
Welcome to r17.ru homepage info - get ready to check R 17 best content for Russia right away, or after learning these important things about r17.ru
Продажа шин и дисков в г. Москва, шиномонтаж, сезонное хранение шин, доставка и самовывоз.
Visit r17.ruWe analyzed R17.ru page load time and found that the first response time was 874 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
r17.ru performance score
name
value
score
weighting
Value1.7 s
92/100
10%
Value3.6 s
60/100
25%
Value6.5 s
39/100
10%
Value4,360 ms
1/100
30%
Value0.008
100/100
15%
Value12.1 s
16/100
10%
874 ms
174 ms
322 ms
327 ms
323 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 89% of them (66 requests) were addressed to the original R17.ru, 8% (6 requests) were made to Mc.yandex.ru and 1% (1 request) were made to Maps.google.ru. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain R17.ru.
Page size can be reduced by 277.1 kB (49%)
564.0 kB
286.9 kB
In fact, the total size of R17.ru main page is 564.0 kB. 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 261.8 kB which makes up the majority of the site volume.
Potential reduce by 37.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. 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 37.7 kB or 80% of the original size.
Potential reduce by 58.6 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, R 17 needs image optimization as it can save up to 58.6 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 150.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 150.9 kB or 69% of the original size.
Potential reduce by 30.0 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. R17.ru needs all CSS files to be minified and compressed as it can save up to 30.0 kB or 83% of the original size.
Number of requests can be reduced by 20 (29%)
70
50
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of R 17. 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 5 to 1 for CSS and as a result speed up the page load time.
r17.ru
874 ms
mootools.js
174 ms
caption.js
322 ms
template_css.css
327 ms
ja-vm.css
323 ms
ja-news.css
336 ms
mootools.v1.1.js
330 ms
ja.script.js
338 ms
jquery-1.3.1.min.js
645 ms
jquery.maskedinput-1.2.2.js
483 ms
script.js
485 ms
ja.splitmenu.css
485 ms
default.css
485 ms
staticmap
375 ms
shadow-right.gif
375 ms
shadow-left.gif
375 ms
header-bg.gif
375 ms
logo.gif
375 ms
phone.png
377 ms
vm-cart-bg.gif
376 ms
button-viewcart.gif
380 ms
mainnav-bg.gif
380 ms
bullet-list.gif
381 ms
mainnav-sep.gif
381 ms
image3.phtml
382 ms
image3.phtml
381 ms
image3.phtml
481 ms
image3.phtml
490 ms
image3.phtml
487 ms
image3.phtml
482 ms
image3.phtml
492 ms
image3.phtml
507 ms
image3.phtml
646 ms
image3.phtml
647 ms
image3.phtml
648 ms
image3.phtml
655 ms
image3.phtml
674 ms
image3.phtml
672 ms
image3.phtml
809 ms
image3.phtml
811 ms
image3.phtml
813 ms
image3.phtml
847 ms
image3.phtml
848 ms
image3.phtml
848 ms
image3.phtml
973 ms
image3.phtml
975 ms
image3.phtml
978 ms
image3.phtml
982 ms
image3.phtml
1024 ms
hit
361 ms
watch.js
359 ms
image3.phtml
655 ms
image3.phtml
768 ms
image3.phtml
770 ms
image3.phtml
772 ms
image3.phtml
776 ms
image3.phtml
821 ms
watch.js
443 ms
image3.phtml
816 ms
image3.phtml
947 ms
image3.phtml
930 ms
image3.phtml
932 ms
image3.phtml
933 ms
image3.phtml
977 ms
image3.phtml
979 ms
image3.phtml
991 ms
dot.gif
984 ms
footer-right.gif
984 ms
footer-left.gif
994 ms
top.gif
1024 ms
advert.gif
85 ms
1
86 ms
25910300
86 ms
29655155
118 ms
r17.ru accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
button, link, and menuitem elements do not have accessible names.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
r17.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Browser errors were logged to the console
r17.ru SEO score
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
RU
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise R17.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 R17.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.
r17.ru
Open Graph description is not detected on the main page of R 17. 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: