3.2 sec in total
776 ms
2.2 sec
298 ms
Welcome to mobilemall.de homepage info - get ready to check Mobilemall best content for Germany right away, or after learning these important things about mobilemall.de
Mobile Commerce Plattform
Visit mobilemall.deWe analyzed Mobilemall.de page load time and found that the first response time was 776 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
mobilemall.de performance score
name
value
score
weighting
Value0.7 s
100/100
10%
Value0.7 s
100/100
25%
Value0.8 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.7 s
100/100
10%
776 ms
23 ms
35 ms
197 ms
194 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 70% of them (52 requests) were addressed to the original Mobilemall.de, 7% (5 requests) were made to My.clickdesk.com and 7% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (776 ms) belongs to the original domain Mobilemall.de.
Page size can be reduced by 867.7 kB (49%)
1.8 MB
902.6 kB
In fact, the total size of Mobilemall.de main page is 1.8 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. 60% of websites need less resources to load. Javascripts take 849.2 kB which makes up the majority of the site volume.
Potential reduce by 70.3 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 70.3 kB or 84% of the original size.
Potential reduce by 22.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. Mobilemall images are well optimized though.
Potential reduce by 608.6 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 608.6 kB or 72% of the original size.
Potential reduce by 166.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. Mobilemall.de needs all CSS files to be minified and compressed as it can save up to 166.1 kB or 84% of the original size.
Number of requests can be reduced by 31 (46%)
68
37
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mobilemall. 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 9 to 1 for CSS and as a result speed up the page load time.
mobilemall.de
776 ms
css
23 ms
css
35 ms
styles.css
197 ms
form.css
194 ms
jquery-1.10.1.min.js
322 ms
custom-form.js
216 ms
custom-form.checkbox.js
200 ms
custom-form.select.js
199 ms
custom-form.radio.js
290 ms
jquery-ui-1.10.4.custom.min.js
292 ms
jquery.cycle.all.js
389 ms
scripts.js
294 ms
wgs.css
310 ms
default.min.css
385 ms
jquery.js
491 ms
jquery-migrate.min.js
404 ms
editor-styles.css
417 ms
widgetkit-fc274d69.css
418 ms
widgetkit-92beefe2.js
507 ms
wp-emoji-release.min.js
192 ms
atrk.js
333 ms
lightbox.js
325 ms
mediaelement-and-player.js
334 ms
spotlight.js
321 ms
analytics.js
319 ms
logo.png
328 ms
ico01.png
327 ms
bg-search-form-close.gif
327 ms
bg-search-field.gif
328 ms
arrow02.png
327 ms
img01.png
395 ms
ico02.png
330 ms
ico03.png
328 ms
ico09.png
328 ms
ico04.png
329 ms
ico05.png
359 ms
bullet04.png
361 ms
bullet02.png
362 ms
ico06.png
378 ms
arrow01.png
395 ms
ico07.png
418 ms
ico08.png
458 ms
img02.png
756 ms
img03.png
666 ms
img04.png
491 ms
brand01.png
492 ms
brand02.png
514 ms
brand03.png
554 ms
brand04.png
589 ms
brand05.png
588 ms
brand06.png
610 ms
brand07.png
650 ms
brand08.png
685 ms
livechat-new.js
288 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
261 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
260 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
261 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
262 ms
Q_pTky3Sc3ubRibGToTAYjnFfol0SnfBMmbnmUK0fZM.ttf
261 ms
close.png
385 ms
blank.gif
401 ms
atrk.gif
52 ms
collect
22 ms
livechat-cloud-new.js
29 ms
test.png
151 ms
livechat-v2.js
10 ms
preferences
292 ms
ajax-loader-cursor.gif
95 ms
3475a7.css
28 ms
warning.png
99 ms
proactive
116 ms
1403776873222
68 ms
ultra-modern-sprite.png
7 ms
mobilemall.de accessibility score
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
mobilemall.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
mobilemall.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mobilemall.de can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Mobilemall.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.
mobilemall.de
Open Graph data is detected on the main page of Mobilemall. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: