7.2 sec in total
554 ms
3.8 sec
2.8 sec
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.deWe analyzed Piano.de page load time and found that the first response time was 554 ms and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
piano.de performance score
name
value
score
weighting
Value8.1 s
0/100
10%
Value9.6 s
0/100
25%
Value14.8 s
1/100
10%
Value23,180 ms
0/100
30%
Value0.375
28/100
15%
Value35.1 s
0/100
10%
554 ms
113 ms
340 ms
225 ms
225 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 76% of them (52 requests) were addressed to the original Piano.de, 9% (6 requests) were made to Youtube.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Piano.de.
Page size can be reduced by 832.4 kB (21%)
4.0 MB
3.2 MB
In fact, the total size of Piano.de main page is 4.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. 45% of websites need less resources to load. Images take 3.5 MB which makes up the majority of the site volume.
Potential reduce by 13.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. 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.6 kB or 70% of the original size.
Potential reduce by 438.8 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 438.8 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 57.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 57.1 kB or 48% of the original size.
Potential reduce by 322.9 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 322.9 kB or 76% of the original size.
Number of requests can be reduced by 49 (78%)
63
14
The browser has sent 63 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 16 to 1 for JavaScripts and from 35 to 1 for CSS and as a result speed up the page load time.
piano.de
554 ms
template.css
113 ms
bootstrap.css
340 ms
style.css
225 ms
behaviour.js
225 ms
jquery.min.js
417 ms
jquery-noconflict.js
227 ms
jquery-migrate.min.js
224 ms
base.css
335 ms
layout.css
333 ms
menus.css
334 ms
modules.css
336 ms
tools.css
516 ms
system.css
521 ms
extensions.css
521 ms
custom.css
526 ms
city.css
527 ms
animations.css
528 ms
lightgrey.css
552 ms
black.css
553 ms
droidsans.css
555 ms
yanonekaffeesatz_uppercase.css
568 ms
yanonekaffeesatz_uppercase.css
567 ms
style.css
559 ms
responsive.css
652 ms
print.css
654 ms
droidsans.css
655 ms
yanonekaffeesatz.css
658 ms
warp.js
658 ms
responsive.js
660 ms
accordionmenu.js
761 ms
verticalDropdown.js
761 ms
template.js
762 ms
base.css
285 ms
layout.css
278 ms
menus.css
280 ms
modules.css
390 ms
tools.css
385 ms
system.css
377 ms
system.css
379 ms
system-all.css
380 ms
responsive.css
240 ms
print.css
341 ms
analytics.js
62 ms
logo-transparent-n.png
466 ms
zapiano-klavier-spielen-320x50.jpg
308 ms
DSC_1047.jpg
308 ms
Design_ohne_Titel2.png
1849 ms
g_VF9GDteiw
240 ms
DroidSans-webfont.woff
237 ms
YanoneKaffeesatz-Light-webfont.woff
323 ms
totop_scroller.png
396 ms
collect
120 ms
collect
140 ms
menu_dropdown_level1.png
170 ms
www-player.css
30 ms
www-embed-player.js
111 ms
base.js
166 ms
fetch-polyfill.js
84 ms
ga-audiences
137 ms
ad_status.js
546 ms
WmYtwbYsvJeTDmsuIOmqRAOrqYQ4FznKv6GQB7SOtoo.js
262 ms
embed.js
85 ms
KFOmCnqEu92Fr1Mu4mxM.woff
440 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
441 ms
id
97 ms
Create
447 ms
typography2.php
227 ms
piano.de accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Links do not have a discernible name
piano.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
piano.de SEO score
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
Document uses legible font sizes
Tap targets are not sized appropriately
DE
DE
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.
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: