Tools & Wizards About Us
opodo.es screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

opodo.es

Ofertas de viajes, y vacaciones: reserva con la agencia online Opodo

Page Load Speed

2.8 sec in total

First Response

367 ms

Resources Loaded

2.3 sec

Page Rendered

136 ms

opodo.es screenshot

About Website

Visit opodo.es now to see the best up-to-date Opodo content for Morocco and also check out these interesting facts you probably never knew about opodo.es

Organiza tus vacaciones con a las mejores ofertas de viajes: encuentra los billetes de avión y hoteles más economicos y reserva con la agencia de viajes Opodo

Visit opodo.es

Key Findings

We analyzed Opodo.es page load time and found that the first response time was 367 ms and then it took 2.4 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.

Performance Metrics

opodo.es performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

18/100

25%

SI (Speed Index)

Value9.0 s

14/100

10%

TBT (Total Blocking Time)

Value9,040 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.012

100/100

15%

TTI (Time to Interactive)

Value36.2 s

0/100

10%

Network Requests Diagram

www.opodo.es

367 ms

none_variation-op_desktop.7fce00c84e14ec12907b.css

429 ms

analytics.js

23 ms

js

55 ms

tc_eDreamsODIGEO_20.js

239 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 70% of them (21 requests) were addressed to the original Opodo.es, 13% (4 requests) were made to Fonts.gstatic.com and 7% (2 requests) were made to Cdn.tagcommander.com. The less responsive or slowest element that took the longest time to load (482 ms) belongs to the original domain Opodo.es.

Page Optimization Overview & Recommendations

Page size can be reduced by 62.2 kB (12%)

Content Size

507.8 kB

After Optimization

445.6 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Opodo.es main page is 507.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Images take 242.2 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 62.0 kB

  • Original 82.3 kB
  • After minification 79.2 kB
  • After compression 20.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 62.0 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 242.2 kB
  • After minification 242.2 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

-0%

Potential reduce by 209 B

  • Original 183.3 kB
  • After minification 183.3 kB
  • After compression 183.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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 14 (61%)

Requests Now

23

After Optimization

9

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 23 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Opodo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

www.opodo.es

www.opodo.es

367 ms

none_variation-op_desktop.7fce00c84e14ec12907b.css

none_variation-op_desktop.7fce00c84e14ec12907b.css

429 ms

analytics.js

analytics.js

23 ms

js

js

55 ms

tc_eDreamsODIGEO_20.js

tc_eDreamsODIGEO_20.js

239 ms

tc_eDreamsODIGEO_21.js

tc_eDreamsODIGEO_21.js

270 ms

email-decode.min.js

email-decode.min.js

8 ms

css

css

29 ms

require.min.js

require.min.js

482 ms

marketing-channel.min.js

marketing-channel.min.js

52 ms

Opodo_logo_negative.svg

Opodo_logo_negative.svg

60 ms

track

track

242 ms

fb_button_logo.png

fb_button_logo.png

161 ms

gplus_button_logo.png

gplus_button_logo.png

453 ms

b35a55a6a16597517736.woff

b35a55a6a16597517736.woff

271 ms

footer-bg.jpg

footer-bg.jpg

432 ms

background.jpg

background.jpg

286 ms

1215260725e2a76cf650.woff

1215260725e2a76cf650.woff

318 ms

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-B4iFV0Uw.ttf

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-B4iFV0Uw.ttf

25 ms

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-NYiFV0Uw.ttf

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-NYiFV0Uw.ttf

35 ms

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-WYiFV0Uw.ttf

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-WYiFV0Uw.ttf

37 ms

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-4I-FV0Uw.ttf

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-4I-FV0Uw.ttf

35 ms

desktop.config.js

desktop.config.js

265 ms

main.js

main.js

45 ms

reactpolyfills.js

reactpolyfills.js

80 ms

es6polyfills.js

es6polyfills.js

43 ms

commonThirdParty.js

commonThirdParty.js

100 ms

desktop.react.js

desktop.react.js

137 ms

desktop.odigeo.all.js

desktop.odigeo.all.js

70 ms

index.jsp

index.jsp

300 ms

Accessibility Review

opodo.es accessibility score

86

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.es best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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.es SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

    ES

  • Language Claimed

    ES

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Opodo.es can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Opodo.es 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

opodo.es

Open Graph description is not detected on the main page of Opodo. 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: