5.8 sec in total
840 ms
4.5 sec
481 ms
Click here to check amazing Cafe Anderson content for Russia. Otherwise, check out these important facts you probably never knew about cafe-anderson.ru
Сеть уютных семейных кафе АндерСон, расположенных в лучших районах Москвы. У нас собственная кондитерская, где изготавливается вкуснейшие десерты. Ждем вас в наших кафе!
Visit cafe-anderson.ruWe analyzed Cafe-anderson.ru page load time and found that the first response time was 840 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
cafe-anderson.ru performance score
name
value
score
weighting
Value8.7 s
0/100
10%
Value9.1 s
1/100
25%
Value20.5 s
0/100
10%
Value3,690 ms
1/100
30%
Value0.43
22/100
15%
Value34.0 s
0/100
10%
840 ms
271 ms
281 ms
568 ms
285 ms
Our browser made a total of 114 requests to load all elements on the main page. We found that 41% of them (47 requests) were addressed to the original Cafe-anderson.ru, 13% (15 requests) were made to Maps.google.com and 11% (12 requests) were made to Vk.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Mc.yandex.ru.
Page size can be reduced by 1.3 MB (31%)
4.3 MB
2.9 MB
In fact, the total size of Cafe-anderson.ru main page is 4.3 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.8 MB which makes up the majority of the site volume.
Potential reduce by 74.8 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 16.2 kB, which is 18% 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 74.8 kB or 81% of the original size.
Potential reduce by 276.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. Cafe Anderson images are well optimized though.
Potential reduce by 819.2 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 819.2 kB or 66% of the original size.
Potential reduce by 149.6 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. Cafe-anderson.ru needs all CSS files to be minified and compressed as it can save up to 149.6 kB or 85% of the original size.
Number of requests can be reduced by 40 (38%)
105
65
The browser has sent 105 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cafe Anderson. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
cafe-anderson.ru
840 ms
kernel_main.css
271 ms
template_a7f5e7f33827286a2f1f01a47cdc5706_fe5ca3a45a936a9b811a82abc4d72f89.css
281 ms
kernel_main.js
568 ms
style.css
285 ms
jquery-1.7.2.min.js
442 ms
slides.min.jquery.js
306 ms
init.js
403 ms
jquery.the-modal.js
422 ms
my.js
425 ms
cs.min.js
867 ms
js
43 ms
openapi.js
386 ms
analytics.js
26 ms
body-bg.jpg
321 ms
a73c4255a9eb82422c43340e17c82b4b.jpg
430 ms
13ff64f22384ca755af28602c3fdfa8c.jpg
670 ms
98a41c6586a5bf1e81ada63b89baa7b7.jpg
321 ms
34c5b07837e8505c98a76af0e95a815b.jpg
846 ms
9c10f213b69899eba0ba0f2796f3415c.jpg
853 ms
34d5d1a5efa98d930ee8e2c1bac7e263.jpg
424 ms
d30c8bbfa815e9739ce77bdc1d3190b6.jpg
573 ms
46a27f50762ae543cdbb64ca0b5f91bc.jpg
565 ms
gift1.jpg
572 ms
2f6bbc0e5fecb2fc0112de2751e6b5c6.jpg
707 ms
19bff7ed9213c9977d43bb05cfd6407d.jpg
715 ms
a0e4a9b22489c0f3e6b94f65c0b39364.jpg
717 ms
ea7716545be3aa2389c65cc1740ff0bf.JPG
803 ms
20e2f008df1252839c757c7286b156d1.png
847 ms
4eeccf46e0a5494e18453e6805e57acf.png
857 ms
dc415368a18cf5a4326f4dc545ea6110.jpg
862 ms
e3c35f9b1555637b0b4cb7122e89c293.jpg
938 ms
56416010f968f6160df2dbed59b42713.png
985 ms
94747b698922f96ac57a07bf640f78f1.png
987 ms
e1213821e6d05bc17a8234ed9fb93f8c.jpg
995 ms
2e3c799974e23b59c5c2a5621ff0a9bd.jpg
1005 ms
5b94987be61d9bf05f8ccf211690ca5f.jpg
1590 ms
c5b360f3ed3ed3b2743f7bf4fcce5ccd.jpg
1114 ms
1e7e9cce04c5e327a066eec4a4ae8b1f.jpg
1153 ms
d640af3177a8521327c435854652f0cd.jpg
1155 ms
6d09c98c7c9f9bfd381a5704f075b85b.png
1156 ms
d0e58a5d877f9397781cb0686d01ffb5.jpg
1316 ms
678c7f0507e974bf786fd96baf9e676c.png
1260 ms
widget.js
926 ms
widget.css
994 ms
collect
12 ms
collect
67 ms
ga-audiences
57 ms
151 ms
opr.png
996 ms
opr1.png
997 ms
consultant.min.js
152 ms
info
281 ms
loader.gif
400 ms
logonew.png
313 ms
icons.png
473 ms
ico_tw.png
419 ms
common.js
22 ms
map.js
21 ms
util.js
72 ms
marker.js
70 ms
linetomain.png
360 ms
StaticMapService.GetMapImage
210 ms
all.js
299 ms
onion.js
23 ms
openhand_8_8.cur
52 ms
ViewportInfoService.GetViewportInfo
86 ms
stats.js
35 ms
controls.js
32 ms
StaticMapService.GetMapImage
216 ms
transparent.png
78 ms
css
70 ms
google4.png
60 ms
mapcnt6.png
61 ms
sv5.png
60 ms
map-marker.png
178 ms
tmapctrl.png
37 ms
tmapctrl4.png
36 ms
vt
34 ms
vt
60 ms
vt
25 ms
vt
26 ms
vt
57 ms
vt
57 ms
vt
27 ms
CrYjSnGjrRCn0pd9VQsnFOvvDin1pK8aKteLpeZ5c0A.woff
52 ms
RxZJdnzeo3R5zSexge8UUbO3LdcAZYWl9Si6vvxL-qU.woff
53 ms
Hgo13k-tfSpn0qi1SFdUfbO3LdcAZYWl9Si6vvxL-qU.woff
53 ms
d-6IYplOFocCacKzxwXSOLO3LdcAZYWl9Si6vvxL-qU.woff
53 ms
upload.gif
137 ms
widget_community.php
286 ms
segoeprint.ttf
285 ms
watch.js
169 ms
AuthenticationService.Authenticate
171 ms
42 ms
xd_arbiter.php
214 ms
xd_arbiter.php
418 ms
watch.js
1612 ms
consultant_main-43A400.css
150 ms
loader_nav19127_3.js
129 ms
lite.css
132 ms
lite.js
513 ms
lang3_0.js
257 ms
widget_community.css
262 ms
xdm.js
263 ms
al_community.js
263 ms
iconset.png
437 ms
c2ZqOc83srQ.jpg
262 ms
Jcn5gK4KDm4.jpg
392 ms
cZDQ1n6_TSA.jpg
406 ms
LVM--39iPWA.jpg
256 ms
g5mrZhbmz7w.jpg
394 ms
camera_50.png
129 ms
w_logo.png
131 ms
cafe-anderson.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
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.
cafe-anderson.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
cafe-anderson.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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 Cafe-anderson.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 Cafe-anderson.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.
cafe-anderson.ru
Open Graph description is not detected on the main page of Cafe Anderson. 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: