Tools & Wizards About Us
odisseias.com screenshot

Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 70

    SEO

    Google-friendlier than
    30% of websites

odisseias.com

Odisseias Experiências e Presentes - Hotéis, SPA, Aventura e Restaurantes

Page Load Speed

3.5 sec in total

First Response

219 ms

Resources Loaded

2.8 sec

Page Rendered

423 ms

odisseias.com screenshot

About Website

Click here to check amazing Odisseias content for Portugal. Otherwise, check out these important facts you probably never knew about odisseias.com

Presentes de sonho e experiências únicas. Ofereça Odisseias, ofereça um voucher, um momento para viver.

Visit odisseias.com

Key Findings

We analyzed Odisseias.com page load time and found that the first response time was 219 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 60% of websites can load faster.

Performance Metrics

odisseias.com performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value8.5 s

1/100

25%

SI (Speed Index)

Value10.0 s

9/100

10%

TBT (Total Blocking Time)

Value3,120 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.223

56/100

15%

TTI (Time to Interactive)

Value18.8 s

3/100

10%

Network Requests Diagram

odisseias.com

219 ms

www.odisseias.com

219 ms

www.odisseias.com

696 ms

gtm.js

94 ms

otSDKStub.js

55 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 19% of them (14 requests) were addressed to the original Odisseias.com, 32% (23 requests) were made to Res.cloudinary.com and 7% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (814 ms) relates to the external source Res.cloudinary.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 208.0 kB (19%)

Content Size

1.1 MB

After Optimization

915.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Odisseias.com main page is 1.1 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. 70% of websites need less resources to load. Images take 580.2 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 205.1 kB

  • Original 237.4 kB
  • After minification 196.8 kB
  • After compression 32.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. This page needs HTML code to be minified as it can gain 40.6 kB, which is 17% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 205.1 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 2.4 kB

  • Original 580.2 kB
  • After minification 577.8 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. Odisseias images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 446 B

  • Original 279.8 kB
  • After minification 279.8 kB
  • After compression 279.3 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.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 26.2 kB
  • After minification 26.2 kB
  • After compression 26.2 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. Odisseias.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 38 (59%)

Requests Now

64

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

odisseias.com

odisseias.com

219 ms

www.odisseias.com

www.odisseias.com

219 ms

www.odisseias.com

www.odisseias.com

696 ms

gtm.js

gtm.js

94 ms

otSDKStub.js

otSDKStub.js

55 ms

10042823-10043760.js

10042823-10043760.js

215 ms

owlcarousel

owlcarousel

395 ms

jquery-ui-custom

jquery-ui-custom

506 ms

main_master_css

main_master_css

727 ms

odisseias.min.css

odisseias.min.css

715 ms

analytics

analytics

612 ms

ld.js

ld.js

41 ms

d35d8036-38a0-4b84-a143-7c89c47504a7.json

d35d8036-38a0-4b84-a143-7c89c47504a7.json

23 ms

location

location

134 ms

js

js

56 ms

analytics.js

analytics.js

52 ms

leadtag.js

leadtag.js

200 ms

pixel.js

pixel.js

143 ms

jquery.min.js

jquery.min.js

186 ms

main_master_js

main_master_js

406 ms

application_min_js

application_min_js

409 ms

bottomnewsletterscripts

bottomnewsletterscripts

408 ms

home_scripts_js

home_scripts_js

686 ms

lazyload_js

lazyload_js

560 ms

platform.js

platform.js

195 ms

css

css

197 ms

otBannerSdk.js

otBannerSdk.js

129 ms

rp.gif

rp.gif

52 ms

a2_etzyil8wb48l_telemetry

a2_etzyil8wb48l_telemetry

46 ms

j.php

j.php

274 ms

temos_um_presente_para_si.png

temos_um_presente_para_si.png

419 ms

odisseias_logotipo.png

odisseias_logotipo.png

422 ms

money_img.png

money_img.png

414 ms

diamante_img.png

diamante_img.png

425 ms

new_img.png

new_img.png

561 ms

gift_img.png

gift_img.png

423 ms

0456_feriasdeverao_maio_fase2_ALL_USERS_D_CHECKIN.jpg

0456_feriasdeverao_maio_fase2_ALL_USERS_D_CHECKIN.jpg

561 ms

0456_feriasdeverao_maio_fase2_ALL_USERS_M_CHECKIN.jpg

0456_feriasdeverao_maio_fase2_ALL_USERS_M_CHECKIN.jpg

423 ms

banner_top_page_2024_d_6Mai24.webp

banner_top_page_2024_d_6Mai24.webp

630 ms

banner_top_page_2024_m_6Mai24.webp

banner_top_page_2024_m_6Mai24.webp

563 ms

banner_circular_2024_hoteis_7Mai24.webp

banner_circular_2024_hoteis_7Mai24.webp

635 ms

banner_circular_2024_spa_7Mai24.webp

banner_circular_2024_spa_7Mai24.webp

635 ms

banner_circular_2024_lazer_7Mai24.webp

banner_circular_2024_lazer_7Mai24.webp

812 ms

banner_circular_2024_restaurantes_7Mai24.webp

banner_circular_2024_restaurantes_7Mai24.webp

814 ms

banner_circular_2024_aventura_7Mai24.webp

banner_circular_2024_aventura_7Mai24.webp

813 ms

banner_circular_2024_beleza_7Mai24.webp

banner_circular_2024_beleza_7Mai24.webp

762 ms

banner_widget_pesquisa_datas_horizontal_d_22Mar24.webp

banner_widget_pesquisa_datas_horizontal_d_22Mar24.webp

811 ms

syncframe

syncframe

286 ms

fbevents.js

fbevents.js

303 ms

afd6bd7c699ee.js

afd6bd7c699ee.js

301 ms

ins.js

ins.js

501 ms

collect

collect

247 ms

landing

landing

321 ms

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9a6Vc.ttf

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9a6Vc.ttf

315 ms

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyAaBO9a6Vc.ttf

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyAaBO9a6Vc.ttf

390 ms

odisseias_icon.ttf

odisseias_icon.ttf

321 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

517 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

572 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

573 ms

p53751.js

p53751.js

327 ms

destination

destination

116 ms

v.gif

v.gif

79 ms

tag-f27920e8127c636f988deb777d3577e5.js

tag-f27920e8127c636f988deb777d3577e5.js

267 ms

banner_home_vantagens_2023_v4_desktop.png

banner_home_vantagens_2023_v4_desktop.png

389 ms

banner_questionario_de_verao_2024_d.webp

banner_questionario_de_verao_2024_d.webp

496 ms

md5.min.js

md5.min.js

150 ms

settings.js

settings.js

62 ms

banner_presentes_para_ajudar_home_d.jpg

banner_presentes_para_ajudar_home_d.jpg

115 ms

banner_bottom_site_lojasolidaria.jpg

banner_bottom_site_lojasolidaria.jpg

129 ms

banner_bottom_site_topdestinos.jpg

banner_bottom_site_topdestinos.jpg

136 ms

banner_bottom_site_instagram.jpg

banner_bottom_site_instagram.jpg

112 ms

banner_bottom_site_facebook.jpg

banner_bottom_site_facebook.jpg

112 ms

event

event

344 ms

Accessibility Review

odisseias.com accessibility score

85

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

odisseias.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

odisseias.com SEO score

70

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

High

robots.txt is not valid

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    PT

  • Encoding

    UTF-8

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

odisseias.com

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