Tools & Wizards About Us
choraline.com screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

choraline.com

Choral Music Site: Choral Sheet Music, SATB Vocal Scores & Downloads : Choraline

Page Load Speed

3.5 sec in total

First Response

265 ms

Resources Loaded

3.1 sec

Page Rendered

200 ms

choraline.com screenshot

About Website

Click here to check amazing Choraline content for United Kingdom. Otherwise, check out these important facts you probably never knew about choraline.com

Over 15,000 singers every year use Choraline. We supply choral vocal scores, SATB vocal scores, voice part rehearsal cds, voice part mp3 downloads, choir folders, choral performance cds, singing sets,...

Visit choraline.com

Key Findings

We analyzed Choraline.com page load time and found that the first response time was 265 ms and then it took 3.3 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

choraline.com performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

22/100

10%

LCP (Largest Contentful Paint)

Value4.0 s

48/100

25%

SI (Speed Index)

Value8.9 s

15/100

10%

TBT (Total Blocking Time)

Value1,250 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value18.0 s

3/100

10%

Network Requests Diagram

choraline.com

265 ms

www.choraline.com

602 ms

style.css

92 ms

shadowbox.css

183 ms

jquery.ui.stars.css

259 ms

Our browser made a total of 113 requests to load all elements on the main page. We found that 72% of them (81 requests) were addressed to the original Choraline.com, 12% (13 requests) were made to Embed.tawk.to and 4% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (832 ms) belongs to the original domain Choraline.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 389.1 kB (23%)

Content Size

1.7 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Choraline.com 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. 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 804.0 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 39.6 kB

  • Original 47.2 kB
  • After minification 44.5 kB
  • After compression 7.6 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 39.6 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 804.0 kB
  • After minification 804.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. Choraline images are well optimized though.

JavaScript Optimization

-36%

Potential reduce by 218.7 kB

  • Original 608.9 kB
  • After minification 608.9 kB
  • After compression 390.2 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 218.7 kB or 36% of the original size.

CSS Optimization

-61%

Potential reduce by 130.8 kB

  • Original 215.7 kB
  • After minification 155.0 kB
  • After compression 84.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. Choraline.com needs all CSS files to be minified and compressed as it can save up to 130.8 kB or 61% of the original size.

Requests Breakdown

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

Requests Now

108

After Optimization

64

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

choraline.com

choraline.com

265 ms

www.choraline.com

www.choraline.com

602 ms

style.css

style.css

92 ms

shadowbox.css

shadowbox.css

183 ms

jquery.ui.stars.css

jquery.ui.stars.css

259 ms

modernizr.js

modernizr.js

262 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

25 ms

jquery.ui.core.min.js

jquery.ui.core.min.js

259 ms

jquery.ui.widget.min.js

jquery.ui.widget.min.js

257 ms

jquery.ui.stars.js

jquery.ui.stars.js

261 ms

jquery.easing.js

jquery.easing.js

269 ms

jquery.cycle.js

jquery.cycle.js

346 ms

hoverIntent.js

hoverIntent.js

357 ms

match-height.js

match-height.js

359 ms

bootstrap.min.js

bootstrap.min.js

356 ms

responsive.js

responsive.js

354 ms

ckeditor.js

ckeditor.js

614 ms

jquery.js

jquery.js

433 ms

shadowbox.js

shadowbox.js

538 ms

site.1.js

site.1.js

453 ms

mlt.js

mlt.js

332 ms

bootstrap.min.css

bootstrap.min.css

451 ms

layout.css

layout.css

366 ms

typography.css

typography.css

435 ms

forms.css

forms.css

460 ms

enhancements.css

enhancements.css

457 ms

mediaqueries.css

mediaqueries.css

524 ms

cms.css

cms.css

541 ms

logo.png

logo.png

94 ms

pp-acceptance-medium.png

pp-acceptance-medium.png

84 ms

O3y4s7uIKvI

O3y4s7uIKvI

185 ms

basket.png

basket.png

98 ms

search2.png

search2.png

100 ms

img1.png

img1.png

93 ms

img2.png

img2.png

206 ms

img3.png

img3.png

183 ms

img4.png

img4.png

168 ms

img5.png

img5.png

181 ms

img6.png

img6.png

206 ms

img7.png

img7.png

526 ms

img8.png

img8.png

525 ms

img9.png

img9.png

524 ms

img10.png

img10.png

526 ms

img11.png

img11.png

528 ms

img12.png

img12.png

527 ms

img13.png

img13.png

660 ms

img14.png

img14.png

661 ms

img15.png

img15.png

661 ms

img16.png

img16.png

662 ms

img17.png

img17.png

661 ms

img18.png

img18.png

662 ms

img19.png

img19.png

662 ms

img201.png

img201.png

662 ms

img21.png

img21.png

663 ms

img22.png

img22.png

664 ms

img23.png

img23.png

664 ms

img24.png

img24.png

663 ms

img25.png

img25.png

664 ms

img26.png

img26.png

683 ms

img27.png

img27.png

683 ms

img28.png

img28.png

683 ms

img29.png

img29.png

683 ms

img30.png

img30.png

683 ms

img39.png

img39.png

683 ms

img31.png

img31.png

832 ms

img32.png

img32.png

830 ms

analytics.js

analytics.js

37 ms

default

default

463 ms

cheltenham_bt-webfont.woff

cheltenham_bt-webfont.woff

758 ms

img33.png

img33.png

744 ms

img34.png

img34.png

738 ms

img35.png

img35.png

737 ms

collect

collect

13 ms

collect

collect

31 ms

js

js

106 ms

img36.png

img36.png

796 ms

www-player.css

www-player.css

8 ms

www-embed-player.js

www-embed-player.js

28 ms

base.js

base.js

161 ms

img37.png

img37.png

785 ms

img38.png

img38.png

785 ms

PaymentsBy.png

PaymentsBy.png

758 ms

Mastercard.gif

Mastercard.gif

732 ms

ad_status.js

ad_status.js

191 ms

visa_debit.gif

visa_debit.gif

441 ms

shopping.png

shopping.png

447 ms

Lloyd_Silverthorne_Choral_Singer_and_Choraline_Musical_Genius.jpg

Lloyd_Silverthorne_Choral_Singer_and_Choraline_Musical_Genius.jpg

445 ms

Martin_Muncaster.jpg

Martin_Muncaster.jpg

523 ms

join.png

join.png

446 ms

OfRUkPbLLmIJHiz0sRQ6wXEqxeMXOYMNgt9OZuziQhg.js

OfRUkPbLLmIJHiz0sRQ6wXEqxeMXOYMNgt9OZuziQhg.js

138 ms

embed.js

embed.js

50 ms

cbigdefault.png

cbigdefault.png

399 ms

ysDJ1jRAChoraLine%20Product%20Page%20Image.png

ysDJ1jRAChoraLine%20Product%20Page%20Image.png

314 ms

IJTQYlX1ChoraLine%20Product%20Page%20Image.png

IJTQYlX1ChoraLine%20Product%20Page%20Image.png

393 ms

bigdefault.png

bigdefault.png

396 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

143 ms

KFOlCnqEu92Fr1MmEU9fBBc-.woff

KFOlCnqEu92Fr1MmEU9fBBc-.woff

144 ms

id

id

21 ms

Create

Create

108 ms

GenerateIT

GenerateIT

14 ms

arrowblank.gif

arrowblank.gif

90 ms

twk-arr-find-polyfill.js

twk-arr-find-polyfill.js

164 ms

twk-object-values-polyfill.js

twk-object-values-polyfill.js

67 ms

twk-event-polyfill.js

twk-event-polyfill.js

73 ms

twk-entries-polyfill.js

twk-entries-polyfill.js

177 ms

twk-iterator-polyfill.js

twk-iterator-polyfill.js

190 ms

twk-promise-polyfill.js

twk-promise-polyfill.js

62 ms

twk-main.js

twk-main.js

152 ms

twk-vendor.js

twk-vendor.js

165 ms

twk-chunk-vendors.js

twk-chunk-vendors.js

199 ms

twk-chunk-common.js

twk-chunk-common.js

241 ms

twk-runtime.js

twk-runtime.js

171 ms

twk-app.js

twk-app.js

215 ms

Accessibility Review

choraline.com accessibility score

61

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.

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

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

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

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

choraline.com best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

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

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

choraline.com

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