Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

piano.directory

Piano Directory | Stores, Brands, Teachers, Movers, Tuners, Sell Your Piano

Page Load Speed

1.5 sec in total

First Response

85 ms

Resources Loaded

913 ms

Page Rendered

525 ms

piano.directory screenshot

About Website

Click here to check amazing Piano content. Otherwise, check out these important facts you probably never knew about piano.directory

A directory of piano teachers, stores, tuners, movers, and more! List your piano for sale. Lookup a piano brand. Get your business listed today!

Visit piano.directory

Key Findings

We analyzed Piano.directory page load time and found that the first response time was 85 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

piano.directory performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value10.9 s

0/100

25%

SI (Speed Index)

Value4.0 s

81/100

10%

TBT (Total Blocking Time)

Value1,380 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0.023

100/100

15%

TTI (Time to Interactive)

Value8.4 s

39/100

10%

Network Requests Diagram

piano.directory

85 ms

piano.directory

243 ms

bootstrap.min.css

26 ms

font-awesome.min.css

35 ms

css

46 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 80% of them (61 requests) were addressed to the original Piano.directory, 5% (4 requests) were made to Chat.gwd.app and 4% (3 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (284 ms) belongs to the original domain Piano.directory.

Page Optimization Overview & Recommendations

Page size can be reduced by 129.7 kB (9%)

Content Size

1.4 MB

After Optimization

1.3 MB

In fact, the total size of Piano.directory main page is 1.4 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 966.1 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 52.3 kB

  • Original 61.5 kB
  • After minification 54.0 kB
  • After compression 9.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. This page needs HTML code to be minified as it can gain 7.5 kB, which is 12% 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 52.3 kB or 85% of the original size.

Image Optimization

-5%

Potential reduce by 49.6 kB

  • Original 966.1 kB
  • After minification 916.5 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 images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 27.6 kB

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

CSS Optimization

-0%

Potential reduce by 172 B

  • Original 38.0 kB
  • After minification 38.0 kB
  • After compression 37.8 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. Piano.directory has all CSS files already compressed.

Requests Breakdown

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

Requests Now

69

After Optimization

30

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

Accessibility Review

piano.directory accessibility score

83

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.

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

Links do not have a discernible name

Best Practices

piano.directory 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

piano.directory SEO score

91

Search Engine Optimization Advices

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 Piano.directory 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 Piano.directory 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

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