Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

opodo.at

Billige Flüge, Städtereisen, Last Minute Urlaub & Reisen | Opodo

Page Load Speed

13.7 sec in total

First Response

177 ms

Resources Loaded

13.2 sec

Page Rendered

412 ms

opodo.at screenshot

About Website

Welcome to opodo.at homepage info - get ready to check Opodo best content for Austria right away, or after learning these important things about opodo.at

Billige Flug-Angebote & Hotels, günstige Pauschralreisen, Städtereisen & Mietwagen. Holen Sie sich die besten Reiseangebote bei Opodo!

Visit opodo.at

Key Findings

We analyzed Opodo.at page load time and found that the first response time was 177 ms and then it took 13.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

opodo.at performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value4.0 s

49/100

25%

SI (Speed Index)

Value7.9 s

23/100

10%

TBT (Total Blocking Time)

Value6,250 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.014

100/100

15%

TTI (Time to Interactive)

Value29.5 s

0/100

10%

Network Requests Diagram

opodo.at

177 ms

www.opodo.at

12794 ms

op_desktop.css

31 ms

background.jpg

35 ms

profile-at.png

32 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 10% of them (2 requests) were addressed to the original Opodo.at, 20% (4 requests) were made to A1.odistatic.net and 20% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (12.8 sec) belongs to the original domain Opodo.at.

Page Optimization Overview & Recommendations

Page size can be reduced by 841.0 kB (60%)

Content Size

1.4 MB

After Optimization

549.9 kB

In fact, the total size of Opodo.at main page is 1.4 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. 50% of websites need less resources to load. CSS take 580.2 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 305.4 kB

  • Original 344.1 kB
  • After minification 343.4 kB
  • After compression 38.7 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 305.4 kB or 89% of the original size.

Image Optimization

-3%

Potential reduce by 15.2 kB

  • Original 446.1 kB
  • After minification 430.9 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. Opodo images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 12.5 kB

  • Original 20.5 kB
  • After minification 20.5 kB
  • After compression 8.0 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 12.5 kB or 61% of the original size.

CSS Optimization

-88%

Potential reduce by 507.9 kB

  • Original 580.2 kB
  • After minification 576.8 kB
  • After compression 72.3 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. Opodo.at needs all CSS files to be minified and compressed as it can save up to 507.9 kB or 88% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

13

After Optimization

13

The browser has sent 13 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Opodo. According to our analytics all requests are already optimized.

Accessibility Review

opodo.at accessibility score

80

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

opodo.at best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

opodo.at SEO score

100

Search Engine Optimization Advices

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Opodo.at can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Opodo.at 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.

Social Sharing Optimization

Open Graph data is detected on the main page of Opodo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: