Report Summary

  • 97

    Performance

    Renders faster than
    94% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

pianoman.ca

Pianoman-Verhnjak Piano Rebuilding Refinishing and Tuning: Charles Walter Pianos-Steinway Pianos-Blüthner Pianos-Heintzman Pianos-Yamaha Pianos-Vancou...

Page Load Speed

442 ms in total

First Response

57 ms

Resources Loaded

227 ms

Page Rendered

158 ms

pianoman.ca screenshot

About Website

Welcome to pianoman.ca homepage info - get ready to check Pianoman best content right away, or after learning these important things about pianoman.ca

Piano Rebuilding, Piano Refinishing, Piano Tuning. Charles Walter Pianos, Blüthner Pianos, Steinway & Sons Pianos, Heintzman Pianos and Knabe Pianos

Visit pianoman.ca

Key Findings

We analyzed Pianoman.ca page load time and found that the first response time was 57 ms and then it took 385 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

pianoman.ca performance score

97

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.7 s

100/100

10%

LCP (Largest Contentful Paint)

Value2.6 s

88/100

25%

SI (Speed Index)

Value0.7 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value0.7 s

100/100

10%

Network Requests Diagram

pianoman.ca

57 ms

id=97913&size=1024&colors=32&referer=&java=false

26 ms

headerbk.JPG

16 ms

verhnjak%20pianos%20vancouver.jpg

87 ms

MAIL2.gif

30 ms

Our browser made a total of 11 requests to load all elements on the main page. We found that 91% of them (10 requests) were addressed to the original Pianoman.ca, 9% (1 request) were made to C1.thecounter.com. The less responsive or slowest element that took the longest time to load (145 ms) belongs to the original domain Pianoman.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 32.5 kB (5%)

Content Size

642.3 kB

After Optimization

609.8 kB

In fact, the total size of Pianoman.ca main page is 642.3 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. Only 10% of websites need less resources to load. Images take 633.4 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 6.3 kB

  • Original 8.9 kB
  • After minification 7.9 kB
  • After compression 2.6 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 958 B, which is 11% 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 6.3 kB or 71% of the original size.

Image Optimization

-4%

Potential reduce by 26.2 kB

  • Original 633.4 kB
  • After minification 607.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. Pianoman images are well optimized though.

Requests Breakdown

We found no issues to fix!

Requests Now

9

After Optimization

9

The browser has sent 9 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pianoman. According to our analytics all requests are already optimized.

Accessibility Review

pianoman.ca accessibility score

60

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

pianoman.ca best practices score

58

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

pianoman.ca SEO score

69

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pianoman.ca can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Pianoman.ca 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 Pianoman. 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: