7.3 sec in total
513 ms
6.1 sec
681 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 513 ms and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
rio-leninskiy.ru performance score
name
value
score
weighting
Value3.9 s
26/100
10%
Value14.8 s
0/100
25%
Value12.7 s
3/100
10%
Value3,240 ms
2/100
30%
Value0
100/100
15%
Value15.6 s
6/100
10%
513 ms
632 ms
1554 ms
276 ms
383 ms
Our browser made a total of 142 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Rio-leninskiy.ru, 49% (69 requests) were made to Imageproxy.ru and 4% (6 requests) were made to Top-fwz1.mail.ru. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Imageproxy.ru.
Page size can be reduced by 932.1 kB (16%)
5.8 MB
4.9 MB
In fact, the total size of Rio-leninskiy.ru main page is 5.8 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. 70% of websites need less resources to load. Images take 4.6 MB which makes up the majority of the site volume.
Potential reduce by 436.5 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 68.6 kB, which is 13% 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 436.5 kB or 80% of the original size.
Potential reduce by 244.3 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 251.3 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 251.3 kB or 36% of the original size.
Number of requests can be reduced by 38 (28%)
135
97
The browser has sent 135 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 19 to 1 for JavaScripts and as a result speed up the page load time.
rio-leninskiy.ru
513 ms
632 ms
leninskiy
1554 ms
f65657bc81ecb8600a4403f3fed4d3c3-1693921273
276 ms
6edb3e039ddb9adad18c516ac35580f3-1674564618
383 ms
441b10941065fba82c806d6f101d45ab-1696513545
514 ms
intersection-observer.js
351 ms
lk.min.js
596 ms
firebase-app.js
184 ms
firebase-analytics.js
234 ms
firebase-auth.js
268 ms
firebase-firestore.js
325 ms
firebase-messaging.js
190 ms
10ff5f2bc8363fde78852f98f946fd61-1682321252
560 ms
loader.js
725 ms
axios.min.js
33 ms
tag.js
938 ms
code.js
794 ms
fbevents.js
21 ms
gtm.js
131 ms
65084b4a6cd53683702915.jpg
1312 ms
loader.svg
159 ms
pointer.svg
161 ms
catalog-card__phone.svg
160 ms
5c5a9ffb0fe00580160361.svg
157 ms
coworking-logo-black.svg
162 ms
worldclass-logo.svg
163 ms
arrow-down.svg
240 ms
footer-logo-1.svg
353 ms
footer-logo-2.svg
242 ms
map-bg-container.svg
372 ms
loopa-such-big.svg
261 ms
5c5aa040c8512713711129.svg
272 ms
5c5a9e338b850177637445.svg
344 ms
64afe0d8032e9344181516.jpg
1434 ms
62f0f86742a67839476126.jpg
1435 ms
63c005a733a5d155512893.jpg
1427 ms
62b09fb128657909915449.jpeg
1433 ms
62f0f86742a67839476126.jpg
1081 ms
63c005a733a5d155512893.jpg
1201 ms
62b09fb128657909915449.jpeg
1318 ms
64afe0d8032e9344181516.jpg
1420 ms
65e603eeb0f5a848881467.jpg
1450 ms
5c3de2948ab24199178567.png
1535 ms
5c13aa3de7302222873441.jpg
1539 ms
5c08d894742b9745955910.png
1545 ms
639cbd160e1e8094664660.jpg
1543 ms
60a66ec63cf2e479727141.png
1547 ms
66902011995da919094148.jpg
1571 ms
669020695d5e0048427430.png
1648 ms
5c4adf708cb0b160583995.jpg
1653 ms
5fc4b915c5c06666069600.png
1658 ms
65a829855a8ff497442165.jpg
1663 ms
5c08d7a39f2e9700759468.png
1660 ms
5c3f38f7a2efd473228766.jpg
1681 ms
654e73e680420147508325.png
1761 ms
5c3f449421ff9920979191.jpg
1767 ms
5c3de30338e76226422619.png
1772 ms
5c4adee2012cd944251932.jpg
1774 ms
5c658464c0656939630413.png
1781 ms
5c3f3f64acb1b923320266.jpg
1800 ms
5c3f0c7c9f3d5767081888.png
1875 ms
5c3f4018e1572072318419.jpg
1881 ms
5c3f10f259cd8035165941.png
1888 ms
5c3f402d38e96577828912.jpg
1890 ms
5c3f0e69e531f924585936.png
1899 ms
5e8208ba7d87d022525016.jpg
1920 ms
5cc1b16d94d46891452396.png
1988 ms
63514ac76af2d613423768.jpg
1995 ms
6409a220b6b43673917840.svg
420 ms
trc-work-time-bg.svg
334 ms
modal_close--hover.svg
336 ms
index-first-block-appearance.svg
398 ms
index-second-block-appearance.svg
408 ms
index-info-block-appearance--full.svg
453 ms
info-block-bg.svg
456 ms
index-third-block-appearance--left-extralarge.svg
456 ms
index-third-block-appearance--right.svg
512 ms
info-block--worldclass-appearance.svg
523 ms
cinemastar-appearance--bottom.svg
537 ms
seo-slider-appearance--top.svg
545 ms
subscribe-1.svg
570 ms
subscribe-2.svg
572 ms
market-subscribe-appearance.svg
626 ms
arrow-down--shevrone--bold.svg
638 ms
footer-appearance.svg
652 ms
modal-appearance-bottom.svg
674 ms
modal-appearance-top.svg
687 ms
current-trc-info__card-bg.svg
691 ms
popup-first-column-top-bg.svg
741 ms
popup-first-column-bottom-bg.svg
754 ms
popup-second-column-bg.svg
675 ms
Gilroy-Semibold.woff
662 ms
Gilroy-Bold.woff
743 ms
gilroymedium.woff
744 ms
gilroyregular.woff
901 ms
enpop.min.js
1063 ms
openapi.c340c125c61ec5745ebb2a98626e46ab.js
239 ms
rtrg
134 ms
sync-loader.js
993 ms
counter
135 ms
dyn-goal-config.js
347 ms
counter
467 ms
63514ac3437f1282573910.png
926 ms
advert.gif
550 ms
5c3f33c65b62e513923590.jpg
803 ms
5c3f1552f0f8b965139980.png
715 ms
enpop-main.min.js
240 ms
5c4ae0672a62a235319492.jpg
721 ms
5c3f095849922657727212.png
680 ms
5c462f2c59d29225187060.jpg
682 ms
5c4ae288757ce143036069.jpg
689 ms
631b3b8b70aaa802286906.png
690 ms
65c140f6b28db495732770.jpg
693 ms
65c1402235fd2531677318.png
713 ms
61767e06b3290730051109.jpg
685 ms
61767da1a3102206630565.png
687 ms
5c3f34e5e40fa507186618.jpg
693 ms
5c3f1f65a1f39413472488.png
694 ms
5c3f4a0f37a60039143443.jpg
711 ms
5c3f19b104e5d572993123.png
711 ms
5c4adf29e6c9b088963407.jpg
684 ms
5c3f1e9b9b589350094039.png
687 ms
5c3f497cd1773167699511.jpg
692 ms
649edb1a51eac271812418.png
692 ms
5f9806d2ccc3a173156975.jpg
713 ms
5c3f120413157042798212.png
721 ms
sync_cookie_image_decide
128 ms
63c7f2ed0eb42253350484.jpeg
685 ms
5c3f0b2f2af41642682312.png
686 ms
6698e7c71572a232523799.jpg
693 ms
669016c55b536146414815.png
692 ms
index-info-block-atm.jpg
713 ms
64afe0a4a4543028740944.jpg
720 ms
62b09fc6cc45a601798728.jpeg
685 ms
63c0058c596b1935298106.jpg
687 ms
62f0f703b4da2701223816.jpg
694 ms
index-info-block-worldclass.jpg
692 ms
64c259313816a621222457.jpg
831 ms
1
128 ms
tracker
130 ms
tracker
131 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.
ARIA tooltip elements do not have accessible names.
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
Page has valid source maps
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
RU
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), while the claimed language is Russian. 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 data is detected on the main page of Rio Leninskiy. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: