5.1 sec in total
345 ms
4.3 sec
465 ms
Welcome to mokka.de homepage info - get ready to check MOKKA best content right away, or after learning these important things about mokka.de
Genießen Sie köstliche Kuchen und Kaffee in allen Variationen oder unseren abwechslungsreichen Mittagstisch in unserem Café & Restaurant. Jetzt genießen!
Visit mokka.deWe analyzed Mokka.de page load time and found that the first response time was 345 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
mokka.de performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value5.1 s
25/100
25%
Value7.9 s
23/100
10%
Value60 ms
100/100
30%
Value0
100/100
15%
Value4.9 s
77/100
10%
345 ms
813 ms
1019 ms
634 ms
668 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 15% of them (9 requests) were addressed to the original Mokka.de, 34% (21 requests) were made to Mein.web4business.de and 32% (20 requests) were made to Fonts.cm4all.net. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Public.od.cm4allbusiness.de.
Page size can be reduced by 203.9 kB (12%)
1.7 MB
1.5 MB
In fact, the total size of Mokka.de main page is 1.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. 35% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 63.0 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 63.0 kB or 83% of the original size.
Potential reduce by 63.8 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. MOKKA images are well optimized though.
Potential reduce by 38.1 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 38.1 kB or 25% of the original size.
Potential reduce by 38.9 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. Mokka.de needs all CSS files to be minified and compressed as it can save up to 38.9 kB or 80% of the original size.
Number of requests can be reduced by 22 (55%)
40
18
The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of MOKKA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
mokka.de
345 ms
mokka.de
813 ms
beng-proxy.js
1019 ms
font-awesome.min.css
634 ms
deploy.css
668 ms
deploy.js
1039 ms
popup-guistrap.css
731 ms
widget-runtime@3.83.13.css
796 ms
jquery.js
1202 ms
prototype.js
912 ms
jshelper.js
859 ms
url.js
900 ms
html.js
975 ms
prototype_impl.js
1009 ms
widget-runtime@3.83.13.js
1119 ms
slideshow-common@3.83.13.css
1092 ms
slideshow-common@3.83.13.js
1111 ms
main.css
1122 ms
responsive.css
1151 ms
vars.css
307 ms
effects.js
998 ms
parallax.js
1031 ms
font-awesome,version=4
419 ms
cm_template-focus-point.js
1031 ms
show.js
119 ms
css
595 ms
b9f908d8-3357-41f1-8d3c-3a99f3e72c7a.jpg
981 ms
effect-003.png
171 ms
scale
576 ms
rss_shiny_20.png
113 ms
ticketrestaurant_small.png
223 ms
sodexo_small.png
276 ms
girocard_small.png
306 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf
323 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0C4n.ttf
611 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf
614 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf
614 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf
642 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4n.ttf
582 ms
fontawesome-webfont.woff
208 ms
If2cXTr6YS-zF4S-kcSWSVi_sxjsohD9F50Ruu7BMSoHTQ.ttf
435 ms
If2cXTr6YS-zF4S-kcSWSVi_sxjsohD9F50Ruu7BAyoHTQ.ttf
544 ms
If2cXTr6YS-zF4S-kcSWSVi_sxjsohD9F50Ruu7B7y0HTQ.ttf
656 ms
If2cXTr6YS-zF4S-kcSWSVi_sxjsohD9F50Ruu7B1i0HTQ.ttf
695 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaooCP.ttf
816 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoooCP.ttf
823 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEooCP.ttf
823 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaooCP.ttf
869 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao4CP.ttf
875 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpYCP.ttf
912 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pYCP.ttf
1020 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapYCP.ttf
1026 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpYCP.ttf
1032 ms
_pixel.img
125 ms
arrows.png
116 ms
scale
875 ms
scale
827 ms
scale
834 ms
scale
969 ms
scale
1160 ms
scale
1437 ms
scale
936 ms
mokka.de 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
Image elements do not have [alt] attributes
Form elements do not have associated labels
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.
mokka.de 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
mokka.de SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mokka.de 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 Mokka.de 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.
mokka.de
Open Graph description is not detected on the main page of MOKKA. 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: