Tools & Wizards About Us
windsortower.com screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

windsortower.com

Windsor Hotel & Tower

Page Load Speed

3.9 sec in total

First Response

869 ms

Resources Loaded

2.8 sec

Page Rendered

237 ms

windsortower.com screenshot

About Website

Click here to check amazing Windsor Tower content. Otherwise, check out these important facts you probably never knew about windsortower.com

Visit windsortower.com

Key Findings

We analyzed Windsortower.com page load time and found that the first response time was 869 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

windsortower.com performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value23.0 s

0/100

25%

SI (Speed Index)

Value23.4 s

0/100

10%

TBT (Total Blocking Time)

Value800 ms

36/100

30%

CLS (Cumulative Layout Shift)

Value0.36

30/100

15%

TTI (Time to Interactive)

Value28.6 s

0/100

10%

Network Requests Diagram

windsortower.com

869 ms

calendario.css

276 ms

style.css

132 ms

jquery.min.js

56 ms

calendario.js

397 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 60% of them (55 requests) were addressed to the original Windsortower.com, 13% (12 requests) were made to Static.tacdn.com and 5% (5 requests) were made to Tripadvisor.es. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Afip.gob.ar.

Page Optimization Overview & Recommendations

Page size can be reduced by 285.3 kB (42%)

Content Size

672.3 kB

After Optimization

386.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-73%

Potential reduce by 27.9 kB

  • Original 38.3 kB
  • After minification 35.7 kB
  • After compression 10.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 27.9 kB or 73% of the original size.

Image Optimization

-14%

Potential reduce by 53.2 kB

  • Original 375.1 kB
  • After minification 321.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. Obviously, Windsor Tower needs image optimization as it can save up to 53.2 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-79%

Potential reduce by 179.1 kB

  • Original 227.3 kB
  • After minification 179.8 kB
  • After compression 48.2 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 179.1 kB or 79% of the original size.

CSS Optimization

-79%

Potential reduce by 25.0 kB

  • Original 31.6 kB
  • After minification 24.5 kB
  • After compression 6.5 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. Windsortower.com needs all CSS files to be minified and compressed as it can save up to 25.0 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (41%)

Requests Now

85

After Optimization

50

  • Images
  • JavaScript
  • CSS

The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Windsor Tower. 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 from 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

windsortower.com

windsortower.com

869 ms

calendario.css

calendario.css

276 ms

style.css

style.css

132 ms

jquery.min.js

jquery.min.js

56 ms

calendario.js

calendario.js

397 ms

SpryEffects.js

SpryEffects.js

473 ms

AC_RunActiveContent.js

AC_RunActiveContent.js

78 ms

reveal.css

reveal.css

138 ms

jquery.reveal.js

jquery.reveal.js

200 ms

wejs

wejs

84 ms

wejs

wejs

84 ms

wejs

wejs

86 ms

wejs

wejs

99 ms

Stacked_TA_logo.png

Stacked_TA_logo.png

68 ms

DATAWEB.jpg

DATAWEB.jpg

1348 ms

tripadvisor_logo_115x18.gif

tripadvisor_logo_115x18.gif

22 ms

fondo.jpg

fondo.jpg

152 ms

01-semana-santa.jpg

01-semana-santa.jpg

154 ms

02-semana-santa.jpg

02-semana-santa.jpg

97 ms

1.png

1.png

153 ms

17.jpg

17.jpg

196 ms

13.jpg

13.jpg

152 ms

18.jpg

18.jpg

188 ms

ico_calendario.gif

ico_calendario.gif

219 ms

bot_continuar_es.gif

bot_continuar_es.gif

219 ms

1.jpg

1.jpg

219 ms

3.jpg

3.jpg

239 ms

5.jpg

5.jpg

255 ms

7.jpg

7.jpg

273 ms

9.jpg

9.jpg

287 ms

11.jpg

11.jpg

284 ms

PROMOt001.jpg

PROMOt001.jpg

295 ms

19.jpg

19.jpg

307 ms

GALERIA001.jpg

GALERIA001.jpg

328 ms

20B.jpg

20B.jpg

336 ms

images.jpg

images.jpg

462 ms

21.jpg

21.jpg

366 ms

14.jpg

14.jpg

377 ms

29.jpg

29.jpg

383 ms

Sibaris_banner_web_windsor.jpg

Sibaris_banner_web_windsor.jpg

417 ms

widget_facebook.png

widget_facebook.png

399 ms

banner-acumula-kms-lanpass.png

banner-acumula-kms-lanpass.png

461 ms

3.png

3.png

474 ms

5.png

5.png

475 ms

7.png

7.png

477 ms

9.png

9.png

482 ms

2.png

2.png

534 ms

20x28_green-21693-2.png

20x28_green-21693-2.png

49 ms

CoE2015_WidgetAsset-14348-2.png

CoE2015_WidgetAsset-14348-2.png

76 ms

15.jpg

15.jpg

507 ms

22.jpg

22.jpg

528 ms

WidgetEmbed-cdsscrollingravenarrow

WidgetEmbed-cdsscrollingravenarrow

63 ms

cdswidget-scrollingrave-v2823050010a.css%20%27%29%3B

cdswidget-scrollingrave-v2823050010a.css%20%27%29%3B

2 ms

cdswidgets_min-c-v23892882724a.js

cdswidgets_min-c-v23892882724a.js

48 ms

cdswidget-scrollingrave-v2823050010a.css

cdswidget-scrollingrave-v2823050010a.css

43 ms

WidgetEmbed-certificateOfExcellence

WidgetEmbed-certificateOfExcellence

20 ms

cdswidCOE-v21462574883a.css%20%27%29%3B

cdswidCOE-v21462574883a.css%20%27%29%3B

1 ms

cdswidFRR-v23865805545a.css%20%27%29%3B

cdswidFRR-v23865805545a.css%20%27%29%3B

2 ms

cdswidCOE-v21462574883a.css

cdswidCOE-v21462574883a.css

3 ms

cdswidFRR-v23865805545a.css

cdswidFRR-v23865805545a.css

16 ms

WidgetEmbed-excellent

WidgetEmbed-excellent

23 ms

cdswidEXC-v22775008216a.css%20%27%29%3B

cdswidEXC-v22775008216a.css%20%27%29%3B

1 ms

cdswidEXC-v22775008216a.css

cdswidEXC-v22775008216a.css

3 ms

WidgetEmbed-socialButtonBubbles

WidgetEmbed-socialButtonBubbles

18 ms

cdswidSOCIAL-v21186289283a.css%20%27%29%3B

cdswidSOCIAL-v21186289283a.css%20%27%29%3B

2 ms

cdswidgets_m-c-v2102084671a.js

cdswidgets_m-c-v2102084671a.js

3 ms

cdswidSOCIAL-v21186289283a.css

cdswidSOCIAL-v21186289283a.css

4 ms

analytics.js

analytics.js

10 ms

modal-gloss.png

modal-gloss.png

308 ms

collect

collect

12 ms

2.jpg

2.jpg

97 ms

Stacked_TA_logo.png

Stacked_TA_logo.png

23 ms

transparent_pixel-17198-2.gif

transparent_pixel-17198-2.gif

23 ms

CoE2015_WidgetAsset-14348-2.png

CoE2015_WidgetAsset-14348-2.png

22 ms

BackgroundRuleBlack.gif

BackgroundRuleBlack.gif

11 ms

tripadvisor_logo_115x18.gif

tripadvisor_logo_115x18.gif

10 ms

ss4.5.gif

ss4.5.gif

10 ms

grayArrowLeft.gif

grayArrowLeft.gif

10 ms

4.jpg

4.jpg

87 ms

6.jpg

6.jpg

105 ms

8.jpg

8.jpg

90 ms

10.jpg

10.jpg

94 ms

12.jpg

12.jpg

91 ms

4.png

4.png

146 ms

6.png

6.png

152 ms

8.png

8.png

155 ms

10.png

10.png

163 ms

PROMOt001b.jpg

PROMOt001b.jpg

170 ms

GALERIA001b.jpg

GALERIA001b.jpg

183 ms

imagesb.jpg

imagesb.jpg

216 ms

20x28_green-21693-2.png

20x28_green-21693-2.png

11 ms

transparent_pixel-11863-2.gif

transparent_pixel-11863-2.gif

8 ms

Accessibility Review

windsortower.com accessibility score

79

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

windsortower.com best practices score

67

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

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

windsortower.com SEO score

83

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

Image elements do not have [alt] attributes

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

    ES

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Windsortower.com can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Windsortower.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

windsortower.com

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