3.3 sec in total
261 ms
2.7 sec
373 ms
Click here to check amazing Mobile content for Germany. Otherwise, check out these important facts you probably never knew about mobile.de
mobile.de » Deutschlands größter Fahrzeugmarkt ✓ Autos als Neu- & Gebrauchtwagen ✓ Wohnmobile ✓ Motorräder ✓ Nutzfahrzeuge ✓Jetzt finden!
Visit mobile.deWe analyzed Mobile.de page load time and found that the first response time was 261 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
mobile.de performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value5.1 s
25/100
25%
Value6.6 s
37/100
10%
Value4,290 ms
1/100
30%
Value0.002
100/100
15%
Value15.8 s
6/100
10%
261 ms
428 ms
271 ms
536 ms
620 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 30% of them (22 requests) were addressed to the original Mobile.de, 9% (7 requests) were made to Static.classistatic.de and 5% (4 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (832 ms) relates to the external source Static.classistatic.de.
Page size can be reduced by 1.1 MB (56%)
2.0 MB
891.2 kB
In fact, the total size of Mobile.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. 45% of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 148.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. 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 148.8 kB or 75% of the original size.
Potential reduce by 83.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. Obviously, Mobile needs image optimization as it can save up to 83.8 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 903.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 903.2 kB or 72% of the original size.
Number of requests can be reduced by 37 (58%)
64
27
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mobile. 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 as a result speed up the page load time.
mobile.de
261 ms
www.mobile.de
428 ms
home-b181ddfe12.css
271 ms
adframe.js
536 ms
676045833advFallback.js
620 ms
3707457750advertisingHeadPacked.js
705 ms
617143658csaHeadPacked.js
790 ms
iam.js
408 ms
jquery.min.js
6 ms
adframe.js
93 ms
home-8e5a87cd91.js
634 ms
2631831453advertisingPacked.js
791 ms
adex.js
256 ms
analytics.js
6 ms
fbevents.js
136 ms
event
16 ms
event
204 ms
24 ms
icons-data-svg.css
95 ms
gpt.js
7 ms
pubads_impl_81.js
5 ms
container.html
13 ms
content_45_01_news.jpg
314 ms
37 ms
ut
218 ms
content_45_02_fahrbericht.jpg
203 ms
content_45_03_ratgeber.jpg
563 ms
motortalk-teaser.jpg
387 ms
ebay-motors-logo.png
209 ms
Auto-Ersatzteile.jpg
201 ms
Autoreifen.jpg
312 ms
Auto-Anbau.jpg
315 ms
Auto-Tuning.jpg
319 ms
Motorradteile.jpg
386 ms
Schmierstoffe.jpg
464 ms
de-play-badge.png
698 ms
teaser-mobile_apps.jpg
486 ms
renault_service_190x35.jpg
476 ms
tx.io
206 ms
ads
105 ms
28 ms
Gibson-Regular-webfont.woff
578 ms
Gibson-SemiBold-webfont.woff
832 ms
conversion_async.js
15 ms
activityi;src=4339217;type=neuen00;cat=conve0;qty=1;cost=;ord=
85 ms
imgad
57 ms
aclk
79 ms
osd.js
30 ms
tx.io
114 ms
html_floating_rendering_lib_200_121.js
41 ms
B9477543.128852994;dc_trk_aid=301849100;dc_trk_cid=69049995;ord=188453619;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=
59 ms
1203755591489734327
20 ms
15206880681401444771
29 ms
134 ms
Download_on_the_App_Store_Badge_DE_Source_135x40.svg
168 ms
B9477543.128852993;dc_trk_aid=301849100;dc_trk_cid=69049995;ord=1949095661;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=
76 ms
loginStatus.js
514 ms
274 ms
Car
368 ms
dealerLogos.html
491 ms
collect
15 ms
collect
57 ms
Car
463 ms
count.json
276 ms
12 ms
52 ms
ga-audiences
41 ms
34 ms
s
161 ms
dis.aspx
214 ms
rta.js
18 ms
rta.js
20 ms
rta.js
19 ms
rc
227 ms
mobile.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
mobile.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
mobile.de 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
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 Mobile.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 Mobile.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.
mobile.de
Open Graph description is not detected on the main page of Mobile. 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: