8.3 sec in total
1.3 sec
6.5 sec
481 ms
Click here to check amazing Bechstein content for Germany. Otherwise, check out these important facts you probably never knew about bechstein.com
Willkommen bei dem Klavierbauer C. Bechstein ➤ Kaufen Sie Flügel und Klaviere der absoluten Spitzenklasse ✓ Höchste Qualität seit 1853 ✓ Made in Germany
Visit bechstein.comWe analyzed Bechstein.com page load time and found that the first response time was 1.3 sec and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
bechstein.com performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value8.1 s
2/100
25%
Value8.2 s
20/100
10%
Value890 ms
32/100
30%
Value0.001
100/100
15%
Value13.0 s
13/100
10%
1343 ms
289 ms
354 ms
1063 ms
296 ms
Our browser made a total of 47 requests to load all elements on the main page. We found that 72% of them (34 requests) were addressed to the original Bechstein.com, 17% (8 requests) were made to Apis.google.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Bechstein.com.
Page size can be reduced by 325.5 kB (44%)
744.8 kB
419.3 kB
In fact, the total size of Bechstein.com main page is 744.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. 30% of websites need less resources to load. Images take 380.5 kB which makes up the majority of the site volume.
Potential reduce by 20.7 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 3.0 kB, which is 12% 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 20.7 kB or 82% of the original size.
Potential reduce by 83.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, Bechstein needs image optimization as it can save up to 83.8 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 199.0 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 199.0 kB or 64% of the original size.
Potential reduce by 22.0 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. Bechstein.com needs all CSS files to be minified and compressed as it can save up to 22.0 kB or 84% of the original size.
Number of requests can be reduced by 29 (64%)
45
16
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Bechstein. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
home-page.html
1343 ms
add2favourite.js
289 ms
plusone.js
354 ms
library.min.js
1063 ms
messages_de.js
296 ms
cufon-yui.js
677 ms
georgia_400-georgia_italic_400.font.js
1725 ms
messages_en.js
409 ms
javascript_a1cb3a5978.js
410 ms
bechstein.css
416 ms
bechstein_navigation.css
532 ms
bechstein_corporate.css
539 ms
bechstein_navigation_corporate.css
548 ms
TCI0_HOME.css
662 ms
bechstein_fontstyles_corporate.css
662 ms
swfobject.js
789 ms
bechstein.home.js
775 ms
bechstein.int.js
788 ms
cb=gapi.loaded_0
188 ms
analytics.js
166 ms
bgPageGradient.png
159 ms
bgHeaderGradient.png
180 ms
logo-corporate.png
182 ms
language_chooser_auswahl_closed.gif
181 ms
bgContentGradient.png
180 ms
home_teaser_mythos.jpg
182 ms
Startseite_Sphinx_EN.jpg
2950 ms
page_title_line.jpg
664 ms
arrow_blue.png
323 ms
haendler.jpg
675 ms
home_teaser_live_erleben.jpg
318 ms
facebook.jpg
320 ms
delicious.jpg
442 ms
digg.jpg
459 ms
cb=gapi.loaded_1
149 ms
fastbutton
276 ms
close.png
325 ms
arrow_left.png
462 ms
arrow_right.png
461 ms
collect
63 ms
collect
258 ms
postmessageRelay
241 ms
cb=gapi.loaded_0
214 ms
cb=gapi.loaded_1
59 ms
1077434459-postmessagerelay.js
85 ms
rpc:shindig_random.js
74 ms
cb=gapi.loaded_0
54 ms
bechstein.com accessibility score
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
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA IDs are not unique
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
bechstein.com 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
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
bechstein.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
DE
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Bechstein.com can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it does not match the claimed English language. Our system also found out that Bechstein.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.
bechstein.com
Open Graph description is not detected on the main page of Bechstein. 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: