Tools & Wizards About Us
nashvillephilharmonic.org screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 99

    Accessibility

    Visual factors better than
    that of 96% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

nashvillephilharmonic.org

Nashville Philharmonic

Page Load Speed

888 ms in total

First Response

152 ms

Resources Loaded

600 ms

Page Rendered

136 ms

nashvillephilharmonic.org screenshot

About Website

Visit nashvillephilharmonic.org now to see the best up-to-date Nashville Philharmonic content and also check out these interesting facts you probably never knew about nashvillephilharmonic.org

Visit nashvillephilharmonic.org

Key Findings

We analyzed Nashvillephilharmonic.org page load time and found that the first response time was 152 ms and then it took 736 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

nashvillephilharmonic.org performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value18.5 s

0/100

25%

SI (Speed Index)

Value9.5 s

12/100

10%

TBT (Total Blocking Time)

Value10,550 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value27.0 s

0/100

10%

Network Requests Diagram

www.nashvillephilharmonic.org

152 ms

gXLMTmO23H9giua6qOF6igTok_sAQI2nfaAYV5ut2kSfe0SIfFHN4UJLFRbh52jhWDjX5AJhwRjkZRSXFR88FhIXwAbtFcJhFy7TMkG0jAFu-WsoShFGZAsude80ZkoRdhXCHKoyjamTiY8Djhy8ZYmC-Ao1Oco8if37OcBDOcu8OfG0jhBk-A4ziPuc-Asqde9lSYGXSKoDSWmyScmDSeBRZPoRdhXCHKoDSWmyScmDSeBRZWFR-emqiAUTdcS0jhNlOeBRiA8XpWFR-emqiAUTdcS0jhNlOeBRiA8XpWFR-emqiAUTdcS0dcmXOeBDOcu8OeFySc8Kda9lZc8qZeU8OWgEFYJ0SaBujW48Sagyjh90jhNlOeUzjhBC-eNDifU0jWFGic8Cdem3-e8C-eBkdAN0-Aw0da41OYFUiABkZWF3jAF8ShFGZAsude80ZkoRdhXCiaiaOcBRiA8XpWFR-emqiAUTdcS0jhNlOYiaikoyjamTiY8Djhy8ZYmC-Ao1Oco8ifUaiaS0jWw0dA9CiaiaOcFySc8Kda9lZc8qZeU8OWgEFYJ0SaBujW48Sagyjh90jhNlOYiaiko0jWFGic8Cdem3-e8C-eBkdAN0-Aw0da41OYiaikoDSWmyScmDSeBRZWFR-emqiAUTdcS0jhNlJ6iXScB0ShBXJ6UXScB0ShBXOWs8pYb7f6KNkMJbMg6IJMJ7f6KxkMJbMg6BJMJ7f6RgkMJbMg6YJMJ7f6KrkMJbMg65JMJ7f6RMkMJbMg6VJMJ7f6RfkMJbMg6sJMJ7f6RYkMJbMs6IJMJ7f6ROkMJbMs6YJMJ7f6RJkMJbMs65JMJ7f6RwkMJbMs6sJMHbMSD_rHje.js

56 ms

legacy.js

41 ms

modern.js

51 ms

extract-css-runtime-1bb8ec0c8c7e3ea40efb-min.en-US.js

46 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Nashvillephilharmonic.org, 31% (11 requests) were made to Assets.squarespace.com and 31% (11 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (196 ms) relates to the external source Images.squarespace-cdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 45.3 kB (3%)

Content Size

1.6 MB

After Optimization

1.5 MB

  • Images
  • JavaScript
  • CSS

In fact, the total size of Nashvillephilharmonic.org main page is 1.6 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. 40% of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-0%

Potential reduce by -8 B

  • Original 0 B

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 web page is already compressed.

Image Optimization

-13%

Potential reduce by 36.4 kB

  • Original 271.4 kB
  • After minification 235.0 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, Nashville Philharmonic needs image optimization as it can save up to 36.4 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 5.7 kB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 1.3 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

-12%

Potential reduce by 3.2 kB

  • Original 26.2 kB
  • After minification 26.2 kB
  • After compression 22.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. Nashvillephilharmonic.org needs all CSS files to be minified and compressed as it can save up to 3.2 kB or 12% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (48%)

Requests Now

23

After Optimization

12

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.nashvillephilharmonic.org

www.nashvillephilharmonic.org

152 ms

gXLMTmO23H9giua6qOF6igTok_sAQI2nfaAYV5ut2kSfe0SIfFHN4UJLFRbh52jhWDjX5AJhwRjkZRSXFR88FhIXwAbtFcJhFy7TMkG0jAFu-WsoShFGZAsude80ZkoRdhXCHKoyjamTiY8Djhy8ZYmC-Ao1Oco8if37OcBDOcu8OfG0jhBk-A4ziPuc-Asqde9lSYGXSKoDSWmyScmDSeBRZPoRdhXCHKoDSWmyScmDSeBRZWFR-emqiAUTdcS0jhNlOeBRiA8XpWFR-emqiAUTdcS0jhNlOeBRiA8XpWFR-emqiAUTdcS0dcmXOeBDOcu8OeFySc8Kda9lZc8qZeU8OWgEFYJ0SaBujW48Sagyjh90jhNlOeUzjhBC-eNDifU0jWFGic8Cdem3-e8C-eBkdAN0-Aw0da41OYFUiABkZWF3jAF8ShFGZAsude80ZkoRdhXCiaiaOcBRiA8XpWFR-emqiAUTdcS0jhNlOYiaikoyjamTiY8Djhy8ZYmC-Ao1Oco8ifUaiaS0jWw0dA9CiaiaOcFySc8Kda9lZc8qZeU8OWgEFYJ0SaBujW48Sagyjh90jhNlOYiaiko0jWFGic8Cdem3-e8C-eBkdAN0-Aw0da41OYiaikoDSWmyScmDSeBRZWFR-emqiAUTdcS0jhNlJ6iXScB0ShBXJ6UXScB0ShBXOWs8pYb7f6KNkMJbMg6IJMJ7f6KxkMJbMg6BJMJ7f6RgkMJbMg6YJMJ7f6KrkMJbMg65JMJ7f6RMkMJbMg6VJMJ7f6RfkMJbMg6sJMJ7f6RYkMJbMs6IJMJ7f6ROkMJbMs6YJMJ7f6RJkMJbMs65JMJ7f6RwkMJbMs6sJMHbMSD_rHje.js

gXLMTmO23H9giua6qOF6igTok_sAQI2nfaAYV5ut2kSfe0SIfFHN4UJLFRbh52jhWDjX5AJhwRjkZRSXFR88FhIXwAbtFcJhFy7TMkG0jAFu-WsoShFGZAsude80ZkoRdhXCHKoyjamTiY8Djhy8ZYmC-Ao1Oco8if37OcBDOcu8OfG0jhBk-A4ziPuc-Asqde9lSYGXSKoDSWmyScmDSeBRZPoRdhXCHKoDSWmyScmDSeBRZWFR-emqiAUTdcS0jhNlOeBRiA8XpWFR-emqiAUTdcS0jhNlOeBRiA8XpWFR-emqiAUTdcS0dcmXOeBDOcu8OeFySc8Kda9lZc8qZeU8OWgEFYJ0SaBujW48Sagyjh90jhNlOeUzjhBC-eNDifU0jWFGic8Cdem3-e8C-eBkdAN0-Aw0da41OYFUiABkZWF3jAF8ShFGZAsude80ZkoRdhXCiaiaOcBRiA8XpWFR-emqiAUTdcS0jhNlOYiaikoyjamTiY8Djhy8ZYmC-Ao1Oco8ifUaiaS0jWw0dA9CiaiaOcFySc8Kda9lZc8qZeU8OWgEFYJ0SaBujW48Sagyjh90jhNlOYiaiko0jWFGic8Cdem3-e8C-eBkdAN0-Aw0da41OYiaikoDSWmyScmDSeBRZWFR-emqiAUTdcS0jhNlJ6iXScB0ShBXJ6UXScB0ShBXOWs8pYb7f6KNkMJbMg6IJMJ7f6KxkMJbMg6BJMJ7f6RgkMJbMg6YJMJ7f6KrkMJbMg65JMJ7f6RMkMJbMg6VJMJ7f6RfkMJbMg6sJMJ7f6RYkMJbMs6IJMJ7f6ROkMJbMs6YJMJ7f6RJkMJbMs65JMJ7f6RwkMJbMs6sJMHbMSD_rHje.js

56 ms

legacy.js

legacy.js

41 ms

modern.js

modern.js

51 ms

extract-css-runtime-1bb8ec0c8c7e3ea40efb-min.en-US.js

extract-css-runtime-1bb8ec0c8c7e3ea40efb-min.en-US.js

46 ms

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

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

148 ms

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

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

48 ms

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

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

147 ms

common-vendors-a21ade7c6b6ba367b345-min.en-US.js

common-vendors-a21ade7c6b6ba367b345-min.en-US.js

151 ms

common-0d056c345ecf62d9430e-min.en-US.js

common-0d056c345ecf62d9430e-min.en-US.js

153 ms

commerce-fe6f60fc3243752ab1e8-min.en-US.js

commerce-fe6f60fc3243752ab1e8-min.en-US.js

153 ms

commerce-fb908395734262466dc9-min.en-US.css

commerce-fb908395734262466dc9-min.en-US.css

66 ms

performance-74d24f5c2adcf3b8ee8a-min.en-US.js

performance-74d24f5c2adcf3b8ee8a-min.en-US.js

153 ms

site.css

site.css

64 ms

static.css

static.css

59 ms

site-bundle.11fff701a22dbd232e9127391845b3e2.js

site-bundle.11fff701a22dbd232e9127391845b3e2.js

138 ms

short-text-only-maroon.png

short-text-only-maroon.png

196 ms

230507_SERIES+4_ST+GEORGE+DRESS+REHEARSAL.00_11_32_05.Still007.jpg

230507_SERIES+4_ST+GEORGE+DRESS+REHEARSAL.00_11_32_05.Still007.jpg

160 ms

Vaughn-Richardson-06-24-02.jpg

Vaughn-Richardson-06-24-02.jpg

160 ms

banner1.jpg

banner1.jpg

162 ms

Asset+2.png

Asset+2.png

161 ms

full-logo-full-color.png

full-logo-full-color.png

162 ms

CFMT_logo%C2%AE-e1495431176578.jpg

CFMT_logo%C2%AE-e1495431176578.jpg

176 ms

tac.png

tac.png

177 ms

ClarinetWide0.3-Bold.woff2

ClarinetWide0.3-Bold.woff2

18 ms

ClarinetWide0.3-Regular.woff2

ClarinetWide0.3-Regular.woff2

3 ms

d

d

39 ms

d

d

22 ms

d

d

40 ms

d

d

59 ms

d

d

42 ms

d

d

39 ms

d

d

58 ms

d

d

40 ms

d

d

40 ms

d

d

40 ms

Accessibility Review

nashvillephilharmonic.org accessibility score

99

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

Best Practices

nashvillephilharmonic.org 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

nashvillephilharmonic.org SEO score

84

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

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nashvillephilharmonic.org can be misinterpreted by Google and other search engines. Our service has detected that English 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 Nashvillephilharmonic.org 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

nashvillephilharmonic.org

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