8.5 sec in total
1.3 sec
6.5 sec
802 ms
Click here to check amazing Restoran content for Russia. Otherwise, check out these important facts you probably never knew about restoran.ru
Рестораны Москвы предлагают своим гостям всю возможную палитру гастрономических красок: от невероятно широкого разнообразия кухонь, как национальных или региона...
Visit restoran.ruWe analyzed Restoran.ru page load time and found that the first response time was 1.3 sec and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
restoran.ru performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value5.4 s
20/100
25%
Value6.3 s
41/100
10%
Value3,330 ms
2/100
30%
Value0.005
100/100
15%
Value12.2 s
15/100
10%
1286 ms
143 ms
283 ms
533 ms
396 ms
Our browser made a total of 138 requests to load all elements on the main page. We found that 93% of them (128 requests) were addressed to the original Restoran.ru, 4% (5 requests) were made to Top-fwz1.mail.ru and 1% (2 requests) were made to Mc.yandex.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Restoran.ru.
Page size can be reduced by 177.6 kB (13%)
1.4 MB
1.2 MB
In fact, the total size of Restoran.ru main page is 1.4 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. 60% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 69.3 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 69.3 kB or 82% of the original size.
Potential reduce by 106.9 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. Restoran images are well optimized though.
Potential reduce by 1.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. This website has mostly compressed JavaScripts.
Potential reduce by 19 B
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. Restoran.ru has all CSS files already compressed.
Number of requests can be reduced by 60 (46%)
130
70
The browser has sent 130 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Restoran. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
www.restoran.ru
1286 ms
datepicker.min.css
143 ms
discount-list.css
283 ms
styles.css
533 ms
index-page.css
396 ms
afisha-list.css
422 ms
where-to-go.css
422 ms
right-filter.css
424 ms
group-19.svg
434 ms
group-_8_.svg
524 ms
veranda_round.svg
674 ms
weedin_round_2.svg
679 ms
birthday_round.svg
682 ms
group-_9_.svg
685 ms
group-_3_.svg
690 ms
logo-open-style-deep-corn-r-only.svg
689 ms
395007781.jpg
974 ms
20.jpg
839 ms
kozuki-oden.jpg
839 ms
shutterstock_247666594.jpg
1736 ms
pasha_420_3.jpg
1470 ms
svadna.jpg
948 ms
shutterstock_158770853.jpg
2098 ms
restoran.jpg
1118 ms
scale_1200.jpg
1208 ms
sav040_1024x683.jpg
1251 ms
htmlimage_10_.jpg
1397 ms
restorany-u-naberezhnoi_-big.jpg
1467 ms
20.jpg
1670 ms
266874572.jpg
1677 ms
karnaval-ulitok1.jpg
1728 ms
kozuki-oden.jpg
1598 ms
395007781.jpg
1729 ms
master-i-margarita_balzi-rossi.jpg
1809 ms
krevetki-s-sousom-ayoli1.jpg
1817 ms
e8c18c60907b6e35dff9917854476035.jpg
1858 ms
js
56 ms
jquery-3.7.1.min.js
1860 ms
passive-fixes.min.js
1747 ms
jquery.validate.min.js
1676 ms
datepicker.min.js
1570 ms
_jquery.autocomplete.min.js
1575 ms
util.min.js
1580 ms
popper2020.min.js
1609 ms
tab.min.js
1658 ms
tooltip.min.js
1578 ms
modal.min.js
1446 ms
dropdown.min.js
1449 ms
slick-1-8-1.min.js
1492 ms
bootstrap-multiselect.min.js
1546 ms
index.min.js
1555 ms
push-worker-init.js
1552 ms
script.min.js
1561 ms
counter2
126 ms
script.min.js
1421 ms
script.min.js
1480 ms
script.min.js
1424 ms
script.min.js
1408 ms
OpenSans-Light.woff
1409 ms
OpenSans-Regular.woff
1435 ms
OpenSans-SemiBold.woff
1274 ms
OpenSans-Bold.woff
1210 ms
PTSerif-Regular.woff
1320 ms
PTSerif-Bold.woff
1196 ms
icomoon.ttf
1065 ms
241ca2df1993809321ce4e65095241ff.jpeg
994 ms
1abbd776f4584686d17c52b3ee9e6c30.jpeg
1075 ms
810237945305f1814c8d7adb7dc5b918.jpeg
1049 ms
a82c2b1311edd1869ae6f96e99c40e9d.jpeg
1054 ms
c4b66e56eb2bf73a389b9df2204801a7.jpeg
1091 ms
cfb9dd64f233b8fcf40b3a6911b7198f.jpg
1016 ms
1cd3624e341ba79f6db4de9b9a6dcb99.jpg
1080 ms
logo-open-style-white--corn.svg
1050 ms
qr-code-restoran-app-link--small.png
1038 ms
footer-app-link-logo.svg
1049 ms
footer-app-link-logo-playmarket.svg
993 ms
list-location-logo--red.svg
985 ms
arrow.svg
1053 ms
logo-open-style--corn.svg
1045 ms
loop.svg
1019 ms
close-black.svg
977 ms
watch-on-map--corn.svg
986 ms
near-special--corn.svg
986 ms
fly-filter-trigger.svg
1050 ms
266874572.jpg
1350 ms
watch-eye.svg
1005 ms
news-comments-white.svg
974 ms
watch-eye-white.svg
1036 ms
watch-eye-silver.svg
1037 ms
news-comments.svg
1050 ms
review-like-icon-blue.svg
1050 ms
review-like-icon-red.svg
1028 ms
filter-trigger-logo.svg
994 ms
tag.js
831 ms
code.js
250 ms
map-trigger-logo.svg
951 ms
left-menu-arrow--corn.svg
906 ms
close-white.svg
904 ms
favorite-icon--red-active.svg
870 ms
sync-loader.js
975 ms
counter
126 ms
dyn-goal-config.js
249 ms
watch-eye--red.svg
841 ms
vk-icon.svg
841 ms
tg-icon--round-gradient.svg
898 ms
trend-logo.svg
901 ms
explore-empty-icon.svg
872 ms
easter-spec-icon--blue.svg
849 ms
post-spec-icon.svg
858 ms
veranda-spec-icon.svg
844 ms
wedding-spec-icon.svg
866 ms
birthday-menu-icon.svg
876 ms
breakfast-2024-shadow-3.svg
871 ms
brunch.svg
853 ms
left-icon-new-place.svg
869 ms
left-menu-book-icon.svg
857 ms
left-menu-arrow.svg
878 ms
discount-icon.svg
887 ms
left-menu-afisha-icon--corn.svg
866 ms
left-menu-reviews-icon--corn.svg
870 ms
ratings-menu-icon.svg
878 ms
left-menu-section-logo.svg
858 ms
left-menu-people-icon.svg
870 ms
left-icon-catering_car.svg
878 ms
user-add-black.svg
874 ms
mail--red.svg
881 ms
left-menu-arrow-thin--corn.svg
857 ms
to-top-btn-bg.png
788 ms
close-red.svg
803 ms
advert.gif
568 ms
395007781.jpg
1184 ms
20.jpg
1154 ms
kozuki-oden.jpg
1002 ms
karnaval-ulitok1.jpg
1120 ms
master-i-margarita_balzi-rossi.jpg
1119 ms
krevetki-s-sousom-ayoli1.jpg
912 ms
1
146 ms
tracker
127 ms
restoran.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.
restoran.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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
restoran.ru SEO score
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
RU
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Restoran.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 Restoran.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.
restoran.ru
Open Graph description is not detected on the main page of Restoran. 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: