Tools & Wizards About Us
piano.de screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

piano.de

Piano.de - 200 Flügel, Klaviere, Pianos, Digital Pianos, Steinway & Sons, Bechstein, Bösendorfer, Fazioli, Blüthner uva. Ankauf & Verkauf

Page Load Speed

3.9 sec in total

First Response

559 ms

Resources Loaded

3 sec

Page Rendered

385 ms

piano.de screenshot

About Website

Visit piano.de now to see the best up-to-date Piano content and also check out these interesting facts you probably never knew about piano.de

200 gebrauchte, neuwertige Flügel, (200 used and 2nd hand pianos & grands) Klaviere, Klavier, Piano und Pianos (größte Auswahl in Deutschland, biggest stock in germany) gebrauchte Klaviere Flügel Pian...

Visit piano.de

Key Findings

We analyzed Piano.de page load time and found that the first response time was 559 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

piano.de performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

59/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

19/100

25%

SI (Speed Index)

Value6.4 s

41/100

10%

TBT (Total Blocking Time)

Value1,350 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0.353

31/100

15%

TTI (Time to Interactive)

Value15.7 s

6/100

10%

Network Requests Diagram

piano.de

559 ms

bootstrap.css

226 ms

style.css

332 ms

jquery.min.js

451 ms

jquery-noconflict.js

334 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 78% of them (51 requests) were addressed to the original Piano.de, 8% (5 requests) were made to Youtube.com and 3% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (847 ms) belongs to the original domain Piano.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 733.4 kB (36%)

Content Size

2.0 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Piano.de main page is 2.0 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 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 13.5 kB

  • Original 19.8 kB
  • After minification 19.2 kB
  • After compression 6.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 13.5 kB or 68% of the original size.

Image Optimization

-14%

Potential reduce by 166.8 kB

  • Original 1.2 MB
  • After minification 990.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. Obviously, Piano needs image optimization as it can save up to 166.8 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-51%

Potential reduce by 219.2 kB

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

CSS Optimization

-77%

Potential reduce by 333.9 kB

  • Original 435.4 kB
  • After minification 434.1 kB
  • After compression 101.5 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.de needs all CSS files to be minified and compressed as it can save up to 333.9 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 47 (78%)

Requests Now

60

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

piano.de

piano.de

559 ms

bootstrap.css

bootstrap.css

226 ms

style.css

style.css

332 ms

jquery.min.js

jquery.min.js

451 ms

jquery-noconflict.js

jquery-noconflict.js

334 ms

jquery-migrate.min.js

jquery-migrate.min.js

335 ms

base.css

base.css

333 ms

layout.css

layout.css

336 ms

menus.css

menus.css

441 ms

modules.css

modules.css

443 ms

tools.css

tools.css

442 ms

system.css

system.css

443 ms

extensions.css

extensions.css

445 ms

custom.css

custom.css

550 ms

city.css

city.css

553 ms

animations.css

animations.css

553 ms

lightgrey.css

lightgrey.css

554 ms

black.css

black.css

556 ms

droidsans.css

droidsans.css

558 ms

yanonekaffeesatz_uppercase.css

yanonekaffeesatz_uppercase.css

660 ms

yanonekaffeesatz_uppercase.css

yanonekaffeesatz_uppercase.css

663 ms

style.css

style.css

664 ms

responsive.css

responsive.css

665 ms

print.css

print.css

666 ms

droidsans.css

droidsans.css

668 ms

yanonekaffeesatz.css

yanonekaffeesatz.css

770 ms

warp.js

warp.js

776 ms

responsive.js

responsive.js

775 ms

accordionmenu.js

accordionmenu.js

777 ms

verticalDropdown.js

verticalDropdown.js

777 ms

template.js

template.js

779 ms

js

js

73 ms

base.css

base.css

421 ms

layout.css

layout.css

425 ms

menus.css

menus.css

426 ms

modules.css

modules.css

426 ms

tools.css

tools.css

427 ms

system.css

system.css

428 ms

system.css

system.css

529 ms

system-all.css

system-all.css

536 ms

responsive.css

responsive.css

336 ms

print.css

print.css

336 ms

logo-transparent-n.png

logo-transparent-n.png

512 ms

hallestrae.jpg

hallestrae.jpg

566 ms

halle_top_view.jpg

halle_top_view.jpg

715 ms

zapiano-klavier-spielen-320x50.jpg

zapiano-klavier-spielen-320x50.jpg

512 ms

Abzug_Plakat__Terrence.jpg

Abzug_Plakat__Terrence.jpg

847 ms

DroidSans-webfont.woff

DroidSans-webfont.woff

498 ms

YanoneKaffeesatz-Light-webfont.woff

YanoneKaffeesatz-Light-webfont.woff

498 ms

gtm.js

gtm.js

59 ms

g_VF9GDteiw

g_VF9GDteiw

131 ms

totop_scroller.png

totop_scroller.png

465 ms

menu_dropdown_level1.png

menu_dropdown_level1.png

413 ms

www-player.css

www-player.css

7 ms

www-embed-player.js

www-embed-player.js

40 ms

base.js

base.js

68 ms

ad_status.js

ad_status.js

204 ms

jDVVIT4ZwDHfBiET8TcWj790JrYgF6qU1g_sOcBWI_w.js

jDVVIT4ZwDHfBiET8TcWj790JrYgF6qU1g_sOcBWI_w.js

155 ms

embed.js

embed.js

59 ms

id

id

35 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

144 ms

KFOlCnqEu92Fr1MmEU9fBBc-.woff

KFOlCnqEu92Fr1MmEU9fBBc-.woff

145 ms

Create

Create

107 ms

GenerateIT

GenerateIT

21 ms

typography2.php

typography2.php

133 ms

Accessibility Review

piano.de accessibility score

90

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.

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

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

piano.de SEO score

98

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

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Piano.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Piano.de 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.de

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: