3.9 sec in total
625 ms
3 sec
226 ms
Visit opodo.pt now to see the best up-to-date Opodo content for Portugal and also check out these interesting facts you probably never knew about opodo.pt
Ofertas de voos baratos e hotel para as tuas férias. Compara os preços de passagens aéreas e reserva a tua viagem low cost com a agência de viagens Opodo.
Visit opodo.ptWe analyzed Opodo.pt page load time and found that the first response time was 625 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
opodo.pt performance score
name
value
score
weighting
Value3.8 s
28/100
10%
Value4.1 s
48/100
25%
Value13.9 s
1/100
10%
Value45,490 ms
0/100
30%
Value0.009
100/100
15%
Value64.7 s
0/100
10%
625 ms
164 ms
168 ms
166 ms
507 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 64% of them (58 requests) were addressed to the original Opodo.pt, 8% (7 requests) were made to Tpc.googlesyndication.com and 4% (4 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (822 ms) belongs to the original domain Opodo.pt.
Page size can be reduced by 1.1 MB (56%)
2.0 MB
859.5 kB
In fact, the total size of Opodo.pt 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. 55% of websites need less resources to load. Javascripts take 784.4 kB which makes up the majority of the site volume.
Potential reduce by 254.1 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 254.1 kB or 75% of the original size.
Potential reduce by 18.7 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.
Potential reduce by 552.4 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 552.4 kB or 70% of the original size.
Potential reduce by 276.9 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.pt needs all CSS files to be minified and compressed as it can save up to 276.9 kB or 80% of the original size.
Number of requests can be reduced by 55 (65%)
84
29
The browser has sent 84 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 20 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
www.opodo.pt
625 ms
jquery.tooltip.css
164 ms
ui.datepicker.css
168 ms
jquery.autocomplete.css
166 ms
GlobalLib_V2.js
507 ms
common.js
249 ms
newsletter.js
169 ms
searchEngine.js
261 ms
global.css
261 ms
json2.js
276 ms
css-37-947399.css2
377 ms
popunder.js
258 ms
sliderHome.js
270 ms
jquery.idle-timer.js
272 ms
WebResource.axd
285 ms
dc.js
40 ms
styles.css
187 ms
searchEngine.css
205 ms
member.css
92 ms
jquery.css
88 ms
__utm.gif
12 ms
ga-audiences
40 ms
hp_bg.jpg
822 ms
logo.png
179 ms
px.gif
178 ms
voo-LIS-MIL.jpg
322 ms
voo-LIS-AMS.jpg
286 ms
ibiza.jpg
192 ms
bilbao.jpg
194 ms
flag-com.png
193 ms
flag-en.png
284 ms
flag-at.png
283 ms
flag-be.png
285 ms
flag-ch.png
378 ms
flag-de.png
383 ms
flag-dk.png
375 ms
flag-es.png
381 ms
flag-fi.png
423 ms
flag-fr.png
460 ms
flag-it.png
483 ms
flag-no.png
498 ms
flag-pt.png
515 ms
flag-se.png
520 ms
flag-pl.png
544 ms
iata.png
574 ms
gpt.js
14 ms
logo.png
586 ms
bg_menu.png
614 ms
hp_bgB.png
634 ms
bg_select.png
640 ms
hp_searchTab.png
652 ms
hp_pictos.png
673 ms
pictos.gif
692 ms
hp_buttons.png
710 ms
bg_popBaby.gif
753 ms
pubads_impl_82.js
14 ms
bg_title.png
745 ms
bg_ad.gif
738 ms
divers.png
782 ms
ads
662 ms
container.html
100 ms
383.js
176 ms
infobubble.png
644 ms
picto_calendar.gif
672 ms
hp_calendar.png
700 ms
bg_calendarT.gif
705 ms
tman.cgi
21 ms
21 ms
ps
16 ms
17 ms
pixel
18 ms
27 ms
Pug
23 ms
usersync
12 ms
demconf.jpg
8 ms
sd
9 ms
cmap
21 ms
16 ms
expansion_embed.js
27 ms
osd.js
16 ms
7287422173096533828
52 ms
abg.js
54 ms
m_js_controller.js
73 ms
googlelogo_color_112x36dp.png
37 ms
16930568692483454242
47 ms
15043252784905501025
102 ms
s
64 ms
x_button_blue2.png
51 ms
tap.php
363 ms
ui
34 ms
opodo.pt 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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
opodo.pt 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
Missing source maps for large first-party JavaScript
opodo.pt 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
PT
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Opodo.pt can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it does not match the claimed French language. Our system also found out that Opodo.pt 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.
opodo.pt
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: