Tools & Wizards About Us
familypianoco.com screenshot

Report Summary

  • 35

    Performance

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

  • 97

    SEO

    Google-friendlier than
    91% of websites

familypianoco.com

Family Piano Co | #1 Rated Piano Store in Chicagoland

Page Load Speed

5.8 sec in total

First Response

97 ms

Resources Loaded

5.1 sec

Page Rendered

618 ms

familypianoco.com screenshot

About Website

Click here to check amazing Family Piano Co content for United States. Otherwise, check out these important facts you probably never knew about familypianoco.com

Your friendly neighborhood piano store. Grands, Uprights, Digitals for Sale. Monthly Piano Rental. Piano Tuning. Digital Piano Repair.

Visit familypianoco.com

Key Findings

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

Performance Metrics

familypianoco.com performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

74/100

10%

LCP (Largest Contentful Paint)

Value12.6 s

0/100

25%

SI (Speed Index)

Value7.0 s

32/100

10%

TBT (Total Blocking Time)

Value980 ms

28/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value14.3 s

9/100

10%

Network Requests Diagram

familypianoco.com

97 ms

familypiano.com

165 ms

jquery.min.js

43 ms

jquery-migrate.min.js

80 ms

public.min.js

87 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Familypianoco.com, 69% (52 requests) were made to Familypiano.com and 29% (22 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (4.1 sec) relates to the external source Familypiano.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 556.6 kB (73%)

Content Size

764.8 kB

After Optimization

208.2 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Familypianoco.com main page is 764.8 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. HTML takes 653.9 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 556.6 kB

  • Original 653.9 kB
  • After minification 653.8 kB
  • After compression 97.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. 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 556.6 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 110.2 kB
  • After minification 110.2 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. Family Piano Co images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 17 B

  • Original 655 B
  • After minification 655 B
  • After compression 638 B

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 37 (79%)

Requests Now

47

After Optimization

10

  • Images
  • JavaScript

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

Network Requests Diagram

familypianoco.com

familypianoco.com

97 ms

familypiano.com

familypiano.com

165 ms

jquery.min.js

jquery.min.js

43 ms

jquery-migrate.min.js

jquery-migrate.min.js

80 ms

public.min.js

public.min.js

87 ms

jquery.bind-first-0.2.3.min.js

jquery.bind-first-0.2.3.min.js

79 ms

js.cookie-2.1.3.min.js

js.cookie-2.1.3.min.js

79 ms

public.js

public.js

84 ms

email-decode.min.js

email-decode.min.js

24 ms

magnific-popup.js

magnific-popup.js

58 ms

main.min.js

main.min.js

58 ms

modernizr.custom.js

modernizr.custom.js

58 ms

popup_effect.min.js

popup_effect.min.js

57 ms

df-script.js

df-script.js

116 ms

hcaptcha-divi.min.js

hcaptcha-divi.min.js

116 ms

scripts.min.js

scripts.min.js

117 ms

smoothscroll.js

smoothscroll.js

115 ms

frontend-bundle.min.js

frontend-bundle.min.js

96 ms

frontend-bundle.min.js

frontend-bundle.min.js

95 ms

hooks.min.js

hooks.min.js

122 ms

react.min.js

react.min.js

122 ms

react-dom.min.js

react-dom.min.js

124 ms

escape-html.min.js

escape-html.min.js

123 ms

element.min.js

element.min.js

120 ms

runtime.js

runtime.js

123 ms

vendors-public.js

vendors-public.js

147 ms

public.js

public.js

448 ms

common.js

common.js

446 ms

frontend-bundle.min.js

frontend-bundle.min.js

145 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

145 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

463 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

463 ms

salvattore.js

salvattore.js

466 ms

jquery.exitintent.min.js

jquery.exitintent.min.js

464 ms

jquery.fitvids.js

jquery.fitvids.js

464 ms

jquery.mobile.js

jquery.mobile.js

474 ms

easypiechart.js

easypiechart.js

464 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew9.woff

54 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf

89 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew9.woff

111 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf

109 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew9.woff

112 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew-.ttf

114 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w9.woff

112 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf

111 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w9.woff

111 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf

113 ms

sticky-elements.js

sticky-elements.js

477 ms

hcaptcha.js

hcaptcha.js

470 ms

lazyload.min.js

lazyload.min.js

436 ms

fa-solid-900.woff

fa-solid-900.woff

108 ms

fa-brands-400.woff

fa-brands-400.woff

553 ms

modules.woff

modules.woff

106 ms

u-4n0qyriQwlOrhSvowK_l52_wFpXA.woff

u-4n0qyriQwlOrhSvowK_l52_wFpXA.woff

101 ms

u-4n0qyriQwlOrhSvowK_l52_wFpXw.ttf

u-4n0qyriQwlOrhSvowK_l52_wFpXw.ttf

101 ms

u-4n0qyriQwlOrhSvowK_l52xwNpXA.woff

u-4n0qyriQwlOrhSvowK_l52xwNpXA.woff

101 ms

u-4n0qyriQwlOrhSvowK_l52xwNpXw.ttf

u-4n0qyriQwlOrhSvowK_l52xwNpXw.ttf

102 ms

u-440qyriQwlOrhSvowK_l5OeA.woff

u-440qyriQwlOrhSvowK_l5OeA.woff

99 ms

u-440qyriQwlOrhSvowK_l5Oew.ttf

u-440qyriQwlOrhSvowK_l5Oew.ttf

100 ms

u-4n0qyriQwlOrhSvowK_l521wRpXA.woff

u-4n0qyriQwlOrhSvowK_l521wRpXA.woff

105 ms

u-4n0qyriQwlOrhSvowK_l521wRpXw.ttf

u-4n0qyriQwlOrhSvowK_l521wRpXw.ttf

105 ms

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R9aXw.woff

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R9aXw.woff

103 ms

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R9aX8.ttf

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R9aX8.ttf

103 ms

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq5Z9aXw.woff

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq5Z9aXw.woff

101 ms

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq5Z9aX8.ttf

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq5Z9aX8.ttf

102 ms

family-piano-wordmark-logo.png

family-piano-wordmark-logo.png

16 ms

church-18.jpg

church-18.jpg

4126 ms

family-piano-co-management-staff.jpg

family-piano-co-management-staff.jpg

15 ms

icons8-tuning-fork-96.png

icons8-tuning-fork-96.png

83 ms

icons8-piano-96.png

icons8-piano-96.png

86 ms

icons8-full-tool-storage-box-96.png

icons8-full-tool-storage-box-96.png

101 ms

Blog-GOB-400x250.jpg

Blog-GOB-400x250.jpg

98 ms

turning-talk-into-trees-400x250.jpg

turning-talk-into-trees-400x250.jpg

177 ms

how-often-tune-a-piano-400x250.jpg

how-often-tune-a-piano-400x250.jpg

97 ms

footer-logo.png

footer-logo.png

131 ms

Accessibility Review

familypianoco.com accessibility score

80

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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

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

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

SEO Factors

familypianoco.com SEO score

97

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

familypianoco.com

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