Tools & Wizards About Us
imperialamador.com screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

imperialamador.com

Imperial Hotel

Page Load Speed

1.6 sec in total

First Response

85 ms

Resources Loaded

1.3 sec

Page Rendered

168 ms

imperialamador.com screenshot

About Website

Visit imperialamador.com now to see the best up-to-date Imperial Amador content and also check out these interesting facts you probably never knew about imperialamador.com

Visit imperialamador.com

Key Findings

We analyzed Imperialamador.com page load time and found that the first response time was 85 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

imperialamador.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

37/100

10%

LCP (Largest Contentful Paint)

Value15.2 s

0/100

25%

SI (Speed Index)

Value10.8 s

7/100

10%

TBT (Total Blocking Time)

Value6,210 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.033

100/100

15%

TTI (Time to Interactive)

Value22.1 s

1/100

10%

Network Requests Diagram

www.imperialhotelamador.com

85 ms

6NubIwJ8W7KSQBT8sZxTGMCXPWeu1_k-FwyriRh8Q8IfenCIfFHN4UJLFRbh52jhWDjDF2gyZAZ8FQjuFQyKwA9oFRsRw28KjU7GMkG0jAFu-WsoShFGZAsude80ZkoRdhXCHKoyjamTiY8Djhy8ZYmC-Ao1Oco8if37OcB3Sc8RdabljW4uZamCjPuDS2woO1FUiABkZWF3jAF8OcFzdP37OcBDOcu8OfG0SaBujW48SagyjhmDjhy8ZYmC-Ao1OcFzdPUyjamTiY8Djhy8ZYmC-Ao1OcFzdPUyjamTiY8Djhy8ZYmC-Ao1Oco8ifUySY4TjhNXOABkiAiudeIlSaMD5PoDSWmyScmDSeBRZPoRdhXCjWw0dA9C-Au3ZW4TjAUGdas8deBljAszSKoRdhXCdeNRjAUGdaFXOYFUiABkZWF3jAF8ShFGZAsude80ZkoRdhXCiaiaOcBRiA8XpWFR-emqiAUTdcS0jhNlOYiaikoyjamTiY8Djhy8ZYmC-Ao1Oco8ifUaiaS0jWgk-AFzifuyS1m1iAUyOWF3wDq0SaBujW48Sagyjh90jhNlOYiaikoySkolZPUaiaS0-Au3ZW4TjAUGdas8deBljAszSKoRdhXCiaiaO1FUiABkZWF3jAF8ShFGZAsude80ZkoRdhXKfhNkSey8iWwlSY4zJy80ZWm8OAyyjWwlZa4ziemD-kuq-WF3deBoH6GJE_tgIMMjgfMfH6GJujXfIMMjgPMfH6GJEdtgIMMjgkMfH6GJEntgIMMj2KMfH6GJkObfIMIjgPMfqMe7loHyg6.js

53 ms

legacy.js

45 ms

modern.js

62 ms

extract-css-runtime-7ab3a573e3fc54c5b534-min.en-US.js

50 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Imperialamador.com, 15% (10 requests) were made to Use.typekit.net and 13% (9 requests) were made to Assets.squarespace.com. The less responsive or slowest element that took the longest time to load (789 ms) relates to the external source Images.squarespace-cdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 615.3 kB (2%)

Content Size

28.5 MB

After Optimization

27.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Imperialamador.com main page is 28.5 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. Only a small number of websites need less resources to load. Images take 27.1 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 293.8 kB

  • Original 326.5 kB
  • After minification 293.2 kB
  • After compression 32.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 293.8 kB or 90% of the original size.

Image Optimization

-1%

Potential reduce by 313.2 kB

  • Original 27.1 MB
  • After minification 26.8 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. Imperial Amador images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 5.2 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 1.1 MB

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

-17%

Potential reduce by 3.1 kB

  • Original 18.7 kB
  • After minification 18.7 kB
  • After compression 15.6 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. Imperialamador.com needs all CSS files to be minified and compressed as it can save up to 3.1 kB or 17% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (21%)

Requests Now

57

After Optimization

45

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.imperialhotelamador.com

www.imperialhotelamador.com

85 ms

6NubIwJ8W7KSQBT8sZxTGMCXPWeu1_k-FwyriRh8Q8IfenCIfFHN4UJLFRbh52jhWDjDF2gyZAZ8FQjuFQyKwA9oFRsRw28KjU7GMkG0jAFu-WsoShFGZAsude80ZkoRdhXCHKoyjamTiY8Djhy8ZYmC-Ao1Oco8if37OcB3Sc8RdabljW4uZamCjPuDS2woO1FUiABkZWF3jAF8OcFzdP37OcBDOcu8OfG0SaBujW48SagyjhmDjhy8ZYmC-Ao1OcFzdPUyjamTiY8Djhy8ZYmC-Ao1OcFzdPUyjamTiY8Djhy8ZYmC-Ao1Oco8ifUySY4TjhNXOABkiAiudeIlSaMD5PoDSWmyScmDSeBRZPoRdhXCjWw0dA9C-Au3ZW4TjAUGdas8deBljAszSKoRdhXCdeNRjAUGdaFXOYFUiABkZWF3jAF8ShFGZAsude80ZkoRdhXCiaiaOcBRiA8XpWFR-emqiAUTdcS0jhNlOYiaikoyjamTiY8Djhy8ZYmC-Ao1Oco8ifUaiaS0jWgk-AFzifuyS1m1iAUyOWF3wDq0SaBujW48Sagyjh90jhNlOYiaikoySkolZPUaiaS0-Au3ZW4TjAUGdas8deBljAszSKoRdhXCiaiaO1FUiABkZWF3jAF8ShFGZAsude80ZkoRdhXKfhNkSey8iWwlSY4zJy80ZWm8OAyyjWwlZa4ziemD-kuq-WF3deBoH6GJE_tgIMMjgfMfH6GJujXfIMMjgPMfH6GJEdtgIMMjgkMfH6GJEntgIMMj2KMfH6GJkObfIMIjgPMfqMe7loHyg6.js

6NubIwJ8W7KSQBT8sZxTGMCXPWeu1_k-FwyriRh8Q8IfenCIfFHN4UJLFRbh52jhWDjDF2gyZAZ8FQjuFQyKwA9oFRsRw28KjU7GMkG0jAFu-WsoShFGZAsude80ZkoRdhXCHKoyjamTiY8Djhy8ZYmC-Ao1Oco8if37OcB3Sc8RdabljW4uZamCjPuDS2woO1FUiABkZWF3jAF8OcFzdP37OcBDOcu8OfG0SaBujW48SagyjhmDjhy8ZYmC-Ao1OcFzdPUyjamTiY8Djhy8ZYmC-Ao1OcFzdPUyjamTiY8Djhy8ZYmC-Ao1Oco8ifUySY4TjhNXOABkiAiudeIlSaMD5PoDSWmyScmDSeBRZPoRdhXCjWw0dA9C-Au3ZW4TjAUGdas8deBljAszSKoRdhXCdeNRjAUGdaFXOYFUiABkZWF3jAF8ShFGZAsude80ZkoRdhXCiaiaOcBRiA8XpWFR-emqiAUTdcS0jhNlOYiaikoyjamTiY8Djhy8ZYmC-Ao1Oco8ifUaiaS0jWgk-AFzifuyS1m1iAUyOWF3wDq0SaBujW48Sagyjh90jhNlOYiaikoySkolZPUaiaS0-Au3ZW4TjAUGdas8deBljAszSKoRdhXCiaiaO1FUiABkZWF3jAF8ShFGZAsude80ZkoRdhXKfhNkSey8iWwlSY4zJy80ZWm8OAyyjWwlZa4ziemD-kuq-WF3deBoH6GJE_tgIMMjgfMfH6GJujXfIMMjgPMfH6GJEdtgIMMjgkMfH6GJEntgIMMj2KMfH6GJkObfIMIjgPMfqMe7loHyg6.js

53 ms

legacy.js

legacy.js

45 ms

modern.js

modern.js

62 ms

extract-css-runtime-7ab3a573e3fc54c5b534-min.en-US.js

extract-css-runtime-7ab3a573e3fc54c5b534-min.en-US.js

50 ms

extract-css-moment-js-vendor-6c569122bfa66a51a056-min.en-US.js

extract-css-moment-js-vendor-6c569122bfa66a51a056-min.en-US.js

75 ms

cldr-resource-pack-e85130cf44bc2d365b8b-min.en-US.js

cldr-resource-pack-e85130cf44bc2d365b8b-min.en-US.js

68 ms

common-vendors-stable-b03dd66b7c78e5e40bc7-min.en-US.js

common-vendors-stable-b03dd66b7c78e5e40bc7-min.en-US.js

75 ms

common-vendors-7598f4eb50a2ef12b555-min.en-US.js

common-vendors-7598f4eb50a2ef12b555-min.en-US.js

174 ms

common-c7ec25718250fde6b042-min.en-US.js

common-c7ec25718250fde6b042-min.en-US.js

176 ms

performance-eb022691e09e39c54c48-min.en-US.js

performance-eb022691e09e39c54c48-min.en-US.js

172 ms

site.css

site.css

74 ms

static.css

static.css

72 ms

site-bundle.5ba448b7aa80223d4688bd176bcb7afb.js

site-bundle.5ba448b7aa80223d4688bd176bcb7afb.js

152 ms

Imperial-Hotel-Mini-Logo_outline_wht_fnl.png

Imperial-Hotel-Mini-Logo_outline_wht_fnl.png

202 ms

widget.js

widget.js

320 ms

photo0.jpeg

photo0.jpeg

159 ms

DSC06062.JPG

DSC06062.JPG

181 ms

DSC06699.JPG

DSC06699.JPG

178 ms

DSC07753.JPG

DSC07753.JPG

179 ms

DSC07645.JPG

DSC07645.JPG

177 ms

DSC01302.JPG

DSC01302.JPG

405 ms

DSC07701.JPG

DSC07701.JPG

179 ms

DSC07809.JPG

DSC07809.JPG

182 ms

DSC07839.JPG

DSC07839.JPG

492 ms

8B4CA7D5-3324-418B-9D40-7293FD2174AE.jpeg

8B4CA7D5-3324-418B-9D40-7293FD2174AE.jpeg

183 ms

DSC07876.JPG

DSC07876.JPG

434 ms

DSC08575.JPG

DSC08575.JPG

412 ms

DSC07868.JPG

DSC07868.JPG

187 ms

DSC07872.JPG

DSC07872.JPG

449 ms

DSC08165.JPG

DSC08165.JPG

463 ms

BCDF9FDA-1D97-4D31-A962-0AA5FC1B71D4+%281%29.jpeg

BCDF9FDA-1D97-4D31-A962-0AA5FC1B71D4+%281%29.jpeg

410 ms

DSC08216.JPG

DSC08216.JPG

416 ms

DSC08471.JPG

DSC08471.JPG

415 ms

DSC06227.JPG

DSC06227.JPG

419 ms

DSC07896.JPG

DSC07896.JPG

424 ms

DSC07902.JPG

DSC07902.JPG

425 ms

DSC07966.JPG

DSC07966.JPG

657 ms

DSC00936.JPG

DSC00936.JPG

429 ms

DSC06435.JPG

DSC06435.JPG

433 ms

DSC06456.JPG

DSC06456.JPG

438 ms

DSC06464.JPG

DSC06464.JPG

438 ms

DSC06670.JPG

DSC06670.JPG

444 ms

DSC01273.JPG

DSC01273.JPG

633 ms

DSC07824.JPG

DSC07824.JPG

449 ms

DSC08153.JPG

DSC08153.JPG

637 ms

DSC00967.JPG

DSC00967.JPG

452 ms

DSC07085.JPG

DSC07085.JPG

460 ms

Screen+Shot+2023-03-27+at+10.31.01+PM.png

Screen+Shot+2023-03-27+at+10.31.01+PM.png

789 ms

DSC01291.JPG

DSC01291.JPG

464 ms

DSC06107.JPG

DSC06107.JPG

471 ms

i

i

42 ms

i

i

12 ms

i

i

12 ms

i

i

18 ms

i

i

19 ms

i

i

34 ms

i

i

36 ms

i

i

36 ms

i

i

35 ms

C45D8869-FD61-4819-988B-D3682765A86F+%281%29.jpeg

C45D8869-FD61-4819-988B-D3682765A86F+%281%29.jpeg

552 ms

DSC07681.JPG

DSC07681.JPG

742 ms

DSC03101.JPG

DSC03101.JPG

464 ms

DSC06991.JPG

DSC06991.JPG

668 ms

DSC06993.JPG

DSC06993.JPG

469 ms

DSC02385.jpg

DSC02385.jpg

472 ms

widget_app_1725367019229.js

widget_app_1725367019229.js

21 ms

Accessibility Review

imperialamador.com accessibility score

100

Accessibility Issues

Best Practices

imperialamador.com best practices score

92

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

Page has valid source maps

SEO Factors

imperialamador.com SEO score

93

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

imperialamador.com

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