mobile.de mobile.de

Mobile Usability

99/100

Good

Mobile Speed

45/100

Bad

Last tested: 2017-08-27

Rescan
mobile.de Mobile Usability: 99/100
mobile.de Mobile Usability Test Quick Overview

Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.
The following tap targets are close to other nearby tap targets and may need additional spacing around them.
The tap target <a href="/fahrzeuge/auto" class="nocolor"></a> and 3 others are close to other tap targets.
mobile.de Mobile Speed: 45/100
mobile.de Mobile Speed Test Quick Overview

Avoid landing page redirects

Your page has 3 redirects. Redirects introduce additional delays before the page can be loaded.
Avoid landing page redirects for the following chain of redirected URLs.
http://mobile.de/
http://www.mobile.de/
https://www.mobile.de/
https://m.mobile.de/fahrzeuge/auto
Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 5 blocking script resources and 3 blocking CSS resources. This causes a delay in rendering your page.
https://ssl.google-analytics.com/ga_exp.js?utmxkey…utmxtime=1494270448848
https://m.mobile.de/portal/js/libs.min.be3b30dbffbaf1293829c50346fa5afe.js
https://cdn.optimizely.com/js/6770241153.js
https://script.ioam.de/iam.js
https://m.mobile.de/portal/js/app.min.2197619a2a918381862d3cf71bfef669.js
Optimize CSS Delivery of the following:
https://m.mobile.de/portal/css/app-sprite.de25fc39…897c13c9c42731b823.css
https://m.mobile.de/portal/css/hires-sprite.d2a33f…b9454566978985e2ac.css
https://m.mobile.de/portal/css/icons.svg.ebf362e08…b9ac491cdb6806dfa1.css
Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:
https://ssl.google-analytics.com/ga_exp.js?utmxkey…utmxtime=1494270448848 (30 seconds)
https://m.mobile.de/svc/s/?cn=DE&dam=0&s=Car&vc=Car&fe!=EXPORT&psz=0 (60 seconds)
https://cdn.optimizely.com/js/6770241153.js (2.1 minutes)
https://dmp.theadex.com/d/230/2400/s/adex.js (5 minutes)
https://www.googletagservices.com/tag/js/gpt_mobile.js (15 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/366576093513123?v=2.7.6 (20 minutes)
https://pagead2.googlesyndication.com/pagead/osd.js (60 minutes)
https://script.ioam.de/iam.js (2 hours)
https://www.google-analytics.com/analytics.js (2 hours)
https://m.mobile.de/svc/r/Car (12 hours)
https://m.mobile.de/svc/r/makes/Car (12 hours)
https://m.mobile.de/portal/css/app-sprite.de25fc39…897c13c9c42731b823.css (24 hours)
https://m.mobile.de/portal/css/hires-sprite.d2a33f…b9454566978985e2ac.css (24 hours)
https://m.mobile.de/portal/css/icons.svg.ebf362e08…b9ac491cdb6806dfa1.css (24 hours)
https://m.mobile.de/portal/fonts/mobile.de_iconfont.ttf (24 hours)
https://m.mobile.de/portal/images/dark_background_stripes.gif (24 hours)
https://m.mobile.de/portal/images/highressprite1.png (24 hours)
https://m.mobile.de/portal/images/homescreen/icon-114.png (24 hours)
https://m.mobile.de/portal/js/app.min.2197619a2a918381862d3cf71bfef669.js (24 hours)
https://m.mobile.de/portal/js/libs.min.be3b30dbffbaf1293829c50346fa5afe.js (24 hours)
https://m.mobile.de/portal/js/templates/ad-small.js?1494270451797 (24 hours)
https://m.mobile.de/portal/js/templates/des.js?1494270451885 (24 hours)
https://m.mobile.de/portal/js/templates/header.js?1494270449907 (24 hours)
https://m.mobile.de/portal/js/templates/page1ads.js?1494270451758 (24 hours)
https://m.mobile.de/portal/js/templates/qs.js?1494270449337 (24 hours)
https://m.mobile.de/portal/js/templates/qsfooter.js?1494270450033 (24 hours)
https://m.mobile.de/portal/js/templates/qstabcontent.js?1494270449403 (24 hours)
https://m.mobile.de/portal/js/templates/srp.js?1494270451914 (24 hours)
Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.
The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.
None of the final above-the-fold content could be rendered even with the full HTML response.
Optimize images

Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 6.7KiB (24% reduction).
Compressing https://tpc.googlesyndication.com/simgad/11454133131908118017 could save 6.7KiB (24% reduction).
Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.
Enable compression for the following resources to reduce their transfer size by 1.2KiB (57% reduction).
Compressing https://dis.eu.criteo.com/dis/dis.aspx?p=2844&cb=4…32&sc_d=24&site_type=m could save 1.2KiB (57% reduction).
Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.
Minify JavaScript for the following resources to reduce their size by 710B (12% reduction).
Minifying https://script.ioam.de/iam.js could save 710B (12% reduction) after compression.

mobile.de Mobile Resources


Total Resources90
Number of Hosts36
Static Resources37
JavaScript Resources32
CSS Resources3

mobile.de Mobile Resource Breakdown