15.3 sec in total
3.1 sec
9.3 sec
2.9 sec
Click here to check amazing Resto content for Russia. Otherwise, check out these important facts you probably never knew about resto.ru
RESTO.RU - поисковая система для гурманов: рестораны, кафе, бары Москвы на карте, адреса и меню лучших ресторанов и кафе
Visit resto.ruWe analyzed Resto.ru page load time and found that the first response time was 3.1 sec and then it took 12.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
resto.ru performance score
name
value
score
weighting
Value3.3 s
40/100
10%
Value14.8 s
0/100
25%
Value9.4 s
12/100
10%
Value6,260 ms
0/100
30%
Value0.139
79/100
15%
Value12.0 s
16/100
10%
3116 ms
383 ms
17 ms
381 ms
413 ms
Our browser made a total of 185 requests to load all elements on the main page. We found that 19% of them (36 requests) were addressed to the original Resto.ru, 10% (19 requests) were made to Assets.resto.ru and 8% (14 requests) were made to Content.adriver.ru. The less responsive or slowest element that took the longest time to load (4.3 sec) relates to the external source Assets2.resto.ru.
Page size can be reduced by 1.6 MB (24%)
6.6 MB
5.0 MB
In fact, the total size of Resto.ru main page is 6.6 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.7 MB which makes up the majority of the site volume.
Potential reduce by 353.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 353.4 kB or 76% of the original size.
Potential reduce by 184.2 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. Resto images are well optimized though.
Potential reduce by 499.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 499.9 kB or 70% of the original size.
Potential reduce by 531.5 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. Resto.ru needs all CSS files to be minified and compressed as it can save up to 531.5 kB or 81% of the original size.
Number of requests can be reduced by 73 (43%)
170
97
The browser has sent 170 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Resto. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 55 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
resto.ru
3116 ms
application-9d1ba7f2e1ffa1f3c6794d077e81ed32.css
383 ms
share.js
17 ms
381 ms
openapi.js
413 ms
application-c73d2b3716fa6e793dc6ec05d03ecde0.js
1041 ms
watch.js
1 ms
openapi.js
606 ms
top100.jcn
471 ms
709 ms
combine.xml
1227 ms
autoUpdate.adriver.js
909 ms
fbds.js
184 ms
sdk.js
930 ms
ga.js
29 ms
Circle-Regular-b70c361b6a77f494b0daf62762e721f5.woff
951 ms
download_app_store_badge_ru.png
1320 ms
android_app_on_play_logo_large.png
107 ms
feed_content__98A7741.jpg
1875 ms
IMG_0907.jpg
4349 ms
zal524.png
1953 ms
thumb_01135.jpg
1277 ms
feed_WN_kWF6iPZnOeCEcnIDw7HUM2p1b0wtqFQxYit7D9cU_eARDB_dvMWEJRJQfssM8blRkThW6-xCJ8WG7imM6TpE.jpg
1317 ms
407f.jpg
1318 ms
7893.jpg
1656 ms
457d.jpg
2293 ms
24b3.jpg
1509 ms
1fd0.jpg
1667 ms
08bd.jpg
2036 ms
1cb6.jpg
1761 ms
cd44.jpg
1948 ms
f0ea.jpg
2127 ms
a862.jpg
2936 ms
2867.jpg
2177 ms
607e.jpg
2371 ms
0326.jpg
2734 ms
3658.jpg
2530 ms
e912.jpg
2583 ms
567e.jpg
2704 ms
5b68.jpg
3078 ms
thumb_default-7c316a5b0d607d141ae997b037b3a80e.png
833 ms
resto-2d5a00d1397ba3c3bc175fb3e30dd395.png
834 ms
resto-8769256b590197977f170db62bb71f56.png
834 ms
resto-50a7ac5ebc444507f235c8be011eed69.png
835 ms
evrone-ee5f5e266ee2b1763036ba8a1d9f35d1.svg
1253 ms
header_gray-5ca669aadf72ad8997e6157e1f5c2699.png
971 ms
region_marker-463154385ac0a6c285b09a65f724abd6.png
964 ms
logo-2dec013280670e2a8261db7b16bad67d.png
1003 ms
4.5-17493-4.png
122 ms
4.0-17493-4.png
127 ms
3.0-17493-4.png
129 ms
5.0-17493-4.png
132 ms
__utm.gif
32 ms
144R0N19-2.png
1175 ms
forumgazel-fincanpng__44_.png
1380 ms
Rings.png
1379 ms
map-cd43aa9cabd8dd285746acb1eea5b234.png
916 ms
t-day-ic-690272318cf7c9d5270aec58e5e8c21e.png
1206 ms
t-order-btn-d25b36f3e56f3c670b870649da4c0608.png
1204 ms
toggle_left-7ba5c0794e4dade192497d0a89f27b37.png
1204 ms
toggle_right-042920dcf4ba2c22cd964a4bd7a7439f.png
1211 ms
Circle-Bold-6b257343c087bc34784602a8e39ffabe.woff
1198 ms
side_menu-5e5f40ee9884a19cd0f0ea8dd73948da.svg
1374 ms
side_menu-653fb8c8414bf5430236f8f3bacd891f.woff
1470 ms
msk-f9633f5b84c6de7b6d73de4fd43b48f7.png
1469 ms
widgets.js
704 ms
widget_community.php
773 ms
thumb_____________________________________________450_________3.jpg
1598 ms
place-marker-c161efe50fa22b0bf63d831d477fc1c1.png
1508 ms
post_shadow-7fbf4ea20e36cbf3f38c73c93fbb1688.png
1507 ms
hearts-5a5fbdfebfbb10e2f9afc768c94ff1c1.png
1508 ms
share-fa61ea05fdde4324f9dcaf7b663eb6a3.png
1529 ms
date-d6b87fc15753811b46b44227b9ed1d07.png
1592 ms
msk-7cf754f84d1a153814a41e96f5e988b8.png
1585 ms
756 ms
garantee-3ac24b768b4631f4c7bc882b87e23b4a.png
1603 ms
positive-c795e2224e2a21787d3224b6ee14ccc9.png
1604 ms
negative-a3516972ab3a0743110bd0732f7d4cee.png
1604 ms
footer-stripe-b6d30793465dc20da413e46f0d1b2d8f.png
1648 ms
top100.scn
702 ms
bg_jobs-e34c8854e0ac92542a3b4ba0a2cce727.jpg
1070 ms
feedback_tiser-4f8cf54a114087ad551b2f6e5f986619.png
1109 ms
ui-bg_flat_75_ffffff_40x100-7921c08fa98cc1a05bcdd287cdc0d3a7.png
1155 ms
select2-bb3f5dc50a5be07085f468cdd956a3db.png
1154 ms
handle_active-8fe6f2e5eb28a05d61805d8ae8a3a631.png
1161 ms
likebox.php
411 ms
old.adriver.js
422 ms
button.71000885400e222c3c0eec823f8f93f0.js
493 ms
loader_nav19239_3.js
361 ms
lite.css
396 ms
lite.js
577 ms
lang3_0.js
394 ms
widget_community.css
399 ms
xdm.js
394 ms
al_community.js
398 ms
294 ms
4zvF1Y0eZKv.css
693 ms
SRSW8M763HA.js
934 ms
ullQFyhrQFI.js
1057 ms
y97Ig99UVTs.js
960 ms
KHAtULXOQuz.js
921 ms
xd_arbiter.php
463 ms
xd_arbiter.php
843 ms
ef50ac9e93aaebe3299791c79f277f8e.cur
376 ms
424 ms
3ce22e999d54bb9ca8150a59207f9d3e.cur
533 ms
4965b66fe115b2f2ed500ece66514d86.cur
652 ms
77492cf358d8b12629399322926c93f2.cur
646 ms
counter
410 ms
counter
408 ms
712 ms
tiles
219 ms
tiles
379 ms
tiles
295 ms
tiles
365 ms
597 ms
checkFlash.adriver.js
351 ms
functions.adriver.js
345 ms
follow_button.fd774b599f565016d763dd860cb31c79.ru.html
107 ms
e_e754d21a.jpg
383 ms
eMNqLVT4Tqs.jpg
329 ms
e_bc9f2db4.jpg
441 ms
GFZzGTIptoo.jpg
408 ms
Q5CsVlOK-zw.jpg
405 ms
xEakb67I48Q.jpg
328 ms
camera_50.png
160 ms
deactivated_50.png
160 ms
upload.gif
161 ms
w_logo.png
138 ms
inception-1458751524111.js
490 ms
jot
109 ms
VXcANLwwL5J.js
74 ms
i8XO-4kv8i7.js
70 ms
merle.cgi
281 ms
merle.cgi
284 ms
merle.cgi
299 ms
merle.cgi
537 ms
merle.cgi
547 ms
merle.cgi
558 ms
merle.cgi
306 ms
merle.cgi
301 ms
merle.cgi
334 ms
script.js
256 ms
1.html
277 ms
script.js
263 ms
1.html
277 ms
script.js
271 ms
1.html
305 ms
script.js
251 ms
1.html
271 ms
script.js
284 ms
1.html
268 ms
1.js
270 ms
script.js
245 ms
1.html
268 ms
script.js
306 ms
1.html
269 ms
script.js
276 ms
1.html
300 ms
script.js
271 ms
1.html
503 ms
pixel
17 ms
adriver-sync
283 ms
ADsMZ9f4T6BcC2osxtS9ezw
278 ms
pixel
15 ms
html.adriver.js
328 ms
sync.cgi
264 ms
sync.cgi
261 ms
sync.cgi
275 ms
sync.cgi
264 ms
sync.cgi
264 ms
pixel.adriver.js
136 ms
ippolit_banner.html
278 ms
andiamo_banner.html
269 ms
post_banner.html
270 ms
html.js
280 ms
html.js
272 ms
html.js
248 ms
sync.cgi
559 ms
c7af.jpg
807 ms
0eeb.png
869 ms
fd29.jpg
784 ms
2704.png
655 ms
20f3.jpg
795 ms
nr-918.min.js
55 ms
resto.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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
resto.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the geolocation permission on page load
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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
resto.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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Resto.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 Resto.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.
resto.ru
Open Graph description is not detected on the main page of Resto. 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: