Tools & Wizards About Us
wertheimpiano.com screenshot

Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

wertheimpiano.com

Grand Pianos & Upright Pianos Australia - Wertheim Pianos

Page Load Speed

5.3 sec in total

First Response

518 ms

Resources Loaded

4.4 sec

Page Rendered

465 ms

wertheimpiano.com screenshot

About Website

Click here to check amazing Wertheim Piano content for Australia. Otherwise, check out these important facts you probably never knew about wertheimpiano.com

Wertheim Pianos are Australian-owned, quality German-heritage pianos, known for outstanding Performance, Quality & Value. Check out our fabulous range of Grand pianos and Upright pianos available with...

Visit wertheimpiano.com

Key Findings

We analyzed Wertheimpiano.com page load time and found that the first response time was 518 ms and then it took 4.8 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

wertheimpiano.com performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value13.1 s

0/100

25%

SI (Speed Index)

Value31.3 s

0/100

10%

TBT (Total Blocking Time)

Value6,910 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.41

24/100

15%

TTI (Time to Interactive)

Value34.1 s

0/100

10%

Network Requests Diagram

wertheimpiano.com

518 ms

wertheimpiano.com

130 ms

www.wertheimpiano.com

1006 ms

js

155 ms

gtm.js

244 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 8% of them (6 requests) were addressed to the original Wertheimpiano.com, 39% (30 requests) were made to Cdn11.bigcommerce.com and 9% (7 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Cdn11.bigcommerce.com.

Page Optimization Overview & Recommendations

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

Content Size

3.4 MB

After Optimization

3.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wertheimpiano.com main page is 3.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. 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. Images take 3.0 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 105.5 kB

  • Original 136.3 kB
  • After minification 117.1 kB
  • After compression 30.8 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 19.3 kB, which is 14% 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 105.5 kB or 77% of the original size.

Image Optimization

-5%

Potential reduce by 149.0 kB

  • Original 3.0 MB
  • After minification 2.9 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. Wertheim Piano images are well optimized though.

JavaScript Optimization

-17%

Potential reduce by 39.1 kB

  • Original 228.8 kB
  • After minification 228.8 kB
  • After compression 189.7 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 39.1 kB or 17% of the original size.

CSS Optimization

-0%

Potential reduce by 80 B

  • Original 58.7 kB
  • After minification 58.7 kB
  • After compression 58.6 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. Wertheimpiano.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 37 (54%)

Requests Now

69

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wertheim 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 27 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

wertheimpiano.com

wertheimpiano.com

518 ms

wertheimpiano.com

wertheimpiano.com

130 ms

www.wertheimpiano.com

www.wertheimpiano.com

1006 ms

js

js

155 ms

gtm.js

gtm.js

244 ms

gtm.js

gtm.js

305 ms

flexslider.css

flexslider.css

102 ms

theme-bc4bc970-3733-013c-fb59-3afce6f57de2.css

theme-bc4bc970-3733-013c-fb59-3afce6f57de2.css

105 ms

css

css

92 ms

loader.js

loader.js

151 ms

jquery-3.2.1.min.js

jquery-3.2.1.min.js

96 ms

jquery.flexslider.js

jquery.flexslider.js

146 ms

slick.js

slick.js

202 ms

modernizr-custom.js

modernizr-custom.js

149 ms

sdk.js

sdk.js

86 ms

instafeed.min.js

instafeed.min.js

259 ms

theme-bundle.main.js

theme-bundle.main.js

197 ms

csrf-protection-header-95f3d9ac8c049e3ed132c83a168cf1d6a8ed0237.js

csrf-protection-header-95f3d9ac8c049e3ed132c83a168cf1d6a8ed0237.js

105 ms

visitor_stencil.js

visitor_stencil.js

197 ms

lVtWU0A3Ds

lVtWU0A3Ds

257 ms

fbevents.js

fbevents.js

112 ms

core.js

core.js

172 ms

facebook-1.png

facebook-1.png

856 ms

cart-icon-1.png

cart-icon-1.png

778 ms

mQuU4rKrW-0

mQuU4rKrW-0

573 ms

UR8pLLE2OzU

UR8pLLE2OzU

639 ms

2Enb_0-Ev1o

2Enb_0-Ev1o

835 ms

cards.png

cards.png

835 ms

wertheim-logo_gold_r_1533962769__63963.original.png

wertheim-logo_gold_r_1533962769__63963.original.png

289 ms

search_icon.png

search_icon.png

288 ms

linkedin-1.png

linkedin-1.png

571 ms

google-1.png

google-1.png

291 ms

youtube-1.png

youtube-1.png

291 ms

wf125__27956.jpg

wf125__27956.jpg

621 ms

distribution__83453.jpg

distribution__83453.jpg

754 ms

about_wertheim__49389.jpg

about_wertheim__49389.jpg

622 ms

Student_pianos.png

Student_pianos.png

906 ms

wertheim-factory-over-the-years.jpg

wertheim-factory-over-the-years.jpg

612 ms

close_icon.png

close_icon.png

621 ms

twitter-1.png

twitter-1.png

756 ms

SofiaProRegular.otf

SofiaProRegular.otf

1290 ms

sdk.js

sdk.js

409 ms

SofiaProSemiBold.otf

SofiaProSemiBold.otf

602 ms

widget.js

widget.js

528 ms

cookie-notification

cookie-notification

249 ms

theme-bundle.chunk.16.js

theme-bundle.chunk.16.js

449 ms

js

js

207 ms

analytics.js

analytics.js

466 ms

index.php

index.php

464 ms

lVtWU0A3Ds

lVtWU0A3Ds

441 ms

www-player.css

www-player.css

214 ms

www-embed-player.js

www-embed-player.js

212 ms

base.js

base.js

366 ms

recent

recent

817 ms

wertheim-grand-piano-gold-series-w186__72474.1659077133.jpg

wertheim-grand-piano-gold-series-w186__72474.1659077133.jpg

274 ms

wertheim-grand-piano-gold-series-w170-bp__90874.1659077136.jpg

wertheim-grand-piano-gold-series-w170-bp__90874.1659077136.jpg

349 ms

_W160_Prodigy_Package_G__93655.1666006103.png

_W160_Prodigy_Package_G__93655.1666006103.png

348 ms

wertheim-grand-piano-gold-series-w160-bp-baby-grand__99959.1659416335.jpg

wertheim-grand-piano-gold-series-w160-bp-baby-grand__99959.1659416335.jpg

806 ms

wertheim-upright-piano-gold-series-w126-sm__12466.1659077258.jpg

wertheim-upright-piano-gold-series-w126-sm__12466.1659077258.jpg

807 ms

left_arrow.png

left_arrow.png

735 ms

right_arrow.png

right_arrow.png

801 ms

nav_gred_left.png

nav_gred_left.png

803 ms

nobot

nobot

185 ms

lVtWU0A3Ds

lVtWU0A3Ds

900 ms

ad_status.js

ad_status.js

574 ms

collect

collect

343 ms

widget.css

widget.css

322 ms

QIgJXlTW_ocH5BKR4VvT459F7KnrK51w4wqraUAmDYI.js

QIgJXlTW_ocH5BKR4VvT459F7KnrK51w4wqraUAmDYI.js

378 ms

embed.js

embed.js

198 ms

id

id

153 ms

collect

collect

662 ms

open_sans.css

open_sans.css

126 ms

i

i

316 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

598 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

599 ms

Create

Create

515 ms

Create

Create

521 ms

Accessibility Review

wertheimpiano.com accessibility score

71

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-hidden="true"] elements contain focusable descendents

High

[role]s are not contained by their required parent element

High

ARIA IDs are not unique

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

[id] attributes on active, focusable elements are not unique

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

<frame> or <iframe> elements do not have a title

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

wertheimpiano.com best practices score

67

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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

wertheimpiano.com 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

Links do not have descriptive text

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

wertheimpiano.com

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