6 sec in total
1.1 sec
4.7 sec
241 ms
Visit kantine.com now to see the best up-to-date Kantine content for Germany and also check out these interesting facts you probably never knew about kantine.com
Visit kantine.comWe analyzed Kantine.com page load time and found that the first response time was 1.1 sec and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
kantine.com performance score
name
value
score
weighting
Value3.1 s
48/100
10%
Value11.8 s
0/100
25%
Value9.7 s
11/100
10%
Value770 ms
38/100
30%
Value0.004
100/100
15%
Value11.1 s
20/100
10%
1121 ms
189 ms
189 ms
279 ms
192 ms
Our browser made a total of 100 requests to load all elements on the main page. We found that 49% of them (49 requests) were addressed to the original Kantine.com, 20% (20 requests) were made to Scontent.xx.fbcdn.net and 15% (15 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Kantine.com.
Page size can be reduced by 712.0 kB (44%)
1.6 MB
903.7 kB
In fact, the total size of Kantine.com main page is 1.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 724.6 kB which makes up the majority of the site volume.
Potential reduce by 29.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. 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 29.5 kB or 78% of the original size.
Potential reduce by 26.7 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. Kantine images are well optimized though.
Potential reduce by 461.7 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 461.7 kB or 74% of the original size.
Potential reduce by 194.2 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. Kantine.com needs all CSS files to be minified and compressed as it can save up to 194.2 kB or 83% of the original size.
Number of requests can be reduced by 53 (56%)
94
41
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kantine. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
www.kantine.com
1121 ms
wp-emoji-release.min.js
189 ms
front.css
189 ms
font-awesome.min.css
279 ms
styles.css
192 ms
front.css
192 ms
public.css
283 ms
magnific-popup.css
282 ms
css
25 ms
base.css
284 ms
flexslider.css
285 ms
mmenu.css
454 ms
stapel.css
371 ms
style.css
560 ms
orange.css
374 ms
prettyPhoto.css
375 ms
jquery.js
567 ms
jquery-migrate.min.js
463 ms
cart.js
468 ms
jquery.validate.min.js
469 ms
jquery.magnific-popup.min.js
565 ms
jquery.cookie.js
556 ms
public.js
563 ms
modernizr-2.6.2.js
564 ms
jquery.form.min.js
466 ms
scripts.js
468 ms
superfish.js
468 ms
jquery.mmenu.min.all.js
482 ms
jquery.flexslider.js
556 ms
jquery.matchHeight-min.js
481 ms
jquery.fitvids.js
554 ms
jquery.prettyPhoto.min.js
553 ms
jquery.isotope.js
647 ms
jquery.parallax-1.1.3.js
562 ms
jquery.shoutcast.min.js
585 ms
soundmanager2.js
831 ms
inlineplayer.js
645 ms
ci_audioplayer.js
652 ms
jquery.stapel.js
656 ms
scripts.js
694 ms
retina.js
739 ms
font-awesome.css
21 ms
analytics.js
32 ms
LOGO1-300x94.png
343 ms
Jess-Glynne-Flyer-426x500.jpg
345 ms
tarm_web-426x500.jpg
354 ms
clubnight-web-426x500.jpg
511 ms
aa50-web-426x500.jpg
620 ms
fruehlingserwachen-03.jpg
529 ms
2015_05_13_004.jpg
533 ms
MG_1849-750x500.jpg
543 ms
Logo_bluesnews-small.jpg
527 ms
all.js
15 ms
M2Jd71oPJhLKp0zdtTvoM0DauxaEVho0aInXGvhmB4k.ttf
14 ms
ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf
15 ms
toadOcfmlt9b38dHJxOBGMw1o1eFRj7wYC6JbISqOjY.ttf
16 ms
toadOcfmlt9b38dHJxOBGLsbIrGiHa6JIepkyt5c0A0.ttf
14 ms
toadOcfmlt9b38dHJxOBGBPPOa1q11iOmmM9mDHHHX4.ttf
15 ms
collect
72 ms
108 ms
xd_arbiter.php
21 ms
xd_arbiter.php
25 ms
ping
44 ms
page.php
364 ms
page.php
520 ms
pOm-b7lJL8q.css
47 ms
2NJaWBZ8ldv.css
42 ms
q68gy-v_YMF.js
39 ms
YvxwM8R7ol8.js
63 ms
ihptErjAmMX.js
43 ms
1BQnIVjTFoC.js
45 ms
juKryPYAUFc.js
81 ms
cUsKAwzqrQw.js
86 ms
11225181_10153187165677986_3846241111619299559_n.jpg
146 ms
1381960_10151717625022986_2107184662_n.jpg
55 ms
12118806_10205495472402796_8562946712926002328_n.jpg
60 ms
12804780_908465129266741_7971511981669310444_n.jpg
57 ms
12805791_187287878315409_6621834374324014905_n.jpg
59 ms
12705177_188732814816235_1264607347129884297_n.jpg
57 ms
11899975_1636758843203009_5255838735874797661_n.jpg
57 ms
12801145_168008743580089_561978648135936804_n.jpg
56 ms
1601548_681858545283558_106360370398524082_n.jpg
61 ms
261497_100832963346618_1009407_n.jpg
122 ms
wL6VQj7Ab77.png
52 ms
s7jcwEQH7Sx.png
52 ms
6GqoI2ZyIrf.png
53 ms
1499535_722095754470060_207599606_n.jpg
25 ms
1535679_721721207840848_667539398_n.jpg
21 ms
10268566_771168069583520_8370891380587415226_n.jpg
22 ms
12208660_10205226862053495_6338389412964230652_n.jpg
23 ms
8277_10204228825319970_6264765771582863592_n.jpg
24 ms
11898516_596628360440611_8432972865228718498_n.jpg
24 ms
12821337_1584358281889175_3760703790472225060_n.jpg
25 ms
12647217_10208925583123453_4821829101503468151_n.jpg
25 ms
12003223_10153311632197730_8564708478660521135_n.jpg
26 ms
10463886_993141814100233_8989253718100801325_n.jpg
26 ms
R9a_DtVRZgv.js
6 ms
cUDgRFxaoIk.js
3 ms
0JBr1QHp8Gi.js
2 ms
kDOzhTr2W91.js
3 ms
kantine.com accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
kantine.com 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
Page has valid source maps
kantine.com 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
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kantine.com can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Kantine.com 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.
kantine.com
Open Graph description is not detected on the main page of Kantine. 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: