Tools & Wizards About Us
nashvilletheplace.com screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 0

    Best Practices

  • 84

    SEO

    Google-friendlier than
    52% of websites

nashvilletheplace.com

Home Page - The Place at Fifth + Broadway

Page Load Speed

3.5 sec in total

First Response

32 ms

Resources Loaded

2.1 sec

Page Rendered

1.3 sec

nashvilletheplace.com screenshot

About Website

Click here to check amazing Nashvillethe Place content. Otherwise, check out these important facts you probably never knew about nashvilletheplace.com

Visit nashvilletheplace.com

Key Findings

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

Performance Metrics

nashvilletheplace.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value10.7 s

0/100

25%

SI (Speed Index)

Value8.4 s

18/100

10%

TBT (Total Blocking Time)

Value3,780 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.078

94/100

15%

TTI (Time to Interactive)

Value16.8 s

5/100

10%

Network Requests Diagram

nashvilletheplace.com

32 ms

www.livetheplacenashville.com

919 ms

fonts.css

158 ms

757ae.css

68 ms

a5ff7.css

134 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Nashvilletheplace.com, 45% (17 requests) were made to Livetheplacenashville.com and 11% (4 requests) were made to My.hy.ly. The less responsive or slowest element that took the longest time to load (919 ms) relates to the external source Livetheplacenashville.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 137.4 kB (7%)

Content Size

1.9 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nashvilletheplace.com main page is 1.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. 65% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 70.7 kB

  • Original 88.0 kB
  • After minification 81.4 kB
  • After compression 17.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 70.7 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 1.3 MB
  • After minification 1.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. Nashvillethe Place images are well optimized though.

JavaScript Optimization

-16%

Potential reduce by 65.8 kB

  • Original 423.9 kB
  • After minification 423.9 kB
  • After compression 358.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 65.8 kB or 16% of the original size.

CSS Optimization

-2%

Potential reduce by 812 B

  • Original 49.7 kB
  • After minification 49.7 kB
  • After compression 48.9 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. Nashvilletheplace.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 22 (61%)

Requests Now

36

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nashvilletheplace.com

nashvilletheplace.com

32 ms

www.livetheplacenashville.com

www.livetheplacenashville.com

919 ms

fonts.css

fonts.css

158 ms

757ae.css

757ae.css

68 ms

a5ff7.css

a5ff7.css

134 ms

b0c3f.css

b0c3f.css

306 ms

6656f.js

6656f.js

361 ms

data-layer-event-trigger.js

data-layer-event-trigger.js

33 ms

528df.js

528df.js

317 ms

dni.js

dni.js

43 ms

782b7.js

782b7.js

196 ms

osano.js

osano.js

498 ms

1.js

1.js

884 ms

28f5b.js

28f5b.js

213 ms

gtm.js

gtm.js

61 ms

js

js

44 ms

analytics.js

analytics.js

108 ms

destination

destination

93 ms

event-manager.js

event-manager.js

33 ms

attribution-manager.js

attribution-manager.js

89 ms

fbevents.js

fbevents.js

99 ms

collect

collect

47 ms

collect

collect

59 ms

app.js

app.js

111 ms

pause-icon.svg

pause-icon.svg

102 ms

play-icon.svg

play-icon.svg

102 ms

gold-bg.png

gold-bg.png

329 ms

447201107-the_place_horizontal_white.png

447201107-the_place_horizontal_white.png

197 ms

ThePlace_Amenities_CommunalBalcony_ZackBenson_12.7.jpg

ThePlace_Amenities_CommunalBalcony_ZackBenson_12.7.jpg

429 ms

ThePlace_Int_Feature_Model2_LivingRoom2_Nov22-1.jpg

ThePlace_Int_Feature_Model2_LivingRoom2_Nov22-1.jpg

251 ms

ThePlace_Amenities_PoolDeck_ZackBenson_12.7.22.jpg

ThePlace_Amenities_PoolDeck_ZackBenson_12.7.22.jpg

250 ms

left-arrow-white.png

left-arrow-white.png

67 ms

ThePlace_Amenities_WorkHub_ZackBenson_12.7.22.jpg

ThePlace_Amenities_WorkHub_ZackBenson_12.7.22.jpg

450 ms

underscore-min.js

underscore-min.js

33 ms

api.js

api.js

47 ms

jquery.min.js

jquery.min.js

32 ms

recaptcha__en.js

recaptcha__en.js

98 ms

ping

ping

83 ms

Accessibility Review

nashvilletheplace.com accessibility score

89

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.

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

SEO Factors

nashvilletheplace.com SEO score

84

Search Engine Optimization Advices

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 Nashvilletheplace.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 Nashvilletheplace.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

nashvilletheplace.com

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