Tools & Wizards About Us
pianity.com screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

pianity.com

Pianity - Stream & Collect unique Musical Experiences

Page Load Speed

1.4 sec in total

First Response

54 ms

Resources Loaded

834 ms

Page Rendered

521 ms

pianity.com screenshot

About Website

Click here to check amazing Pianity content for Peru. Otherwise, check out these important facts you probably never knew about pianity.com

The new way to experience and discover music! Own rare musical gems attached to amazing fan experiences, Support talented upcoming artists, and join exclusive and authentic communities...

Visit pianity.com

Key Findings

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

Performance Metrics

pianity.com performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

45/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

29/100

25%

SI (Speed Index)

Value6.2 s

44/100

10%

TBT (Total Blocking Time)

Value3,510 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value15.6 s

6/100

10%

Network Requests Diagram

pianity.com

54 ms

wf-default.css

135 ms

65ac447ab68743c4.css

39 ms

polyfills-c67a75d1b6f99dc8.js

34 ms

webpack-98fb9917faaf31ac.js

35 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 40% of them (19 requests) were addressed to the original Pianity.com, 54% (26 requests) were made to Assets-global.website-files.com and 2% (1 request) were made to D3e54v103j8qbb.cloudfront.net. The less responsive or slowest element that took the longest time to load (480 ms) belongs to the original domain Pianity.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 118.3 kB (21%)

Content Size

564.2 kB

After Optimization

445.9 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Pianity.com main page is 564.2 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. 40% of websites need less resources to load. Images take 385.4 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 102.3 kB

  • Original 138.5 kB
  • After minification 138.3 kB
  • After compression 36.2 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 102.3 kB or 74% of the original size.

Image Optimization

-4%

Potential reduce by 15.5 kB

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

JavaScript Optimization

-1%

Potential reduce by 453 B

  • Original 40.2 kB
  • After minification 40.2 kB
  • After compression 39.8 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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 13 (30%)

Requests Now

43

After Optimization

30

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pianity.com

pianity.com

54 ms

wf-default.css

wf-default.css

135 ms

65ac447ab68743c4.css

65ac447ab68743c4.css

39 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

34 ms

webpack-98fb9917faaf31ac.js

webpack-98fb9917faaf31ac.js

35 ms

framework-560765ab0625ba27.js

framework-560765ab0625ba27.js

30 ms

main-ea38205dce4dd0c9.js

main-ea38205dce4dd0c9.js

32 ms

_app-24a684afdb5aabf2.js

_app-24a684afdb5aabf2.js

84 ms

5935-df247dde96698e4d.js

5935-df247dde96698e4d.js

46 ms

2579-021deb94676ba4a2.js

2579-021deb94676ba4a2.js

51 ms

index-e488cd7b8225ed60.js

index-e488cd7b8225ed60.js

45 ms

_buildManifest.js

_buildManifest.js

49 ms

_ssgManifest.js

_ssgManifest.js

63 ms

jquery-3.5.1.min.dc5e7f18c8.js

jquery-3.5.1.min.dc5e7f18c8.js

17 ms

rocket-loader.min.js

rocket-loader.min.js

46 ms

j.php

j.php

65 ms

63dce8ed9f86b49012a093fc_Player%20Button-2.svg

63dce8ed9f86b49012a093fc_Player%20Button-2.svg

119 ms

select-chevron-dark.svg

select-chevron-dark.svg

21 ms

64673f120682dc8eff3204fc_avatar.webp

64673f120682dc8eff3204fc_avatar.webp

99 ms

63f4dd3530e323452b208687_button%20play.svg

63f4dd3530e323452b208687_button%20play.svg

137 ms

64bfd85b368e3149d635ff16_coin-telegraph.png

64bfd85b368e3149d635ff16_coin-telegraph.png

104 ms

64bfd85b57a4cc3165f121f4_digital-music-news.png

64bfd85b57a4cc3165f121f4_digital-music-news.png

103 ms

64bfd85b67c1cb95257a79eb_les-echos.png

64bfd85b67c1cb95257a79eb_les-echos.png

101 ms

64bfd85c95940d4c8005c4de_rolling-stone.png

64bfd85c95940d4c8005c4de_rolling-stone.png

103 ms

64bfd85cbd343008e320c653_trax.png

64bfd85cbd343008e320c653_trax.png

100 ms

64bfd85cb0740c324e532c37_water-and-music.png

64bfd85cb0740c324e532c37_water-and-music.png

104 ms

64bfd85c934f0a2755da0914_le-monde.png

64bfd85c934f0a2755da0914_le-monde.png

105 ms

64bfd85c363259218ea419cd_news-tank.png

64bfd85c363259218ea419cd_news-tank.png

105 ms

641318774861c6c4c272be24_stream-music.webp

641318774861c6c4c272be24_stream-music.webp

202 ms

6596ceac3b0a369202b2dc4c_Group%20481331_2x-min.png

6596ceac3b0a369202b2dc4c_Group%20481331_2x-min.png

128 ms

63f48568bd53036cfb273e6c_clubs.webp

63f48568bd53036cfb273e6c_clubs.webp

223 ms

63f3a769bf13351f8abe25b4_purple-gradient.svg

63f3a769bf13351f8abe25b4_purple-gradient.svg

107 ms

64131829b446b1d6c990cd56_generative.webp

64131829b446b1d6c990cd56_generative.webp

163 ms

63f388e32d177cac1e50f2ac_unique.png

63f388e32d177cac1e50f2ac_unique.png

128 ms

63f38a455dffb15242406bd6_legendary.png

63f38a455dffb15242406bd6_legendary.png

156 ms

63f38a45b1910b369617e27f_epic.png

63f38a45b1910b369617e27f_epic.png

131 ms

63f38a45b8b19b6d7f5b311c_rare.png

63f38a45b8b19b6d7f5b311c_rare.png

133 ms

64527d16299b9f229949b60a_infograph.webp

64527d16299b9f229949b60a_infograph.webp

168 ms

65cb76985e953c1e0c826fd0_Background%20gradient.svg

65cb76985e953c1e0c826fd0_Background%20gradient.svg

138 ms

6336ba2dc4a07d23fe6af825_app_store.png

6336ba2dc4a07d23fe6af825_app_store.png

171 ms

6336ba3aa9242e02421a685f_google_play.png

6336ba3aa9242e02421a685f_google_play.png

157 ms

65ca584eb9c30afa92b6e658_mock%20up-min%20(1).png

65ca584eb9c30afa92b6e658_mock%20up-min%20(1).png

264 ms

63c6bdd3e34f3426cddca611_Arrow.png

63c6bdd3e34f3426cddca611_Arrow.png

165 ms

PolySans-Neutral.woff

PolySans-Neutral.woff

451 ms

PolySans-Median.woff

PolySans-Median.woff

405 ms

PolySans-Slim.woff

PolySans-Slim.woff

418 ms

PolySans-Bulky.woff

PolySans-Bulky.woff

480 ms

webfont.js

webfont.js

26 ms

Accessibility Review

pianity.com accessibility score

87

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.

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 IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

pianity.com best practices score

75

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

pianity.com SEO score

98

Search Engine Optimization Advices

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

pianity.com

Open Graph data is detected on the main page of Pianity. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: