Tools & Wizards About Us
prs.com screenshot

Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

prs.com

Page Load Speed

600 ms in total

First Response

38 ms

Resources Loaded

411 ms

Page Rendered

151 ms

prs.com screenshot

About Website

Visit prs.com now to see the best up-to-date Prs content for United States and also check out these interesting facts you probably never knew about prs.com

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

Visit prs.com

Key Findings

We analyzed Prs.com page load time and found that the first response time was 38 ms and then it took 562 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

prs.com performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

4/100

10%

LCP (Largest Contentful Paint)

Value11.8 s

0/100

25%

SI (Speed Index)

Value6.4 s

41/100

10%

TBT (Total Blocking Time)

Value2,420 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value1.192

1/100

15%

TTI (Time to Interactive)

Value11.4 s

19/100

10%

Network Requests Diagram

prs.com

38 ms

www.classicalarchives.com

79 ms

ca.css

95 ms

page-home.css

43 ms

ga.js

9 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Prs.com, 95% (57 requests) were made to Classicalarchives.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (168 ms) relates to the external source Classicalarchives.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 644.1 kB (52%)

Content Size

1.2 MB

After Optimization

603.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Prs.com main page is 1.2 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. 50% of websites need less resources to load. Javascripts take 583.7 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 96.2 kB

  • Original 129.8 kB
  • After minification 111.6 kB
  • After compression 33.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. This page needs HTML code to be minified as it can gain 18.2 kB, which is 14% 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 96.2 kB or 74% of the original size.

Image Optimization

-1%

Potential reduce by 3.3 kB

  • Original 385.4 kB
  • After minification 382.1 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. Prs images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 421.4 kB

  • Original 583.7 kB
  • After minification 568.5 kB
  • After compression 162.3 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 421.4 kB or 72% of the original size.

CSS Optimization

-83%

Potential reduce by 123.3 kB

  • Original 148.9 kB
  • After minification 147.4 kB
  • After compression 25.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. Prs.com needs all CSS files to be minified and compressed as it can save up to 123.3 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (21%)

Requests Now

58

After Optimization

46

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

prs.com

prs.com

38 ms

www.classicalarchives.com

www.classicalarchives.com

79 ms

ca.css

ca.css

95 ms

page-home.css

page-home.css

43 ms

ga.js

ga.js

9 ms

ca.js

ca.js

168 ms

page-home.js

page-home.js

11 ms

carousel-min.js

carousel-min.js

13 ms

collection_engine.js

collection_engine.js

44 ms

nv_sprite.png

nv_sprite.png

56 ms

__utm.gif

__utm.gif

29 ms

b_scroll.png

b_scroll.png

13 ms

bg_header.jpg

bg_header.jpg

14 ms

a_logo.gif

a_logo.gif

18 ms

Forum.png

Forum.png

12 ms

20th_anniversary_at_1x-17y.png

20th_anniversary_at_1x-17y.png

14 ms

b_search.gif

b_search.gif

15 ms

bg_sec_nav.gif

bg_sec_nav.gif

15 ms

b_view-cart.png

b_view-cart.png

16 ms

testimonials_link.jpg

testimonials_link.jpg

17 ms

b_black-arrow.gif

b_black-arrow.gif

17 ms

stage_play.jpg

stage_play.jpg

18 ms

stage_download.jpg

stage_download.jpg

20 ms

stage_midi.jpg

stage_midi.jpg

20 ms

stage_home.jpg

stage_home.jpg

19 ms

app_announce_home.png

app_announce_home.png

34 ms

bg_stage-content.gif

bg_stage-content.gif

19 ms

3149020222522_100.jpg

3149020222522_100.jpg

31 ms

b_play.gif

b_play.gif

30 ms

b_buy_mp3_album.gif

b_buy_mp3_album.gif

44 ms

4571353265027_100.jpg

4571353265027_100.jpg

31 ms

028947960126_100.jpg

028947960126_100.jpg

30 ms

827949055768_100.jpg

827949055768_100.jpg

31 ms

3760127222620_100.jpg

3760127222620_100.jpg

33 ms

5060189560523_100.jpg

5060189560523_100.jpg

31 ms

827949057861_100.jpg

827949057861_100.jpg

32 ms

028947960119_100.jpg

028947960119_100.jpg

35 ms

4260036254112_100.jpg

4260036254112_100.jpg

33 ms

3760127223023_100.jpg

3760127223023_100.jpg

32 ms

4040741013798_100.jpg

4040741013798_100.jpg

33 ms

634065037086_100.jpg

634065037086_100.jpg

32 ms

5902547012407_100.jpg

5902547012407_100.jpg

32 ms

4260036255485_100.jpg

4260036255485_100.jpg

33 ms

3760195733929_100.jpg

3760195733929_100.jpg

34 ms

4010072773906_100.jpg

4010072773906_100.jpg

34 ms

core.json

core.json

39 ms

collection_engine.html

collection_engine.html

30 ms

nav-data.json

nav-data.json

41 ms

4260052385340_100.jpg

4260052385340_100.jpg

29 ms

747313900480_100.jpg

747313900480_100.jpg

27 ms

028948121748_100.jpg

028948121748_100.jpg

28 ms

4035719009095_100.jpg

4035719009095_100.jpg

27 ms

bigpicturescience-banner-938x80.png

bigpicturescience-banner-938x80.png

27 ms

ico_unicorn.gif

ico_unicorn.gif

26 ms

bg_footer.gif

bg_footer.gif

27 ms

navbar_send_gift_cta.png

navbar_send_gift_cta.png

26 ms

mnav_arrow.gif

mnav_arrow.gif

25 ms

master_header_bkd.png

master_header_bkd.png

19 ms

nv_row.gif

nv_row.gif

20 ms

nv_sprite.png

nv_sprite.png

20 ms

Accessibility Review

prs.com accessibility score

65

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-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

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

High

[aria-*] attributes do not have valid values

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

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

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

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prs.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 Prs.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

prs.com

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