Tools & Wizards About Us
piano.directory screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    48% 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

2.2 sec in total

First Response

220 ms

Resources Loaded

1.4 sec

Page Rendered

565 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 220 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

piano.directory performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

26/100

10%

LCP (Largest Contentful Paint)

Value10.9 s

0/100

25%

SI (Speed Index)

Value5.2 s

59/100

10%

TBT (Total Blocking Time)

Value2,180 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.022

100/100

15%

TTI (Time to Interactive)

Value9.8 s

28/100

10%

Network Requests Diagram

piano.directory

220 ms

bootstrap.min.css

15 ms

font-awesome.min.css

220 ms

css

52 ms

api.js

63 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 120.2 kB (10%)

Content Size

1.2 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Piano.directory 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. 40% of websites need less resources to load. Images take 824.1 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 47.0 kB

  • Original 56.3 kB
  • After minification 49.1 kB
  • After compression 9.4 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.2 kB, which is 13% 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 47.0 kB or 83% of the original size.

Image Optimization

-6%

Potential reduce by 51.1 kB

  • Original 824.1 kB
  • After minification 773.0 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

-7%

Potential reduce by 22.0 kB

  • Original 301.0 kB
  • After minification 301.0 kB
  • After compression 279.1 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

-1%

Potential reduce by 169 B

  • Original 16.5 kB
  • After minification 16.5 kB
  • After compression 16.4 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 22 (42%)

Requests Now

52

After Optimization

30

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 52 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 14 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

piano.directory

piano.directory

220 ms

bootstrap.min.css

bootstrap.min.css

15 ms

font-awesome.min.css

font-awesome.min.css

220 ms

css

css

52 ms

api.js

api.js

63 ms

css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css

css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css

186 ms

css_vZ_wrMQ9Og-YPPxa1q4us3N7DsZMJa-14jShHgRoRNo.css

css_vZ_wrMQ9Og-YPPxa1q4us3N7DsZMJa-14jShHgRoRNo.css

251 ms

css_1Q9DEu4KR7T-6OUxR4jcHKQM4tozud1lzVPVmZRDSig.css

css_1Q9DEu4KR7T-6OUxR4jcHKQM4tozud1lzVPVmZRDSig.css

29 ms

css_uUFeAqlj8FMnJJBuIlhiokHj5rfdhRi28BR1xqUk2mM.css

css_uUFeAqlj8FMnJJBuIlhiokHj5rfdhRi28BR1xqUk2mM.css

259 ms

css_H-Bw4Qz5M5tO4eiTJJ5xzjAKqM11xY2T0qW9G_3fRDU.css

css_H-Bw4Qz5M5tO4eiTJJ5xzjAKqM11xY2T0qW9G_3fRDU.css

30 ms

js_MkqqE4TglVXKNqHPKqYeCh7sudjs04MuHC7QUKxFFf0.js

js_MkqqE4TglVXKNqHPKqYeCh7sudjs04MuHC7QUKxFFf0.js

289 ms

js_lboD8mxHbiFYKzdGkJi9JvFQWJGyCslzWjcNjvVR3X0.js

js_lboD8mxHbiFYKzdGkJi9JvFQWJGyCslzWjcNjvVR3X0.js

37 ms

v3

v3

51 ms

js_Wnq3osx6F4tmxk_zn4UALXF-tpCYoba5dWgEmByDzMM.js

js_Wnq3osx6F4tmxk_zn4UALXF-tpCYoba5dWgEmByDzMM.js

52 ms

js_s-5hvK4bJwcxOx26FXR5Lim4vwYlz_x3-zgRPaijHc4.js

js_s-5hvK4bJwcxOx26FXR5Lim4vwYlz_x3-zgRPaijHc4.js

69 ms

js

js

86 ms

bootstrap.min.js

bootstrap.min.js

84 ms

jquery.backstretch.min.js

jquery.backstretch.min.js

95 ms

app.js

app.js

106 ms

recaptcha__en.js

recaptcha__en.js

46 ms

logo.jpg

logo.jpg

100 ms

banner-2.jpg

banner-2.jpg

429 ms

icon-1.png

icon-1.png

217 ms

icon-2.png

icon-2.png

100 ms

icon-3.png

icon-3.png

172 ms

icon-4.png

icon-4.png

216 ms

icon-5.png

icon-5.png

268 ms

icon-6.png

icon-6.png

99 ms

lines.png

lines.png

100 ms

music_icon.png

music_icon.png

100 ms

directory-map.jpg

directory-map.jpg

101 ms

bosendorfer-pianos.jpg

bosendorfer-pianos.jpg

101 ms

petrof-pianos.jpg

petrof-pianos.jpg

101 ms

schimmel-pianos.jpg

schimmel-pianos.jpg

102 ms

yamaha-pianos.jpg

yamaha-pianos.jpg

103 ms

example-listing.jpg

example-listing.jpg

150 ms

karine-koroukian-piano-teacher-chevy-chase-maryland.jpg

karine-koroukian-piano-teacher-chevy-chase-maryland.jpg

152 ms

placeholder_6.jpg

placeholder_6.jpg

152 ms

pianoshowcase.jpg

pianoshowcase.jpg

152 ms

1AE48420-E574-4578-B216-6F50E1A74EA2.jpeg

1AE48420-E574-4578-B216-6F50E1A74EA2.jpeg

153 ms

GothamBold.woff

GothamBold.woff

354 ms

GothamLight.woff

GothamLight.woff

243 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

324 ms

phplive_v2.js.php

phplive_v2.js.php

140 ms

m-outer-3437aaddcdf6922d623e172c2d6f9278.html

m-outer-3437aaddcdf6922d623e172c2d6f9278.html

17 ms

fallback

fallback

30 ms

fallback

fallback

46 ms

m-outer-15a2b40a058ddff1cffdb63779fe3de1.js

m-outer-15a2b40a058ddff1cffdb63779fe3de1.js

5 ms

inner-preview.html

inner-preview.html

23 ms

fallback__ltr.css

fallback__ltr.css

4 ms

css

css

13 ms

logo_48.png

logo_48.png

4 ms

font

font

21 ms

phplive.js

phplive.js

49 ms

footprints.php

footprints.php

419 ms

status.php

status.php

287 ms

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

piano.directory

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: