Tools & Wizards About Us
hotelmare.pt screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 68

    SEO

    Google-friendlier than
    28% of websites

hotelmare.pt

Hotel Maré - Hotel de Charme em Nazaré, Portugal

Page Load Speed

23.3 sec in total

First Response

262 ms

Resources Loaded

22.8 sec

Page Rendered

293 ms

hotelmare.pt screenshot

About Website

Visit hotelmare.pt now to see the best up-to-date Hotel Mare content and also check out these interesting facts you probably never knew about hotelmare.pt

Hotel Maré oferece acomodação de luxo no coração de Nazaré. Desfrute de quartos elegantes, vista para o mar, e experiências únicas na Costa de Prata portuguesa.

Visit hotelmare.pt

Key Findings

We analyzed Hotelmare.pt page load time and found that the first response time was 262 ms and then it took 23.1 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 15 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

hotelmare.pt performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.9 s

4/100

10%

LCP (Largest Contentful Paint)

Value9.5 s

0/100

25%

SI (Speed Index)

Value16.8 s

0/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.1 s

41/100

10%

Network Requests Diagram

hotelmare.pt

262 ms

www.hotelmare.pt

354 ms

www.hotelmare.pt

428 ms

gtm.js

61 ms

font-awesome.min.css

50 ms

Our browser made a total of 97 requests to load all elements on the main page. We found that 89% of them (86 requests) were addressed to the original Hotelmare.pt, 6% (6 requests) were made to Maxcdn.bootstrapcdn.com and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (20.1 sec) belongs to the original domain Hotelmare.pt.

Page Optimization Overview & Recommendations

Page size can be reduced by 132.2 kB (3%)

Content Size

4.3 MB

After Optimization

4.1 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Hotelmare.pt main page is 4.3 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 4.1 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 48.5 kB

  • Original 59.1 kB
  • After minification 50.2 kB
  • After compression 10.6 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 8.9 kB, which is 15% 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 48.5 kB or 82% of the original size.

Image Optimization

-2%

Potential reduce by 82.0 kB

  • Original 4.1 MB
  • After minification 4.1 MB

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. Hotel Mare images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 1.7 kB

  • Original 67.1 kB
  • After minification 67.0 kB
  • After compression 65.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.

Requests Breakdown

Number of requests can be reduced by 11 (16%)

Requests Now

70

After Optimization

59

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hotelmare.pt

hotelmare.pt

262 ms

www.hotelmare.pt

www.hotelmare.pt

354 ms

www.hotelmare.pt

www.hotelmare.pt

428 ms

gtm.js

gtm.js

61 ms

font-awesome.min.css

font-awesome.min.css

50 ms

font-awesome.min.css

font-awesome.min.css

60 ms

bootstrap.min.css

bootstrap.min.css

81 ms

jquery.min.js

jquery.min.js

31 ms

bootstrap.min.js

bootstrap.min.js

81 ms

jquery.validate.min.js

jquery.validate.min.js

109 ms

aTools.ashx

aTools.ashx

446 ms

addthis_widget.js

addthis_widget.js

185 ms

aTools.ashx

aTools.ashx

905 ms

css

css

48 ms

aTools.ashx

aTools.ashx

792 ms

en.png

en.png

20097 ms

es.png

es.png

20097 ms

ImageGen.ashx

ImageGen.ashx

335 ms

ImageGen.ashx

ImageGen.ashx

342 ms

reserve_err_icon.png

reserve_err_icon.png

20097 ms

ImageGen.ashx

ImageGen.ashx

422 ms

ImageGen.ashx

ImageGen.ashx

428 ms

ImageGen.ashx

ImageGen.ashx

508 ms

ImageGen.ashx

ImageGen.ashx

522 ms

ImageGen.ashx

ImageGen.ashx

522 ms

ImageGen.ashx

ImageGen.ashx

587 ms

ImageGen.ashx

ImageGen.ashx

594 ms

ImageGen.ashx

ImageGen.ashx

599 ms

ImageGen.ashx

ImageGen.ashx

669 ms

ImageGen.ashx

ImageGen.ashx

676 ms

ImageGen.ashx

ImageGen.ashx

681 ms

ImageGen.ashx

ImageGen.ashx

833 ms

ImageGen.ashx

ImageGen.ashx

760 ms

ImageGen.ashx

ImageGen.ashx

765 ms

ImageGen.ashx

ImageGen.ashx

843 ms

ImageGen.ashx

ImageGen.ashx

847 ms

ImageGen.ashx

ImageGen.ashx

917 ms

ImageGen.ashx

ImageGen.ashx

928 ms

ImageGen.ashx

ImageGen.ashx

931 ms

ImageGen.ashx

ImageGen.ashx

1000 ms

ImageGen.ashx

ImageGen.ashx

1011 ms

ImageGen.ashx

ImageGen.ashx

1013 ms

newsletter_icon.png

newsletter_icon.png

20094 ms

pocentro_pt2020_feder_bom.jpg

pocentro_pt2020_feder_bom.jpg

1293 ms

uc.js

uc.js

24 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

620 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

15 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

25 ms

nunito-bold-webfont.ttf

nunito-bold-webfont.ttf

707 ms

sourcesanspro-regular-webfont.ttf

sourcesanspro-regular-webfont.ttf

794 ms

nunito-light-webfont.ttf

nunito-light-webfont.ttf

878 ms

nunito-regular-webfont.ttf

nunito-regular-webfont.ttf

893 ms

backgroundNewsletter.png

backgroundNewsletter.png

19590 ms

bx_loader.gif

bx_loader.gif

19534 ms

ui-bg_flat_100_d7d7d7_40x100.png

ui-bg_flat_100_d7d7d7_40x100.png

19534 ms

controls.png

controls.png

19534 ms

ImageGen.ashx

ImageGen.ashx

19534 ms

ImageGen.ashx

ImageGen.ashx

19535 ms

ImageGen.ashx

ImageGen.ashx

19535 ms

ImageGen.ashx

ImageGen.ashx

19535 ms

ImageGen.ashx

ImageGen.ashx

19535 ms

ImageGen.ashx

ImageGen.ashx

19512 ms

ImageGen.ashx

ImageGen.ashx

19506 ms

ImageGen.ashx

ImageGen.ashx

20110 ms

ImageGen.ashx

ImageGen.ashx

19940 ms

ImageGen.ashx

ImageGen.ashx

20019 ms

ImageGen.ashx

ImageGen.ashx

19927 ms

ImageGen.ashx

ImageGen.ashx

20023 ms

ImageGen.ashx

ImageGen.ashx

19856 ms

ImageGen.ashx

ImageGen.ashx

20025 ms

ImageGen.ashx

ImageGen.ashx

19940 ms

ImageGen.ashx

ImageGen.ashx

19940 ms

ImageGen.ashx

ImageGen.ashx

19942 ms

ImageGen.ashx

ImageGen.ashx

19868 ms

ImageGen.ashx

ImageGen.ashx

20044 ms

ImageGen.ashx

ImageGen.ashx

19965 ms

ImageGen.ashx

ImageGen.ashx

19868 ms

ImageGen.ashx

ImageGen.ashx

19882 ms

ImageGen.ashx

ImageGen.ashx

19841 ms

fontawesome-webfont.ttf

fontawesome-webfont.ttf

19747 ms

ImageGen.ashx

ImageGen.ashx

19684 ms

ImageGen.ashx

ImageGen.ashx

19691 ms

ImageGen.ashx

ImageGen.ashx

19663 ms

ImageGen.ashx

ImageGen.ashx

19651 ms

ImageGen.ashx

ImageGen.ashx

960 ms

ImageGen.ashx

ImageGen.ashx

962 ms

ImageGen.ashx

ImageGen.ashx

967 ms

ImageGen.ashx

ImageGen.ashx

978 ms

ImageGen.ashx

ImageGen.ashx

1062 ms

ImageGen.ashx

ImageGen.ashx

1059 ms

ImageGen.ashx

ImageGen.ashx

1045 ms

ImageGen.ashx

ImageGen.ashx

1062 ms

ImageGen.ashx

ImageGen.ashx

1069 ms

ImageGen.ashx

ImageGen.ashx

1076 ms

ImageGen.ashx

ImageGen.ashx

1131 ms

ImageGen.ashx

ImageGen.ashx

1148 ms

fontawesome-webfont.svg

fontawesome-webfont.svg

285 ms

Accessibility Review

hotelmare.pt accessibility score

74

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

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

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

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

hotelmare.pt 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

hotelmare.pt SEO score

68

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

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 Hotelmare.pt 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 Hotelmare.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.

Social Sharing Optimization

hotelmare.pt

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