opodo.de Billige Flüge, Urlaub, Hotels und Reisen buchen bei Opodo

Mobile Usability



Mobile Speed



Last tested: 2017-08-29

opodo.de Mobile Usability: 99/100
opodo.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 <label for="swiper-slide0" class="od-swiper-pagi…per_pagination"></label> is close to 1 other tap targets.
The tap target <label for="swiper-slide1" class="od-swiper-pagi…per_pagination"></label> is close to 1 other tap targets.
opodo.de Mobile Speed: 52/100
opodo.de Mobile Speed Test Quick Overview

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 1 blocking CSS resources. This causes a delay in rendering your page.
Optimize CSS Delivery of the following:
Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.
Avoid landing page redirects for the following chain of redirected URLs.
Reduce server response time

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.
84.9KiB of the HTML response was required to render the above-the-fold content. This requires 3 network round-trips. Prioritize the above-the-fold content so that it can be rendered with only the first 2 round-trips' worth of HTML.
Only about 30% of the final above-the-fold content could be rendered with the HTML delivered within 2 round-trips.
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 36.2KiB (68% reduction).
Compressing https://api.boxever.com/v1.2/boxever-cross-domain.…A%2F%2Fwww.opodo.de%2F could save 17.4KiB (69% reduction).
Compressing https://api.boxever.com/v1.2/boxever-min.js?client…4xhDV9rsny82DvKa1iYFBN could save 17KiB (68% reduction).
Compressing https://www.opodo.de/travel/service/tracking/ua/customDimensions could save 967B (68% reduction).
Compressing https://dis.eu.criteo.com/dis/dis.aspx?p=3282&cb=3…32&sc_d=24&site_type=m could save 818B (52% reduction).
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://nexus.ensighten.com/opodo/mobile-prod/Bootstrap.js (5 minutes)
https://stats.g.doubleclick.net/dc.js (2 hours)
https://www.google-analytics.com/analytics.js (2 hours)
Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.
Minify HTML for the following resources to reduce their size by 18.3KiB (73% reduction).
Minifying https://api.boxever.com/v1.2/boxever-cross-domain.…A%2F%2Fwww.opodo.de%2F could save 18.3KiB (73% reduction).
Optimize images

Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 864B (23% reduction).
Compressing https://a2.odistatic.net/images/onefront/bluestone/OP/app-4stars@2x.png could save 864B (23% reduction).

opodo.de Mobile Resources

Total Resources68
Number of Hosts23
Static Resources29
JavaScript Resources33
CSS Resources2

opodo.de Mobile Resource Breakdown