Tools & Wizards About Us
pianosolo.me screenshot

Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

pianosolo.me

Original covers and arrangements for a piano and synthesizer with sheet music and midi files.

Page Load Speed

7 sec in total

First Response

400 ms

Resources Loaded

5.9 sec

Page Rendered

734 ms

pianosolo.me screenshot

About Website

Welcome to pianosolo.me homepage info - get ready to check Piano Solo best content for Russia right away, or after learning these important things about pianosolo.me

Sheet music and midi files for original covers and arrangements for keyboard instruments: piano and synthesizer.

Visit pianosolo.me

Key Findings

We analyzed Pianosolo.me page load time and found that the first response time was 400 ms and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

pianosolo.me performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

4/100

25%

SI (Speed Index)

Value17.5 s

0/100

10%

TBT (Total Blocking Time)

Value21,550 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.363

30/100

15%

TTI (Time to Interactive)

Value34.8 s

0/100

10%

Network Requests Diagram

pianosolo.me

400 ms

2540 ms

style.offersList.1945c6dff674.css

230 ms

bundle.min.js

21 ms

js

67 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 65% of them (44 requests) were addressed to the original Pianosolo.me, 7% (5 requests) were made to Google.com and 4% (3 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Pianosolo.me.

Page Optimization Overview & Recommendations

Page size can be reduced by 215.6 kB (19%)

Content Size

1.1 MB

After Optimization

924.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pianosolo.me main page is 1.1 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. 55% of websites need less resources to load. Images take 573.2 kB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 197.9 kB

  • Original 214.0 kB
  • After minification 174.0 kB
  • After compression 16.1 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 40.0 kB, which is 19% 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 197.9 kB or 92% of the original size.

Image Optimization

-1%

Potential reduce by 7.9 kB

  • Original 573.2 kB
  • After minification 565.3 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. Piano Solo images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 4.0 kB

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

CSS Optimization

-20%

Potential reduce by 5.8 kB

  • Original 28.9 kB
  • After minification 28.9 kB
  • After compression 23.0 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. Pianosolo.me needs all CSS files to be minified and compressed as it can save up to 5.8 kB or 20% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (47%)

Requests Now

62

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Piano Solo. 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 from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

pianosolo.me

pianosolo.me

400 ms

2540 ms

style.offersList.1945c6dff674.css

style.offersList.1945c6dff674.css

230 ms

bundle.min.js

bundle.min.js

21 ms

js

js

67 ms

context.js

context.js

1085 ms

api.js

api.js

44 ms

365 ms

586 ms

analitics.7cdb0cc841d4.js

analitics.7cdb0cc841d4.js

380 ms

offersList.bundle.3b45bbf1a727.js

offersList.bundle.3b45bbf1a727.js

1082 ms

tag.js

tag.js

1084 ms

openapi.c340c125c61ec5745ebb2a98626e46ab.js

openapi.c340c125c61ec5745ebb2a98626e46ab.js

233 ms

facebook-g.17fd093f5f37.png

facebook-g.17fd093f5f37.png

226 ms

logo_en.bd2c3054f57e.png

logo_en.bd2c3054f57e.png

226 ms

search.c2c9f785d462.png

search.c2c9f785d462.png

232 ms

tabs.80c8d0206daa.png

tabs.80c8d0206daa.png

226 ms

articles.3451a8f57d29.png

articles.3451a8f57d29.png

322 ms

rating.78bc6e95f5da.png

rating.78bc6e95f5da.png

320 ms

cart.b0cb7b80fd9f.png

cart.b0cb7b80fd9f.png

321 ms

3d0dcec9445847ed9c98ffad92693774.png

3d0dcec9445847ed9c98ffad92693774.png

560 ms

stat-comments.99da3e78eba4.png

stat-comments.99da3e78eba4.png

424 ms

stat-views.4b927b4c5ac5.png

stat-views.4b927b4c5ac5.png

465 ms

stat-like-dislike.a1b4c60329b6.png

stat-like-dislike.a1b4c60329b6.png

425 ms

stat-playlist.fe0b89fdf427.png

stat-playlist.fe0b89fdf427.png

425 ms

8bb5af16a24a46c7982ac5a4eabb75b9.png

8bb5af16a24a46c7982ac5a4eabb75b9.png

724 ms

6f1c4cd11460437d8a4782b87dd603b0.png

6f1c4cd11460437d8a4782b87dd603b0.png

744 ms

fbde76a4789f4de6be2dab9b0d58464d.png

fbde76a4789f4de6be2dab9b0d58464d.png

779 ms

6fb6ee6d45e6496ebeabae8c28f650e5.png

6fb6ee6d45e6496ebeabae8c28f650e5.png

671 ms

05e4219c139a408bb9bfd880cea295f9.png

05e4219c139a408bb9bfd880cea295f9.png

628 ms

b1416ea56335469da81c8831a926250a.png

b1416ea56335469da81c8831a926250a.png

799 ms

25b5f37ad1dc449aa29211178b92ac77.png

25b5f37ad1dc449aa29211178b92ac77.png

749 ms

c48b469f77904b5aa4dafb142908098b.png

c48b469f77904b5aa4dafb142908098b.png

793 ms

b080332af8b842b7b827d90aae60ec79.jpeg

b080332af8b842b7b827d90aae60ec79.jpeg

861 ms

b8f0b0e68ce347afb8a9f5986d8c2293.png

b8f0b0e68ce347afb8a9f5986d8c2293.png

860 ms

e6adf2f7b3ff4f50990fc9d2de90df72.png

e6adf2f7b3ff4f50990fc9d2de90df72.png

883 ms

591dd9bafb4a4ac197d6e7a4a18b9191.png

591dd9bafb4a4ac197d6e7a4a18b9191.png

888 ms

8def652ecb2b425a80585c979f2532f5.png

8def652ecb2b425a80585c979f2532f5.png

928 ms

eb4c2312c6f943e0ad9a38b81317ad5d.png

eb4c2312c6f943e0ad9a38b81317ad5d.png

938 ms

294aaff23ae941d49198b1bcfd6f2701.jpeg

294aaff23ae941d49198b1bcfd6f2701.jpeg

967 ms

1d1d0628cba1fcebbb7f155af587cf47.png

1d1d0628cba1fcebbb7f155af587cf47.png

994 ms

91f2edb0bba4276c414b3e983daee621.png

91f2edb0bba4276c414b3e983daee621.png

1008 ms

40efc12b39366e38c28982b1d7c44f69.png

40efc12b39366e38c28982b1d7c44f69.png

997 ms

a2eb900e86e8b946e7f9ab4d02484bfd.png

a2eb900e86e8b946e7f9ab4d02484bfd.png

1044 ms

telegram.acae42dff9f9.png

telegram.acae42dff9f9.png

1082 ms

vk.f5f25c77a0b8.png

vk.f5f25c77a0b8.png

1080 ms

youtube-g.52b5d4a45ba6.png

youtube-g.52b5d4a45ba6.png

1127 ms

medium-g.1d5f0402e42d.png

medium-g.1d5f0402e42d.png

1106 ms

recaptcha__en.js

recaptcha__en.js

26 ms

fontello.b44b3bf4c3d5.woff

fontello.b44b3bf4c3d5.woff

911 ms

odnoklassniki.5687d01ee32d.png

odnoklassniki.5687d01ee32d.png

945 ms

795 ms

hit

hit

682 ms

chatra.js

chatra.js

163 ms

fallback

fallback

50 ms

fallback

fallback

114 ms

fallback

fallback

107 ms

fallback

fallback

113 ms

fallback__ltr.css

fallback__ltr.css

68 ms

css

css

54 ms

advert.gif

advert.gif

641 ms

chat.chatra.io

chat.chatra.io

56 ms

logo_48.png

logo_48.png

6 ms

78e37d4769f5368f32fc629d8f7d355d533e20a6.css

78e37d4769f5368f32fc629d8f7d355d533e20a6.css

57 ms

meteor_runtime_config.js

meteor_runtime_config.js

17 ms

8eee3a8516633dd771243fa908ac80369637ad73.js

8eee3a8516633dd771243fa908ac80369637ad73.js

133 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

20 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

25 ms

Accessibility Review

pianosolo.me accessibility score

88

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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.

Best Practices

pianosolo.me 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

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

Missing source maps for large first-party JavaScript

SEO Factors

pianosolo.me 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 Pianosolo.me 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 Pianosolo.me 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

pianosolo.me

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