6.3 sec in total
541 ms
5.6 sec
160 ms
Click here to check amazing Rusrezina content for Russia. Otherwise, check out these important facts you probably never knew about rusrezina.ru
Официальный сайт завода РТИ "Русская Резина". Изготовление резинотехнических изделий широкого спектра по низким ценам.
Visit rusrezina.ruWe analyzed Rusrezina.ru page load time and found that the first response time was 541 ms and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
rusrezina.ru performance score
name
value
score
weighting
Value7.3 s
1/100
10%
Value18.1 s
0/100
25%
Value13.2 s
2/100
10%
Value1,770 ms
10/100
30%
Value0.04
99/100
15%
Value17.5 s
4/100
10%
541 ms
585 ms
466 ms
1176 ms
32 ms
Our browser made a total of 104 requests to load all elements on the main page. We found that 81% of them (84 requests) were addressed to the original Rusrezina.ru, 4% (4 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Rusrezina.ru.
Page size can be reduced by 1.9 MB (51%)
3.7 MB
1.9 MB
In fact, the total size of Rusrezina.ru main page is 3.7 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. 65% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 85.9 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. This page needs HTML code to be minified as it can gain 28.4 kB, which is 27% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 85.9 kB or 81% of the original size.
Potential reduce by 1.3 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. Obviously, Rusrezina needs image optimization as it can save up to 1.3 MB or 61% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 464.5 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 464.5 kB or 33% of the original size.
Potential reduce by 11.3 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. Rusrezina.ru needs all CSS files to be minified and compressed as it can save up to 11.3 kB or 20% of the original size.
Number of requests can be reduced by 65 (72%)
90
25
The browser has sent 90 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rusrezina. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 29 to 1 for CSS and as a result speed up the page load time.
rusrezina.ru
541 ms
rusrezina.ru
585 ms
www.rusrezina.ru
466 ms
www.rusrezina.ru
1176 ms
font-awesome.min.css
32 ms
style.css
134 ms
index_goods_slider.css
267 ms
owl.carousel.css
401 ms
reset.css
401 ms
jquery.mCustomScrollbar.min.css
402 ms
owl.carousel.css
404 ms
owl.carousel.theme.css
404 ms
main.css
407 ms
bootstrap-grid.css
533 ms
main.css
532 ms
login.css
535 ms
jquery-ui.css
534 ms
style_ext.css
536 ms
menu_3.css
537 ms
jquery.mCustomScrollbar.min.css
671 ms
menu_style.css
676 ms
jquery.fancybox.min.css
673 ms
style.css
674 ms
style.css
676 ms
style.css
671 ms
style.css
803 ms
style.css
803 ms
style.css
803 ms
template_styles.css
804 ms
core.js
1210 ms
protobuf.js
1095 ms
model.js
936 ms
core_promise.js
935 ms
rest.client.js
935 ms
pull.client.js
1072 ms
jquery.min.js
30 ms
jquery-ui.min.js
1337 ms
jquery.mCustomScrollbar.concat.min.js
1070 ms
owl.carousel.js
1206 ms
jquery.inputmask.js
1233 ms
jquery.inputmask.extensions.js
1206 ms
api.js
47 ms
adsbygoogle.js
171 ms
index_slider.css
1229 ms
owl.carousel.css
1247 ms
owl.transitions.css
1113 ms
jquery.inputmask.date.extensions.js
980 ms
jquery.inputmask.numeric.extensions.js
981 ms
jquery.zoom.min.js
979 ms
lib.js
1078 ms
menu_5.js
1078 ms
css
29 ms
jquery.menu-aim.js
1074 ms
jquery.mCustomScrollbar.min.js
952 ms
jquery.mousewheel.min.js
949 ms
menu_script.js
980 ms
jquery.fancybox.min.js
1081 ms
script.js
1079 ms
script.js
1077 ms
script.js
947 ms
script.js
948 ms
script.js
971 ms
script.js
1072 ms
script.js
1072 ms
owl.carousel.js
1074 ms
owl.carousel.js
1043 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4kaVQ.woff
17 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4kaVQ.woff
48 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4kaVQ.woff
25 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4kaVQ.woff
26 ms
ba.js
405 ms
spread.php
215 ms
recaptcha__en.js
157 ms
3_1_FFFFFFFF_EFEFEFFF_0_pageviews
732 ms
logo.png
211 ms
whatsapp.svg
213 ms
icon_search.png
212 ms
logo_mini.png
210 ms
5r416uhfrjc2e4xf6rc3t74pqdbl12aw.jpg
881 ms
cg7d60g0xivcam3yjdtsqalkgb9gek14.jpg
614 ms
e42f02c967725362fbc3a352fe72d9dd.jpg
477 ms
ffhsrhloqtpovldrk39jjs3v2k052amq.jpg
380 ms
90a6cc28d7d7f6f63f562fd1899fb21a.jpg
611 ms
c225275beedf0222ae6cf8c01f8ab657.jpg
381 ms
93dfe4f325b8abc2cc5b6a115d6401a8.jpg
615 ms
ca20079dd2276dc168bf0386ffe8a160.jpg
481 ms
9c97d025d391efe8a69dc1d1d8d343b1.jpg
743 ms
ca87d6a49dace75dc85fe57f7f2bfb28.jpg
616 ms
a2dfcf9c6ef941d911c638a71485d153.jpg
747 ms
e4422a425b8bfb4bdf18cfc5d342323e.jpg
745 ms
icon_down_1c.svg
745 ms
show_ads_impl.js
274 ms
fontawesome-webfont.woff
60 ms
rouble-webfont.woff
719 ms
slider_arrows.png
794 ms
ico_download.png
795 ms
tag.js
899 ms
arrow_success.png
793 ms
init
836 ms
IadKIBmGw9
108 ms
spread.php
136 ms
zrt_lookup.html
50 ms
ads
41 ms
bx_stat
186 ms
rusrezina.ru accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
rusrezina.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
rusrezina.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
![]()
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rusrezina.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 Rusrezina.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.
rusrezina.ru
Open Graph description is not detected on the main page of Rusrezina. 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: