Tools & Wizards About Us
stlsymphony.org screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    47% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 81

    SEO

    Google-friendlier than
    42% of websites

stlsymphony.org

SLSO

Page Load Speed

2.1 sec in total

First Response

98 ms

Resources Loaded

1.9 sec

Page Rendered

164 ms

stlsymphony.org screenshot

About Website

Click here to check amazing Stlsymphony content for United States. Otherwise, check out these important facts you probably never knew about stlsymphony.org

Founded in 1880, the St. Louis Symphony Orchestra is recognized internationally as an ensemble of the highest caliber, performing a broad musical repertoire with skill and spirit. The St. Louis Sympho...

Visit stlsymphony.org

Key Findings

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

Performance Metrics

stlsymphony.org performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

22/100

10%

LCP (Largest Contentful Paint)

Value26.0 s

0/100

25%

SI (Speed Index)

Value7.9 s

23/100

10%

TBT (Total Blocking Time)

Value950 ms

29/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value25.6 s

0/100

10%

Network Requests Diagram

stlsymphony.org

98 ms

www.stlsymphony.org

547 ms

tBf9shg_EeSVQiIACtqXBA.js

22 ms

Bootstrap.js

33 ms

trafficControl.js

41 ms

Our browser made a total of 158 requests to load all elements on the main page. We found that 53% of them (84 requests) were addressed to the original Stlsymphony.org, 4% (7 requests) were made to Match.adsrvr.org and 3% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (547 ms) belongs to the original domain Stlsymphony.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (66%)

Content Size

1.7 MB

After Optimization

581.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Stlsymphony.org main page is 1.7 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. 60% of websites need less resources to load. CSS take 811.8 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 33.8 kB

  • Original 40.8 kB
  • After minification 34.1 kB
  • After compression 7.0 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 6.7 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 33.8 kB or 83% of the original size.

Image Optimization

-5%

Potential reduce by 14.0 kB

  • Original 301.8 kB
  • After minification 287.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. Stlsymphony images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 379.8 kB

  • Original 567.8 kB
  • After minification 509.6 kB
  • After compression 188.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 379.8 kB or 67% of the original size.

CSS Optimization

-88%

Potential reduce by 713.4 kB

  • Original 811.8 kB
  • After minification 615.3 kB
  • After compression 98.4 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. Stlsymphony.org needs all CSS files to be minified and compressed as it can save up to 713.4 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 85 (83%)

Requests Now

103

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

stlsymphony.org

stlsymphony.org

98 ms

www.stlsymphony.org

www.stlsymphony.org

547 ms

tBf9shg_EeSVQiIACtqXBA.js

tBf9shg_EeSVQiIACtqXBA.js

22 ms

Bootstrap.js

Bootstrap.js

33 ms

trafficControl.js

trafficControl.js

41 ms

app.css

app.css

154 ms

require.js

require.js

42 ms

serverComponent.php

serverComponent.php

54 ms

db79431f8268c9fdc47cc0e696c64d69.js

db79431f8268c9fdc47cc0e696c64d69.js

7 ms

fbds.js

fbds.js

5 ms

25 ms

font-awesome.min.css

font-awesome.min.css

27 ms

css

css

28 ms

owl.carousel.css

owl.carousel.css

27 ms

gtm.js

gtm.js

64 ms

sdk.js

sdk.js

40 ms

woo.js

woo.js

39 ms

logo.svg

logo.svg

53 ms

action2.js

action2.js

42 ms

1617subscriptiononsale_1300.jpg

1617subscriptiononsale_1300.jpg

106 ms

1516_prokofievromeojuliet_1300x350.jpg

1516_prokofievromeojuliet_1300x350.jpg

151 ms

1516_shakespearefestival_425x100.jpg

1516_shakespearefestival_425x100.jpg

104 ms

phil_home216_425x100.jpg

phil_home216_425x100.jpg

147 ms

1516_cali_tour_roger_kaza_425.jpg

1516_cali_tour_roger_kaza_425.jpg

174 ms

wells_fargo_advisors.jpg

wells_fargo_advisors.jpg

126 ms

K6ngFdK5haaaRGBV8waDwA.ttf

K6ngFdK5haaaRGBV8waDwA.ttf

104 ms

187TYb8ysVvxar86IcDsZ_esZW2xOQ-xsNqO47m55DA.ttf

187TYb8ysVvxar86IcDsZ_esZW2xOQ-xsNqO47m55DA.ttf

147 ms

nHiQo1BypvYzt95zlPq1TvesZW2xOQ-xsNqO47m55DA.ttf

nHiQo1BypvYzt95zlPq1TvesZW2xOQ-xsNqO47m55DA.ttf

196 ms

main.js

main.js

144 ms

activityi;src=4566215;type=count0;cat=sitev0;num=147667711135;ord=1

activityi;src=4566215;type=count0;cat=sitev0;num=147667711135;ord=1

115 ms

activityi;src=4566215;type=count0;cat=pagev0;ord=3892816067673.266

activityi;src=4566215;type=count0;cat=pagev0;ord=3892816067673.266

139 ms

190 ms

analytics.js

analytics.js

83 ms

conversion_async.js

conversion_async.js

58 ms

fbevents.js

fbevents.js

33 ms

oct.js

oct.js

103 ms

xd_arbiter.php

xd_arbiter.php

146 ms

xd_arbiter.php

xd_arbiter.php

275 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

28 ms

cse

cse

176 ms

186 ms

62 ms

62 ms

73 ms

require.config.js

require.config.js

50 ms

collect

collect

27 ms

collect

collect

89 ms

collect

collect

33 ms

collect

collect

32 ms

collect

collect

124 ms

collect

collect

148 ms

adsct

adsct

147 ms

adsct

adsct

73 ms

require.config.js

require.config.js

22 ms

100 ms

jquery-1.11.0.min.js

jquery-1.11.0.min.js

40 ms

moment.js

moment.js

65 ms

handlebars.runtime.js

handlebars.runtime.js

62 ms

underscore-min.js

underscore-min.js

80 ms

cse

cse

84 ms

cse

cse

171 ms

generic

generic

96 ms

www-embed-player-vflZsBgOl.css

www-embed-player-vflZsBgOl.css

132 ms

www-embed-player.js

www-embed-player.js

173 ms

generic

generic

88 ms

owl.carousel.min.js

owl.carousel.min.js

36 ms

moment.js

moment.js

29 ms

handlebarsHelpers.js

handlebarsHelpers.js

44 ms

backbone-min.js

backbone-min.js

30 ms

owl.carousel.min.js

owl.carousel.min.js

31 ms

pixel

pixel

35 ms

rum

rum

78 ms

rtset

rtset

47 ms

Pug

Pug

56 ms

pixel

pixel

123 ms

handlebarsHelpers.js

handlebarsHelpers.js

31 ms

pixel

pixel

80 ms

cse

cse

175 ms

sd

sd

17 ms

cse

cse

161 ms

tap.php

tap.php

100 ms

main_global.js

main_global.js

45 ms

rum

rum

37 ms

59 ms

google

google

48 ms

main_global.js

main_global.js

54 ms

6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js

6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js

23 ms

ad_status.js

ad_status.js

78 ms

google

google

26 ms

blank.gif

blank.gif

18 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

93 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

99 ms

cse

cse

302 ms

utilities.js

utilities.js

30 ms

epiPageTypes.js

epiPageTypes.js

30 ms

search.js

search.js

50 ms

cse

cse

73 ms

utilities.js

utilities.js

26 ms

epiPageTypes.js

epiPageTypes.js

26 ms

generic

generic

8 ms

generic

generic

13 ms

search.js

search.js

25 ms

match

match

7 ms

generic

generic

4 ms

global.js

global.js

23 ms

HomePageData.js

HomePageData.js

24 ms

global.js

global.js

21 ms

HomePageData.js

HomePageData.js

23 ms

menuView.js

menuView.js

22 ms

calendarFlyOut.js

calendarFlyOut.js

23 ms

calendarEventCollection.js

calendarEventCollection.js

23 ms

calendar.js

calendar.js

40 ms

eventListView.js

eventListView.js

40 ms

view.js

view.js

40 ms

menuView.js

menuView.js

31 ms

calendarFlyOut.js

calendarFlyOut.js

34 ms

calendarEventCollection.js

calendarEventCollection.js

23 ms

calendar.js

calendar.js

47 ms

eventListView.js

eventListView.js

35 ms

view.js

view.js

45 ms

calendarEvent.js

calendarEvent.js

21 ms

templates.js

templates.js

22 ms

mainMenuData.js

mainMenuData.js

23 ms

templates.js

templates.js

26 ms

calendarEvent.js

calendarEvent.js

24 ms

templates.js

templates.js

35 ms

mainMenuData.js

mainMenuData.js

25 ms

templates.js

templates.js

47 ms

eventCollection.js

eventCollection.js

23 ms

templates.js

templates.js

28 ms

subviewCollection.js

subviewCollection.js

26 ms

calendarMonth.js

calendarMonth.js

27 ms

calendar.js

calendar.js

28 ms

eventCollection.js

eventCollection.js

42 ms

templates.js

templates.js

29 ms

subviewCollection.js

subviewCollection.js

27 ms

calendarMonth.js

calendarMonth.js

34 ms

calendar.js

calendar.js

60 ms

collection.js

collection.js

22 ms

subview.js

subview.js

21 ms

eventItem.js

eventItem.js

22 ms

subview.js

subview.js

22 ms

collection.js

collection.js

23 ms

eventItem.js

eventItem.js

22 ms

calendarDay.js

calendarDay.js

22 ms

calendarWeek.js

calendarWeek.js

23 ms

calendarMonth.js

calendarMonth.js

26 ms

calendarMonthCollection.js

calendarMonthCollection.js

26 ms

model.js

model.js

24 ms

calendarDay.js

calendarDay.js

22 ms

calendarWeek.js

calendarWeek.js

23 ms

calendarMonth.js

calendarMonth.js

23 ms

calendarMonthCollection.js

calendarMonthCollection.js

34 ms

model.js

model.js

31 ms

calendarDayCollection.js

calendarDayCollection.js

44 ms

calendarWeekCollection.js

calendarWeekCollection.js

42 ms

calendarWeekCollection.js

calendarWeekCollection.js

23 ms

calendarDayCollection.js

calendarDayCollection.js

23 ms

Accessibility Review

stlsymphony.org accessibility score

74

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-hidden="true"] elements contain focusable descendents

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

Image elements do not have [alt] attributes

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

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

Page has valid source maps

SEO Factors

stlsymphony.org SEO score

81

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

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

stlsymphony.org

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