Tools & Wizards About Us
pianosoundz.com screenshot

Report Summary

  • 7

    Performance

    Renders faster than
    22% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

pianosoundz.com

Piano Accompaniment Tracks, Find Tracks by Instruments | Piano Sounds

Page Load Speed

5.4 sec in total

First Response

802 ms

Resources Loaded

4.1 sec

Page Rendered

452 ms

pianosoundz.com screenshot

About Website

Welcome to pianosoundz.com homepage info - get ready to check Piano Soundz best content right away, or after learning these important things about pianosoundz.com

Find tracks by instruments (Voice, double bass, violin, flute, etc) by genre (Classical, pop rock, Jazz, etc). Piano Sounds is a great piano accompaniment

Visit pianosoundz.com

Key Findings

We analyzed Pianosoundz.com page load time and found that the first response time was 802 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

pianosoundz.com performance score

7

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.2 s

1/100

10%

LCP (Largest Contentful Paint)

Value13.6 s

0/100

25%

SI (Speed Index)

Value10.5 s

7/100

10%

TBT (Total Blocking Time)

Value1,300 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value1.134

1/100

15%

TTI (Time to Interactive)

Value16.8 s

5/100

10%

Network Requests Diagram

pianosoundz.com

802 ms

pianosoundz.com

476 ms

js

52 ms

slick.css

31 ms

w3.css

36 ms

Our browser made a total of 162 requests to load all elements on the main page. We found that 94% of them (153 requests) were addressed to the original Pianosoundz.com, 1% (2 requests) were made to Cdn.jsdelivr.net and 1% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Pianosoundz.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (32%)

Content Size

3.8 MB

After Optimization

2.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pianosoundz.com main page is 3.8 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. 60% of websites need less resources to load. Images take 3.4 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 191.0 kB

  • Original 225.4 kB
  • After minification 184.5 kB
  • After compression 34.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 40.9 kB, which is 18% 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 191.0 kB or 85% of the original size.

Image Optimization

-31%

Potential reduce by 1.1 MB

  • Original 3.4 MB
  • After minification 2.3 MB

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, Piano Soundz needs image optimization as it can save up to 1.1 MB or 31% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 1.0 kB

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

CSS Optimization

-5%

Potential reduce by 249 B

  • Original 5.3 kB
  • After minification 5.3 kB
  • After compression 5.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. Pianosoundz.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 122 (77%)

Requests Now

159

After Optimization

37

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pianosoundz.com

pianosoundz.com

802 ms

pianosoundz.com

pianosoundz.com

476 ms

js

js

52 ms

slick.css

slick.css

31 ms

w3.css

w3.css

36 ms

css

css

41 ms

global.css

global.css

178 ms

style.min.css

style.min.css

270 ms

fonts.css

fonts.css

269 ms

sumoselect.min.css

sumoselect.min.css

273 ms

jquery.mCustomScrollbar.min.css

jquery.mCustomScrollbar.min.css

274 ms

styles.min.css

styles.min.css

277 ms

jquery-ui.css

jquery-ui.css

280 ms

woocommerce-extra-public.css

woocommerce-extra-public.css

353 ms

front.css

front.css

360 ms

chosen.min.css

chosen.min.css

356 ms

by_author.css

by_author.css

357 ms

by_instock.css

by_instock.css

359 ms

by_onsales.css

by_onsales.css

367 ms

front.css

front.css

439 ms

label.css

label.css

442 ms

select_radio_check.css

select_radio_check.css

443 ms

checkbox.css

checkbox.css

446 ms

radio.css

radio.css

448 ms

switcher.css

switcher.css

456 ms

color.css

color.css

523 ms

tooltip.css

tooltip.css

528 ms

front.css

front.css

529 ms

switcher.css

switcher.css

533 ms

woocommerce-layout.css

woocommerce-layout.css

537 ms

woocommerce.css

woocommerce.css

548 ms

style.css

style.css

609 ms

style.css

style.css

616 ms

css

css

37 ms

genericons.css

genericons.css

704 ms

wavesurfer-wp_font.css

wavesurfer-wp_font.css

620 ms

wavesurfer-wp_default.css

wavesurfer-wp_default.css

627 ms

custom.css

custom.css

636 ms

jquery-1.12.4-wp.js

jquery-1.12.4-wp.js

785 ms

jquery-migrate-1.4.1-wp.js

jquery-migrate-1.4.1-wp.js

708 ms

circle-progress.js

circle-progress.js

709 ms

global.js

global.js

717 ms

bootstrap.min.css

bootstrap.min.css

36 ms

slick.min.js

slick.min.js

23 ms

api.js

api.js

38 ms

wc-blocks.css

wc-blocks.css

649 ms

sections.css

sections.css

627 ms

tooltipster.bundle.min.css

tooltipster.bundle.min.css

536 ms

tooltipster-sideTip-noir.min.css

tooltipster-sideTip-noir.min.css

533 ms

ion.rangeSlider.css

ion.rangeSlider.css

539 ms

front-builder.css

front-builder.css

547 ms

jquery.tabSlideOut.css

jquery.tabSlideOut.css

599 ms

slideout.css

slideout.css

604 ms

husky.js

husky.js

533 ms

jquery.sumoselect.min.js

jquery.sumoselect.min.js

535 ms

tocca.min.js

tocca.min.js

546 ms

jquery.mCustomScrollbar.concat.min.js

jquery.mCustomScrollbar.concat.min.js

557 ms

jquery.fullscreen.min.js

jquery.fullscreen.min.js

604 ms

scripts.min.js

scripts.min.js

698 ms

core.min.js

core.min.js

537 ms

datepicker.min.js

datepicker.min.js

537 ms

front-custom.js

front-custom.js

549 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

561 ms

add-to-cart.min.js

add-to-cart.min.js

600 ms

js.cookie.min.js

js.cookie.min.js

606 ms

woocommerce.min.js

woocommerce.min.js

557 ms

woocommerce-add-to-cart.js

woocommerce-add-to-cart.js

554 ms

js.cookie.js

js.cookie.js

590 ms

custom.js

custom.js

631 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

670 ms

sourcebuster.min.js

sourcebuster.min.js

704 ms

order-attribution.min.js

order-attribution.min.js

641 ms

imagesloaded.min.js

imagesloaded.min.js

640 ms

masonry.min.js

masonry.min.js

639 ms

jquery.masonry.min.js

jquery.masonry.min.js

634 ms

functions.js

functions.js

624 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

555 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

555 ms

wp-polyfill.min.js

wp-polyfill.min.js

557 ms

index.js

index.js

561 ms

tooltipster.bundle.min.js

tooltipster.bundle.min.js

588 ms

front.js

front.js

532 ms

radio.js

radio.js

529 ms

checkbox.js

checkbox.js

532 ms

select.js

select.js

556 ms

mselect.js

mselect.js

562 ms

by_author.js

by_author.js

573 ms

by_instock.js

by_instock.js

543 ms

by_onsales.js

by_onsales.js

537 ms

front.js

front.js

537 ms

label.js

label.js

557 ms

sections.js

sections.js

562 ms

select_radio_check.js

select_radio_check.js

566 ms

front.js

front.js

543 ms

chosen.jquery.js

chosen.jquery.js

536 ms

ion.rangeSlider.min.js

ion.rangeSlider.min.js

532 ms

cart-fragments.min.js

cart-fragments.min.js

546 ms

true_false.js

true_false.js

548 ms

jquery.tabSlideOut.js

jquery.tabSlideOut.js

521 ms

slideout.js

slideout.js

532 ms

lazyload.min.js

lazyload.min.js

569 ms

PlayfairDisplay-Regular.otf

PlayfairDisplay-Regular.otf

607 ms

pz_banner-1.png

pz_banner-1.png

1139 ms

logo-account.png

logo-account.png

484 ms

logo-card.png

logo-card.png

401 ms

voice-cat.png

voice-cat.png

427 ms

double-bass.png

double-bass.png

432 ms

viola.png

viola.png

481 ms

cello-cat.png

cello-cat.png

478 ms

viol-cat.png

viol-cat.png

507 ms

recaptcha__en.js

recaptcha__en.js

22 ms

basson.png

basson.png

510 ms

flute.png

flute.png

508 ms

recorder.png

recorder.png

562 ms

tuba-cat.png

tuba-cat.png

560 ms

search-icon.png

search-icon.png

589 ms

logo-voice2.png

logo-voice2.png

583 ms

menu-before.png

menu-before.png

542 ms

string2.png

string2.png

585 ms

logo-woodwin2.png

logo-woodwin2.png

587 ms

logo-brass2.png

logo-brass2.png

614 ms

logo-choral2.png

logo-choral2.png

594 ms

logo-plus2.png

logo-plus2.png

580 ms

h1-before.png

h1-before.png

604 ms

fond-2.png

fond-2.png

592 ms

traditional.png

traditional.png

703 ms

after_opera.png

after_opera.png

618 ms

5.png

5.png

767 ms

after_country.png

after_country.png

623 ms

Musical.png

Musical.png

981 ms

after_classical.png

after_classical.png

619 ms

3.png

3.png

744 ms

after_religious.png

after_religious.png

697 ms

4.png

4.png

761 ms

after_jazz.png

after_jazz.png

743 ms

disney.jpg

disney.jpg

735 ms

pianosoundz.com

pianosoundz.com

1046 ms

after_disney.png

after_disney.png

695 ms

pop-rock.jpg

pop-rock.jpg

734 ms

after_pop.png

after_pop.png

732 ms

h4-after.png

h4-after.png

709 ms

h1-before-white.png

h1-before-white.png

743 ms

footer.jpg

footer.jpg

775 ms

dote_menu.png

dote_menu.png

737 ms

arrow-slider-left.png

arrow-slider-left.png

738 ms

arrow-slider-right.png

arrow-slider-right.png

746 ms

logo%20white%20b.png

logo%20white%20b.png

780 ms

clarinet-cat.png

clarinet-cat.png

787 ms

obo-cat.png

obo-cat.png

735 ms

saxo-cat.png

saxo-cat.png

738 ms

french_horn.png

french_horn.png

752 ms

trombone.png

trombone.png

782 ms

trump-cat.png

trump-cat.png

787 ms

play-featured.png

play-featured.png

735 ms

best-1.png

best-1.png

738 ms

best-2.png

best-2.png

750 ms

best-3.png

best-3.png

787 ms

best-4.png

best-4.png

786 ms

best-5.png

best-5.png

740 ms

best-6.png

best-6.png

738 ms

banner2.jpg

banner2.jpg

746 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

92 ms

Accessibility Review

pianosoundz.com accessibility score

80

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 input fields do not have accessible names

High

ARIA toggle fields do not have accessible names

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

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

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

SEO Factors

pianosoundz.com SEO score

85

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

pianosoundz.com

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