5.2 sec in total
549 ms
4.4 sec
309 ms
Click here to check amazing Kafebar content for Russia. Otherwise, check out these important facts you probably never knew about kafebar.ru
Каталог рестораны кафе Москвы - удобный поиск ресторана по станции метро. Единая банкетная служба всех банкетных залов. Провести свадебу и банкет в ресторане в Москве поможет каталог Кафебар.ру
Visit kafebar.ruWe analyzed Kafebar.ru page load time and found that the first response time was 549 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
kafebar.ru performance score
name
value
score
weighting
Value2.5 s
68/100
10%
Value2.5 s
90/100
25%
Value8.6 s
17/100
10%
Value4,110 ms
1/100
30%
Value0.242
51/100
15%
Value25.7 s
0/100
10%
549 ms
448 ms
671 ms
461 ms
462 ms
Our browser made a total of 117 requests to load all elements on the main page. We found that 33% of them (39 requests) were addressed to the original Kafebar.ru, 46% (54 requests) were made to St6-21.vk.com and 6% (7 requests) were made to Vk.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source St6-21.vk.com.
Page size can be reduced by 419.9 kB (15%)
2.7 MB
2.3 MB
In fact, the total size of Kafebar.ru main page is 2.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. Javascripts take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 46.6 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 10.0 kB, which is 17% 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 46.6 kB or 80% of the original size.
Potential reduce by 14.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. Kafebar images are well optimized though.
Potential reduce by 282.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 282.3 kB or 16% of the original size.
Potential reduce by 76.4 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. Kafebar.ru needs all CSS files to be minified and compressed as it can save up to 76.4 kB or 14% of the original size.
Number of requests can be reduced by 68 (64%)
106
38
The browser has sent 106 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kafebar. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
kafebar.ru
549 ms
base2.css
448 ms
jquery-1.3.2.min.js
671 ms
index.js
461 ms
swfobject.js
462 ms
openapi.js
363 ms
conversion.js
79 ms
js
60 ms
ya.ru
376 ms
current_traffic_150.gif
515 ms
banya1.jpg
219 ms
logo.png
223 ms
bg-title2.jpg
111 ms
left2.jpg
113 ms
right2.jpg
216 ms
rekl200.jpg
225 ms
bs200.jpg
335 ms
ban_otelra.jpg
337 ms
avtos.jpg
321 ms
ikra250i.jpg
328 ms
belle200.jpg
335 ms
a15.jpg
336 ms
b23.jpg
439 ms
a18.jpg
463 ms
bank.jpg
464 ms
n85.jpg
465 ms
n55.jpg
466 ms
n3.jpg
466 ms
n54.jpg
561 ms
_vraiu0.jpg
565 ms
znam.jpg
565 ms
_rodnik0.jpg
565 ms
n52.jpg
565 ms
n12.jpg
566 ms
_7kr2.jpg
636 ms
white20.gif
671 ms
left37.jpg
675 ms
left38.jpg
674 ms
left39.jpg
675 ms
Fb1.jpg
676 ms
Tv1.jpg
740 ms
Vk1.jpg
784 ms
perfo.gif
769 ms
pluso-like.js
142 ms
tag.js
951 ms
bg-title2.jpg
116 ms
openapi.a2ed73393cad04481c1dfb3f7794921f.js
234 ms
54 ms
js
59 ms
analytics.js
27 ms
97 ms
collect
56 ms
36 ms
widget_community_messages.php
211 ms
loader_nav210110080168_3.js
175 ms
fonts_cnt.c7a76efe.css
970 ms
lite.ca486089.css
681 ms
lang3_2.js
476 ms
c3d11fba.296f7859.js
567 ms
community_messages.js
591 ms
react.6a15a5cc.js
778 ms
vkui.a2e1063b.js
915 ms
vkcom-kit.7b3cac7c.css
798 ms
vkcom-kit.1be21eee.js
1009 ms
vkcom-kit-icons.76c15529.js
875 ms
state-management.d517d148.js
896 ms
architecture-mobx.906cf75b.js
901 ms
audioplayer-lib.93b52d88.css
959 ms
audioplayer-lib.8f87c867.js
1098 ms
palette.c6976fb5.css
1006 ms
palette.af6605eb.js
1017 ms
sticker-lib.72942183.css
1040 ms
sticker-lib.5dba0bca.js
1044 ms
common.7a6628b8.js
1749 ms
af475d37.163909ea.js
1084 ms
39820787.e54fad24.js
1105 ms
782f47a3.985754ca.js
1126 ms
fc936a0f.55bdd7f7.js
1128 ms
f3627a66.5a6a198d.js
1258 ms
emoji.39f546de.css
1178 ms
emoji.aaccc99e.js
1192 ms
ui_common.b1037836.css
1206 ms
ui_common.e824cbec.js
1215 ms
b691fd56.8c978f39.js
1357 ms
ui_media_selector.33883160.css
1278 ms
ui_media_selector.4b37971d.js
1288 ms
xdm.js
1297 ms
f528815f.2172bb1b.js
1352 ms
upload.b1037836.css
1365 ms
upload.19464188.js
1370 ms
stickers.00218c43.css
1378 ms
stickers.542e9e8a.js
1446 ms
lang3_0.js
766 ms
lite.bcf10ece3464fec8b554bde483fa2494.js
448 ms
advert.gif
837 ms
vkui.43318ab6.css
981 ms
widget_community_messages.06a7f227.css
878 ms
notifier.c8aea11f.css
777 ms
ui_common.5f35f406.css
706 ms
ui_media_selector.2e6f2ad1.css
749 ms
base.e3cf9d3a.css
686 ms
openapi.js
666 ms
sync_cookie_image_decide
143 ms
1
143 ms
lA5K18hXY1aNGu7KQ390sT8z4gqac51b02TdAE_n1hv-yeiDv2_OG8MhH90z0xb6zzgwgSUw92nuKgOeKksYH1Xu.jpg
532 ms
QulWsGFAn5k.png
501 ms
w_chat_icon.png
84 ms
w_chat_logo.png
85 ms
widgets_logo_white.svg
89 ms
chats.png
88 ms
community_messages_widget_small_logo.svg
91 ms
emoji_smile_icon.svg
85 ms
upload.gif
161 ms
roboto400.woff
293 ms
roboto500.woff
264 ms
roboto300.woff
280 ms
roboto700.woff
278 ms
kafebar.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.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
<object> elements do not have alternate text
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
kafebar.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
kafebar.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
Document uses plugins
RU
N/A
WINDOWS-1251
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kafebar.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 Kafebar.ru main page’s claimed encoding is windows-1251. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
kafebar.ru
Open Graph description is not detected on the main page of Kafebar. 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: