Tools & Wizards About Us
hardrockhotelorlando.com screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

hardrockhotelorlando.com

Orlando Resorts | Hard Rock Hotel Orlando

Page Load Speed

3.2 sec in total

First Response

63 ms

Resources Loaded

2.5 sec

Page Rendered

582 ms

hardrockhotelorlando.com screenshot

About Website

Welcome to hardrockhotelorlando.com homepage info - get ready to check Hard Rock Hotel Orlando best content for United States right away, or after learning these important things about hardrockhotelorlando.com

Vacation to your own beat at Hard Rock Hotel Orlando, offering electric hotel rooms with music-inspired details minutes from your favorite theme parks.

Visit hardrockhotelorlando.com

Key Findings

We analyzed Hardrockhotelorlando.com page load time and found that the first response time was 63 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

hardrockhotelorlando.com performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

58/100

10%

LCP (Largest Contentful Paint)

Value4.5 s

36/100

25%

SI (Speed Index)

Value5.2 s

59/100

10%

TBT (Total Blocking Time)

Value1,210 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0.05

99/100

15%

TTI (Time to Interactive)

Value14.6 s

8/100

10%

Network Requests Diagram

hardrockhotelorlando.com

63 ms

www.hardrockhotelorlando.com

125 ms

orlando

78 ms

88 ms

combined.css

112 ms

Our browser made a total of 104 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Hardrockhotelorlando.com, 57% (59 requests) were made to Hardrockhotels.com and 8% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (873 ms) relates to the external source Hardrockhotels.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 923.2 kB (32%)

Content Size

2.9 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hardrockhotelorlando.com main page is 2.9 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 60.6 kB

  • Original 78.2 kB
  • After minification 72.5 kB
  • After compression 17.5 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 60.6 kB or 78% of the original size.

Image Optimization

-5%

Potential reduce by 87.4 kB

  • Original 1.8 MB
  • After minification 1.7 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. Hard Rock Hotel Orlando images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 554.1 kB

  • Original 762.1 kB
  • After minification 725.9 kB
  • After compression 208.0 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 554.1 kB or 73% of the original size.

CSS Optimization

-85%

Potential reduce by 221.1 kB

  • Original 260.7 kB
  • After minification 257.3 kB
  • After compression 39.7 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. Hardrockhotelorlando.com needs all CSS files to be minified and compressed as it can save up to 221.1 kB or 85% of the original size.

Requests Breakdown

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

Requests Now

93

After Optimization

55

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hardrockhotelorlando.com

hardrockhotelorlando.com

63 ms

www.hardrockhotelorlando.com

www.hardrockhotelorlando.com

125 ms

orlando

orlando

78 ms

88 ms

combined.css

combined.css

112 ms

combined.js

combined.js

231 ms

all.js

all.js

419 ms

plusone.js

plusone.js

64 ms

satelliteLib-7b0f5b736b1bc7475d3eb2fda42c6845eb03bfaf.js

satelliteLib-7b0f5b736b1bc7475d3eb2fda42c6845eb03bfaf.js

101 ms

jsapi

jsapi

29 ms

js

js

53 ms

font-awesome.min.css

font-awesome.min.css

30 ms

combined.css

combined.css

136 ms

combined.js

combined.js

118 ms

VisitorInformation.aspx

VisitorInformation.aspx

77 ms

embed.js

embed.js

88 ms

s_code.js

s_code.js

56 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

16 ms

mbox-contents-152af745f022aa0b35a559d60d8300dc872e42c0.js

mbox-contents-152af745f022aa0b35a559d60d8300dc872e42c0.js

39 ms

satellite-554390443134620017430000.js

satellite-554390443134620017430000.js

76 ms

s-code-contents-5a13775ea5c8b17b23cca8d2c08766a50bde69df.js

s-code-contents-5a13775ea5c8b17b23cca8d2c08766a50bde69df.js

86 ms

115 ms

9_2.gif

9_2.gif

870 ms

cal1.gif

cal1.gif

94 ms

@2xlogo.png

@2xlogo.png

51 ms

Exterior-Header.jpg

Exterior-Header.jpg

873 ms

Kids-Header.jpg

Kids-Header.jpg

154 ms

Pool-header.jpg

Pool-header.jpg

418 ms

Morris_Day_flex_-_Long2.jpg

Morris_Day_flex_-_Long2.jpg

664 ms

UOR_logo11.gif

UOR_logo11.gif

61 ms

kidswimming.jpg

kidswimming.jpg

92 ms

SoundStay-SM.jpg

SoundStay-SM.jpg

125 ms

AAA_4_Diamond.png

AAA_4_Diamond.png

108 ms

destinationsDownArrow.png

destinationsDownArrow.png

93 ms

1-1X1.JPG

1-1X1.JPG

16 ms

logoBg.png

logoBg.png

370 ms

shareIcon.png

shareIcon.png

102 ms

firstevent

firstevent

31 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

30 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

132 ms

TheSans_TT5_.woff

TheSans_TT5_.woff

167 ms

TheSans_TT5_.svg

TheSans_TT5_.svg

165 ms

TheSans_TT5_Caps.woff

TheSans_TT5_Caps.woff

355 ms

TheSans_TT5_Caps.svg

TheSans_TT5_Caps.svg

356 ms

widgets.js

widgets.js

6 ms

iconsSm.png

iconsSm.png

333 ms

navBg.png

navBg.png

335 ms

iconHome.png

iconHome.png

335 ms

navDivider.png

navDivider.png

335 ms

headerOverlay.png

headerOverlay.png

322 ms

drsbBg.jpg

drsbBg.jpg

323 ms

ctaPhoto.png

ctaPhoto.png

323 ms

calBg.png

calBg.png

303 ms

bgHome.jpg

bgHome.jpg

302 ms

footerBgNew.jpg

footerBgNew.jpg

303 ms

h1Bg.png

h1Bg.png

304 ms

anchorButton.png

anchorButton.png

304 ms

bullet.png

bullet.png

302 ms

ctaBg.jpg

ctaBg.jpg

305 ms

TheSans_TT3_.woff

TheSans_TT3_.woff

302 ms

TheSans_TT3_.svg

TheSans_TT3_.svg

303 ms

s64747051803860

s64747051803860

59 ms

newsBg.jpg

newsBg.jpg

295 ms

newsIcon.png

newsIcon.png

297 ms

21 ms

default+en.css

default+en.css

6 ms

default+en.I.js

default+en.I.js

21 ms

eventsIcon.png

eventsIcon.png

242 ms

instagram.png

instagram.png

219 ms

bg80.png

bg80.png

212 ms

logoSm.png

logoSm.png

213 ms

satellite-55a0089664383000170000ab.js

satellite-55a0089664383000170000ab.js

196 ms

xd_arbiter.php

xd_arbiter.php

230 ms

xd_arbiter.php

xd_arbiter.php

437 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

51 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

27 ms

fastbutton

fastbutton

125 ms

linkArrow.png

linkArrow.png

41 ms

instruction_arrows.png

instruction_arrows.png

42 ms

selectBG.png

selectBG.png

51 ms

selectArrowDown.png

selectArrowDown.png

42 ms

bg90.png

bg90.png

43 ms

anchorButtonFooter.png

anchorButtonFooter.png

43 ms

s66355170309543

s66355170309543

22 ms

postmessageRelay

postmessageRelay

50 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

19 ms

print.css

print.css

38 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

42 ms

rpc:shindig_random.js

rpc:shindig_random.js

40 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

21 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

19 ms

like.php

like.php

103 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

7 ms

pJeswbKZO4XwVR0035gpgvesZW2xOQ-xsNqO47m55DA.ttf

pJeswbKZO4XwVR0035gpgvesZW2xOQ-xsNqO47m55DA.ttf

19 ms

jot

jot

78 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

487 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

549 ms

sliderNav.png

sliderNav.png

29 ms

dest4.html

dest4.html

17 ms

sliderPrev.png

sliderPrev.png

37 ms

sliderNext.png

sliderNext.png

36 ms

arrowPrev.png

arrowPrev.png

36 ms

arrowNext.png

arrowNext.png

37 ms

gr

gr

8 ms

Accessibility Review

hardrockhotelorlando.com accessibility score

90

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

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

Links do not have a discernible name

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

hardrockhotelorlando.com best practices score

83

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

SEO Factors

hardrockhotelorlando.com SEO score

82

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

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hardrockhotelorlando.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 Hardrockhotelorlando.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

hardrockhotelorlando.com

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