9.2 sec in total
1.1 sec
7.9 sec
182 ms
Click here to check amazing M A I content for Germany. Otherwise, check out these important facts you probably never knew about m-a-i.de
Visit m-a-i.deWe analyzed M-a-i.de page load time and found that the first response time was 1.1 sec and then it took 8.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
m-a-i.de performance score
name
value
score
weighting
Value6.7 s
2/100
10%
Value11.2 s
0/100
25%
Value13.2 s
2/100
10%
Value1,600 ms
12/100
30%
Value0.002
100/100
15%
Value11.7 s
17/100
10%
1143 ms
218 ms
763 ms
440 ms
328 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 92% of them (58 requests) were addressed to the original M-a-i.de, 3% (2 requests) were made to Statistik.m-a-i.de and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.7 sec) relates to the external source Statistik.m-a-i.de.
Page size can be reduced by 913.1 kB (46%)
2.0 MB
1.1 MB
In fact, the total size of M-a-i.de main page is 2.0 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. 20% of websites need less resources to load. Images take 841.5 kB which makes up the majority of the site volume.
Potential reduce by 22.1 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 22.1 kB or 77% of the original size.
Potential reduce by 54.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. M A I images are well optimized though.
Potential reduce by 552.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 552.7 kB or 72% of the original size.
Potential reduce by 284.1 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. M-a-i.de needs all CSS files to be minified and compressed as it can save up to 284.1 kB or 84% of the original size.
Number of requests can be reduced by 45 (75%)
60
15
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of M A I. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.
1143 ms
style.css
218 ms
bootstrap.min.css
763 ms
bootstrap-responsive.min.css
440 ms
bootstrap-extended.css
328 ms
bootstrap-frontend.min.css
330 ms
bootstrap-responsive-frontend.min.css
547 ms
system.css
437 ms
general.css
545 ms
template.css
977 ms
template_pro.css
1097 ms
cyan.css
769 ms
custom.css
767 ms
jsn_wide.css
768 ms
jsn_mobile.css
1182 ms
jsn_social_icons.css
979 ms
custom.css
1089 ms
modal.css
990 ms
style.css
1297 ms
skitter.styles.css
1304 ms
template.css
1206 ms
mootools-core.js
1666 ms
core.js
1207 ms
jquery.min.js
1849 ms
jquery-noconflict.js
1319 ms
jquery-migrate.min.js
1517 ms
k2.js
1524 ms
bootstrap.min.js
1647 ms
caption.js
1540 ms
mootools-more.js
2495 ms
noconflict.js
1739 ms
utils.js
2080 ms
jsn_template.js
1868 ms
modal.js
1987 ms
jquery.min.js
2546 ms
jsn_is_conflict.js
2062 ms
jquery.easing.1.3.js
2083 ms
jquery.animate-colors-min.js
2094 ms
jquery.skitter.js
2598 ms
system.css
1967 ms
css
55 ms
439 ms
Logo_MAI_klein.png
317 ms
logo.png
432 ms
icons-uni.png
217 ms
icons-social.png
433 ms
icon-arrow-down.png
231 ms
de.gif
227 ms
en.gif
434 ms
bg-promo.png
441 ms
Startseite1_eng.jpg
1234 ms
Startseite2_eng.jpg
1290 ms
Startseite3_eng.jpg
1421 ms
Broschure.png
968 ms
Servicehotline.png
858 ms
top.png
642 ms
BkZwJXYnumPMepfEA344yQ.ttf
67 ms
piwik.js
749 ms
prev.png
806 ms
next.png
1008 ms
ajax-loader.gif
1136 ms
piwik.php
2724 ms
print.css
112 ms
m-a-i.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
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
m-a-i.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
m-a-i.de 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
DE
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise M-a-i.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it does not match the claimed English language. Our system also found out that M-a-i.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.
m-a-i.de
Open Graph description is not detected on the main page of M A I. 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: