Tools & Wizards About Us
renaissancenashville.com screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 74

    SEO

    Google-friendlier than
    31% of websites

renaissancenashville.com

Nashville Hotels, Downtown | Renaissance Nashville Hotel

Page Load Speed

6.4 sec in total

First Response

63 ms

Resources Loaded

4.7 sec

Page Rendered

1.6 sec

renaissancenashville.com screenshot

About Website

Welcome to renaissancenashville.com homepage info - get ready to check Renaissance Nashville best content right away, or after learning these important things about renaissancenashville.com

Renaissance Nashville Hotel welcomes you to Tennessee. Our luxury hotel in downtown Nashville contains modern, stylish accommodations and superb amenities. Book your stay with us and enjoy our downtow...

Visit renaissancenashville.com

Key Findings

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

Performance Metrics

renaissancenashville.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value27.6 s

0/100

25%

SI (Speed Index)

Value37.0 s

0/100

10%

TBT (Total Blocking Time)

Value31,220 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.047

99/100

15%

TTI (Time to Interactive)

Value70.2 s

0/100

10%

Network Requests Diagram

renaissancenashville.com

63 ms

www.renaissancenashville.com

103 ms

475 ms

marriottCommon.js

70 ms

6e15e9b645406f938b23f5e9f0ee55b0f0aafa2feb045

256 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 5% of them (2 requests) were addressed to the original Renaissancenashville.com, 65% (24 requests) were made to Marriott.com and 24% (9 requests) were made to Cache.marriott.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Marriott.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (33%)

Content Size

4.1 MB

After Optimization

2.7 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Renaissancenashville.com main page is 4.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. 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 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 252.8 kB

  • Original 298.6 kB
  • After minification 251.6 kB
  • After compression 45.8 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 47.0 kB, which is 16% 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 252.8 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 612 B

  • Original 2.3 MB
  • After minification 2.3 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. Renaissance Nashville images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 1.1 MB

  • Original 1.5 MB
  • After minification 1.5 MB
  • After compression 386.8 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 1.1 MB or 74% of the original size.

Requests Breakdown

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

Requests Now

29

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

renaissancenashville.com

renaissancenashville.com

63 ms

www.renaissancenashville.com

www.renaissancenashville.com

103 ms

475 ms

marriottCommon.js

marriottCommon.js

70 ms

6e15e9b645406f938b23f5e9f0ee55b0f0aafa2feb045

6e15e9b645406f938b23f5e9f0ee55b0f0aafa2feb045

256 ms

ruxitagentjs_ICA7NQVfhqrux_10297240712040816.js

ruxitagentjs_ICA7NQVfhqrux_10297240712040816.js

30 ms

datalayer

datalayer

1019 ms

clientlib-base.min.569a20d572bd560535b3c0a54ddfbdfc.css

clientlib-base.min.569a20d572bd560535b3c0a54ddfbdfc.css

24 ms

clientlib-firstpaint.min.bb64ce684b6fb201696bfd41bad85797.css

clientlib-firstpaint.min.bb64ce684b6fb201696bfd41bad85797.css

40 ms

clientlib-firstpaint.min.bdced2ea2ca43b0566b32eada99e1dd8.js

clientlib-firstpaint.min.bdced2ea2ca43b0566b32eada99e1dd8.js

82 ms

clientlib-sitev2.min.57596c3dee58a2cb4aa791b7234c8603.css

clientlib-sitev2.min.57596c3dee58a2cb4aa791b7234c8603.css

63 ms

clientlib-bptv2.min.6a93c126f91048bd5ccdf33be8a22570.css

clientlib-bptv2.min.6a93c126f91048bd5ccdf33be8a22570.css

89 ms

clientlibs.d317a5d9bbba6e3a517179296858ca98.css

clientlibs.d317a5d9bbba6e3a517179296858ca98.css

120 ms

clientlib-hws-jquery.min.4709cf7b87b5f9ad6240b012a8445143.js

clientlib-hws-jquery.min.4709cf7b87b5f9ad6240b012a8445143.js

92 ms

launch-EN1ce795381cea451fa40478e502ecce2f.min.js

launch-EN1ce795381cea451fa40478e502ecce2f.min.js

43 ms

clientlibs.min.d317a5d9bbba6e3a517179296858ca98.css

clientlibs.min.d317a5d9bbba6e3a517179296858ca98.css

106 ms

clientlibs.min.16e9cd6e528138d85421b96b2b5a36a5.js

clientlibs.min.16e9cd6e528138d85421b96b2b5a36a5.js

110 ms

clientlibs.16e9cd6e528138d85421b96b2b5a36a5.js

clientlibs.16e9cd6e528138d85421b96b2b5a36a5.js

113 ms

clientlib-base.min.97809428e8a7697927b484e808804291.js

clientlib-base.min.97809428e8a7697927b484e808804291.js

122 ms

clientlib-sitev2.min.16be20fd861cdd619f71e43bdc2d0ce4.js

clientlib-sitev2.min.16be20fd861cdd619f71e43bdc2d0ce4.js

467 ms

clientlib-bptv2.min.e4b31a7e590b2e0ed56bd249b275b15c.js

clientlib-bptv2.min.e4b31a7e590b2e0ed56bd249b275b15c.js

136 ms

bundle.js

bundle.js

135 ms

bv.js

bv.js

17 ms

EVhMgJzs

EVhMgJzs

133 ms

marriottCommon.js

marriottCommon.js

267 ms

br_logo_L.png

br_logo_L.png

332 ms

br-bnash-the-club-lounge-33157:Classic-Hor

br-bnash-the-club-lounge-33157:Classic-Hor

999 ms

bnash-attraction-broad-5508-hor-clsc.jpg

bnash-attraction-broad-5508-hor-clsc.jpg

533 ms

bnash-sobro-1970-hor-clsc.jpg

bnash-sobro-1970-hor-clsc.jpg

531 ms

br-bnash-rh_bnash_fifthbroad_resta-25174-wide-hor.jpg

br-bnash-rh_bnash_fifthbroad_resta-25174-wide-hor.jpg

767 ms

Swiss721BT-Medium.woff

Swiss721BT-Medium.woff

391 ms

Swiss721BT-Bold.woff

Swiss721BT-Bold.woff

390 ms

Swiss721BT-Regular.woff

Swiss721BT-Regular.woff

392 ms

mi-icons.woff

mi-icons.woff

392 ms

mi-brand-logo-icons.woff

mi-brand-logo-icons.woff

393 ms

bundle.js

bundle.js

483 ms

bundle.js

bundle.js

482 ms

Accessibility Review

renaissancenashville.com accessibility score

64

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

button, link, and menuitem elements do not have accessible names.

High

ARIA IDs are not unique

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

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

High

Image elements do not have [alt] attributes

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

renaissancenashville.com 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

renaissancenashville.com SEO score

74

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

renaissancenashville.com

Open Graph data is detected on the main page of Renaissance Nashville. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: