13.9 sec in total
817 ms
12.3 sec
844 ms
Welcome to rio-leninskiy.ru homepage info - get ready to check Rio Leninskiy best content for Russia right away, or after learning these important things about rio-leninskiy.ru
ТРЦ «РИО» Ленинский предлагает своим гостям высокое качество обслуживания, а также большой выбор товаров и услуг. Торговый центр расположен по адресу: Москва, Ленинский проспект, 109.
Visit rio-leninskiy.ruWe analyzed Rio-leninskiy.ru page load time and found that the first response time was 817 ms and then it took 13.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
rio-leninskiy.ru performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value7.0 s
6/100
25%
Value45.2 s
0/100
10%
Value63,750 ms
0/100
30%
Value0
100/100
15%
Value97.4 s
0/100
10%
817 ms
1002 ms
276 ms
274 ms
2714 ms
Our browser made a total of 113 requests to load all elements on the main page. We found that 55% of them (62 requests) were addressed to the original Rio-leninskiy.ru, 11% (12 requests) were made to Vk.com and 4% (5 requests) were made to Scontent.cdninstagram.com. The less responsive or slowest element that took the longest time to load (8.8 sec) belongs to the original domain Rio-leninskiy.ru.
Page size can be reduced by 1.0 MB (15%)
6.9 MB
5.9 MB
In fact, the total size of Rio-leninskiy.ru main page is 6.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 5.7 MB which makes up the majority of the site volume.
Potential reduce by 169.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 169.4 kB or 66% of the original size.
Potential reduce by 150.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. Rio Leninskiy images are well optimized though.
Potential reduce by 522.4 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 522.4 kB or 74% of the original size.
Potential reduce by 197.9 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. Rio-leninskiy.ru needs all CSS files to be minified and compressed as it can save up to 197.9 kB or 81% of the original size.
Number of requests can be reduced by 33 (30%)
109
76
The browser has sent 109 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rio Leninskiy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
rio-leninskiy.ru
817 ms
kernel_main.css
1002 ms
page_dffab4f6c3907171feeebff48028e127.css
276 ms
template_79bf04a518ddea5eaa17486966bbf5c4.css
274 ms
kernel_main.js
2714 ms
template_2a71cb54bc312a965d4798da944cca0c.js
456 ms
fonts.css
282 ms
jquery.fancybox.css
452 ms
style.css
1146 ms
responsive.css
884 ms
jquery.bxslider.css
590 ms
jquery.modal.css
729 ms
font-awesome.min.css
1008 ms
jquery.min.js
104 ms
html5shiv.js
868 ms
jquery.bxslider.min.js
1161 ms
jquery.jcarousel.js
1528 ms
jquery.fancybox.js
1705 ms
main.js
1283 ms
jquery.modal.edited.js
1296 ms
velocity.js
1649 ms
owl.carousel.css
1456 ms
owl.theme.css
1495 ms
owl.carousel.js
1732 ms
openapi.js
388 ms
instafeed.min.js
1514 ms
ba.js
213 ms
11259054_1008438482570762_525186100_a.jpg
651 ms
vk.png
155 ms
fb.png
157 ms
inst.png
158 ms
info.png
157 ms
f21c2bf5bcc225a834a9411045a0079e.png
7153 ms
42f66fb2b218554b35b287901140f08f.png
3435 ms
59dea68561dbb980cb1d468f4b5391d9.png
8784 ms
8cb8fa8b9723526b164514103b3895cc.png
3971 ms
8f05eef83ad74aa08123c1369b3f3ab2.jpg
1510 ms
a034e54471673d192082c30c6b0bd372.jpg
1027 ms
1131ebe9e82e31ea774b76e01d92706b.jpg
2182 ms
16ff603b03cc0d6d9b9515d0bed5ce81.jpg
3431 ms
1ff3c7496733d96c8d3896acc016413a.png
2956 ms
5978093e79e4db234c4282fd20463ac0.png
5571 ms
5d98f36209fcbbd858eb825615dceee8.png
4303 ms
568fb1c83b27b64cf344665f7614fe2c.png
8618 ms
6abd40e20a1df839b472d54a3548f0ed.jpeg
7141 ms
cff36a5501b3200c22b7d3d0cc9e8b34.png
6123 ms
097865490f53b2691e664285dc7b39ed.jpeg
6227 ms
40dcca0f7b3a96a878c7ff229270a502.jpeg
7697 ms
e23a16346e5b2f030f19958bf669a349.jpeg
6708 ms
a471dd0ec6233f732d53e237babb342b.jpeg
7155 ms
subs_img.png
8425 ms
rio_logo_footer.svg
7318 ms
appstore.png
7327 ms
gplay.png
7528 ms
rio-animate-logo.png
7838 ms
search_icon.png
7668 ms
NeoSansProRegular.woff
8500 ms
NeoSansProBold.woff
8009 ms
icon-search-clear.png
7984 ms
menu_control.png
8142 ms
prev.png
8152 ms
next.png
8299 ms
sdk.js
221 ms
small_prev.png
8242 ms
small_next.png
8369 ms
upload.gif
155 ms
widget_community.php
341 ms
recent
326 ms
btn_bg.png
8309 ms
bx_stat
278 ms
dev.svg
8367 ms
288 ms
xd_arbiter.php
209 ms
xd_arbiter.php
494 ms
12907417_1604014586518636_1124578436_n.jpg
440 ms
12918560_1008627632563547_1774937967_n.jpg
576 ms
12479644_1769329356619526_52073269_n.jpg
698 ms
12141857_1670918013168465_1066060557_n.jpg
770 ms
12599467_659044477566774_2099669024_n.jpg
700 ms
loader_nav19239_3.js
175 ms
lite.css
216 ms
lite.js
606 ms
lang3_0.js
355 ms
widget_community.css
355 ms
xdm.js
355 ms
al_community.js
365 ms
9RWX2bzxLeg.jpg
272 ms
0DKzeZAC-YQ.jpg
393 ms
I_RZgbM2HxU.jpg
398 ms
ykdZYJN2_lM.jpg
389 ms
3sCI8RABo5c.jpg
391 ms
LbdpWqUwRDU.jpg
405 ms
UNZRccwwSRU.jpg
391 ms
sx9GlWV9kKU.jpg
393 ms
FDiJ7h2QiPA.jpg
415 ms
e_c68b8287.jpg
389 ms
uBgBrLx_ys8.jpg
257 ms
yYgeMk9xsKM.jpg
403 ms
1UbH69uIQfw.jpg
263 ms
ZRMfHMpBHeI.jpg
452 ms
e_aa900286.jpg
392 ms
ZUeYUlb-e8c.jpg
392 ms
8vlP4Eu3kbI.jpg
383 ms
e_67e22d74.jpg
382 ms
vjQsNtH_-X8.jpg
388 ms
YD13UwbeXfs.jpg
388 ms
-BR5tzxHgK0.jpg
392 ms
lEpCZDbGwm0.jpg
406 ms
By2qassqoPY.jpg
392 ms
WZSaEzLA3Mg.jpg
500 ms
3w-8uwd0-Wk.jpg
505 ms
camera_50.png
130 ms
w_logo.png
143 ms
rio-leninskiy.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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
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.
rio-leninskiy.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
Missing source maps for large first-party JavaScript
rio-leninskiy.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
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 doesn't use legible font sizes
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rio-leninskiy.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 Rio-leninskiy.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.
rio-leninskiy.ru
Open Graph description is not detected on the main page of Rio Leninskiy. 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: