Tools & Wizards About Us
classicalarchives.com screenshot

Report Summary

  • 7

    Performance

    Renders faster than
    22% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

classicalarchives.com

Classical Archives

Page Load Speed

717 ms in total

First Response

7 ms

Resources Loaded

620 ms

Page Rendered

90 ms

classicalarchives.com screenshot

About Website

Welcome to classicalarchives.com homepage info - get ready to check Classical Archives best content for United States right away, or after learning these important things about classicalarchives.com

The world's best curated classical music site on the web. Over a million of classical music files. Most composers and their music are represented. Biographies, reviews, playlists and store.

Visit classicalarchives.com

Key Findings

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

classicalarchives.com performance score

7

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value11.2 s

0/100

25%

SI (Speed Index)

Value8.5 s

17/100

10%

TBT (Total Blocking Time)

Value1,490 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value1.601

0/100

15%

TTI (Time to Interactive)

Value15.5 s

7/100

10%

Network Requests Diagram

classicalarchives.com

7 ms

18 ms

gtm.js

110 ms

bootstrap.min.css

56 ms

dataTables.bootstrap4.min.css

71 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 44% of them (28 requests) were addressed to the original Classicalarchives.com, 47% (30 requests) were made to Cdn.jsdelivr.net and 5% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (453 ms) relates to the external source Cdn.jsdelivr.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 347.8 kB (42%)

Content Size

822.3 kB

After Optimization

474.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Classicalarchives.com main page is 822.3 kB. 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 433.0 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 32.7 kB

  • Original 38.9 kB
  • After minification 27.1 kB
  • After compression 6.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. This page needs HTML code to be minified as it can gain 11.8 kB, which is 30% 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 32.7 kB or 84% of the original size.

Image Optimization

-11%

Potential reduce by 48.7 kB

  • Original 433.0 kB
  • After minification 384.4 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, Classical Archives needs image optimization as it can save up to 48.7 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-84%

Potential reduce by 263.3 kB

  • Original 314.7 kB
  • After minification 306.9 kB
  • After compression 51.4 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 263.3 kB or 84% of the original size.

CSS Optimization

-9%

Potential reduce by 3.2 kB

  • Original 35.7 kB
  • After minification 35.7 kB
  • After compression 32.6 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. Classicalarchives.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 39 (74%)

Requests Now

53

After Optimization

14

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

classicalarchives.com

classicalarchives.com

7 ms

18 ms

gtm.js

gtm.js

110 ms

bootstrap.min.css

bootstrap.min.css

56 ms

dataTables.bootstrap4.min.css

dataTables.bootstrap4.min.css

71 ms

slick.min.css

slick.min.css

73 ms

slick-theme.min.css

slick-theme.min.css

96 ms

css2

css2

73 ms

css2

css2

108 ms

font-awesome.min.css

font-awesome.min.css

99 ms

css2

css2

161 ms

jquery-ui.min.css

jquery-ui.min.css

347 ms

video-js.min.css

video-js.min.css

95 ms

animate.min.css

animate.min.css

88 ms

calibri.css

calibri.css

40 ms

mnmain.css

mnmain.css

72 ms

jquery.min.js

jquery.min.js

96 ms

popper.min.js

popper.min.js

100 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

105 ms

jquery.dataTables.min.js

jquery.dataTables.min.js

105 ms

jquery-ui.min.js

jquery-ui.min.js

146 ms

jquery.ui.touch-punch.min.js

jquery.ui.touch-punch.min.js

104 ms

jquery.ui.sortable-animation.min.js

jquery.ui.sortable-animation.min.js

147 ms

dataTables.bootstrap4.min.js

dataTables.bootstrap4.min.js

148 ms

sweetalert2.all.min.js

sweetalert2.all.min.js

148 ms

angular.min.js

angular.min.js

150 ms

angular-filter.min.js

angular-filter.min.js

149 ms

angular-animate.min.js

angular-animate.min.js

442 ms

angular-touch.min.js

angular-touch.min.js

149 ms

angular-ui.min.js

angular-ui.min.js

64 ms

angular-sanitize.min.js

angular-sanitize.min.js

150 ms

ui-bootstrap-tpls-3.0.7.min.js

ui-bootstrap-tpls-3.0.7.min.js

151 ms

angular-route.min.js

angular-route.min.js

148 ms

sortable.min.js

sortable.min.js

439 ms

slick.min.js

slick.min.js

151 ms

angular-slick.min.js

angular-slick.min.js

453 ms

video.min.js

video.min.js

153 ms

jquery.marquee.min.js

jquery.marquee.min.js

151 ms

common.js

common.js

35 ms

module.js

module.js

40 ms

services.js

services.js

40 ms

controller.js

controller.js

54 ms

js

js

45 ms

logo-unicorn.png

logo-unicorn.png

52 ms

logo-white.svg

logo-white.svg

49 ms

usericon.png

usericon.png

49 ms

info.png

info.png

63 ms

footer-banner-desktop.png

footer-banner-desktop.png

65 ms

footer-banner-mobile.png

footer-banner-mobile.png

69 ms

app-apple.png

app-apple.png

63 ms

app-google.png

app-google.png

66 ms

app-sonos.png

app-sonos.png

66 ms

app-amazon.png

app-amazon.png

67 ms

app-alexa.png

app-alexa.png

66 ms

help-player.png

help-player.png

69 ms

calibri.latin-ext.woff

calibri.latin-ext.woff

4 ms

calibri.latin.woff

calibri.latin.woff

4 ms

calibrib.latin-ext.woff

calibrib.latin-ext.woff

5 ms

calibrib.latin.woff

calibrib.latin.woff

4 ms

calibriz.latin-ext.woff

calibriz.latin-ext.woff

22 ms

calibriz.latin.woff

calibriz.latin.woff

7 ms

calibrii.latin-ext.woff

calibrii.latin-ext.woff

21 ms

calibrii.latin.woff

calibrii.latin.woff

4 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

22 ms

Accessibility Review

classicalarchives.com accessibility score

83

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

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

High

Links do not have a discernible name

Best Practices

classicalarchives.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

Page has valid source maps

SEO Factors

classicalarchives.com SEO score

81

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

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

classicalarchives.com

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