1.6 sec in total
181 ms
1 sec
365 ms
Welcome to steinway.com homepage info - get ready to check Steinway best content for United States right away, or after learning these important things about steinway.com
Since 1853, Steinway & Sons has upheld the tradition of handcrafting world-class pianos, including grand pianos, upright pianos, and player pianos.
Visit steinway.comWe analyzed Steinway.com page load time and found that the first response time was 181 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
steinway.com performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value10.3 s
0/100
25%
Value7.5 s
27/100
10%
Value1,650 ms
12/100
30%
Value0.065
97/100
15%
Value14.1 s
10/100
10%
181 ms
71 ms
66 ms
217 ms
206 ms
Our browser made a total of 34 requests to load all elements on the main page. We found that 62% of them (21 requests) were addressed to the original Steinway.com, 15% (5 requests) were made to Use.typekit.net and 6% (2 requests) were made to Js.maxmind.com. The less responsive or slowest element that took the longest time to load (217 ms) relates to the external source Cloud.typography.com.
Page size can be reduced by 50.4 kB (65%)
77.3 kB
26.9 kB
In fact, the total size of Steinway.com main page is 77.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. 40% of websites need less resources to load. Javascripts take 57.5 kB which makes up the majority of the site volume.
Potential reduce by 15.4 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 4.5 kB, which is 22% 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 15.4 kB or 78% of the original size.
Potential reduce by 35.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 35.0 kB or 61% of the original size.
Number of requests can be reduced by 11 (44%)
25
14
The browser has sent 25 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Steinway. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
steinway.com
181 ms
main.css
71 ms
typo.css
66 ms
fonts.css
217 ms
kvw5odd.js
206 ms
jquery-1.9.1.min.js
98 ms
jquery-ui-1.11.4.min.js
93 ms
plugins.js
184 ms
comp.js
79 ms
analytics.js
99 ms
geoip2.js
37 ms
geo-location.js
116 ms
84397B89AA8802C51.css
166 ms
ss-logo.svg
91 ms
steinway.com
78 ms
ss-lyre.svg
78 ms
yuja_smiling_square.jpg.jpg
76 ms
PB_STEINWAY_SON_030215_08_345_CMJN300_square.jpg.jpg
80 ms
b__overhead_square.jpg.jpg
76 ms
PB_STEINWAY_SON_030215_17_226_CMJN300_square.jpg.jpg
78 ms
lang_lang_cuba_square.jpg.jpg
78 ms
PB_STEINWAY_SON_030215_02_386_CMJN300_square.jpg.jpg
78 ms
HA==
149 ms
yKvEJXWmnGIl8086KZxzRzLJV8HPbU92J9uMGb9VvIlsuLEGYMcyb1fznkyQNe7q2oUAl7W1xrKm+p8+MYBdzbz0oxhL6RPIux61sEizueBO9k3u8aSlaw4POms9JVshw5uDhPHlIdFjI+vd15eyeHn0rxCziSPxw=
151 ms
icomoon.ttf
152 ms
analytics.js
81 ms
me
131 ms
model_b_room_landscape.jpg.jpg
131 ms
arrow.svg
54 ms
p.gif
139 ms
VI3eQ-UJ3Mh_diM9EsmGmKwqKCy6V0dBy8Nx-icWU19ffF-RgsMdeMJ6Mk6g5Msfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
88 ms
YzSRr6Ljf9WYNqBqaSJ8n_Angec2JAUE5QtTL096_z6ffFeRgsMdeMJ6Mk6g5Mifb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
140 ms
P-Pmk1bcrurSf83p_axcG7J_C78IgS62lnqOpnieSTJffF5RgsMdeMJ6Mk6g5Mofb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
189 ms
collect
16 ms
steinway.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-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
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-*] attributes are not valid or misspelled
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
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.
steinway.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
steinway.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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Steinway.com 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 Steinway.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.
steinway.com
Open Graph description is not detected on the main page of Steinway. 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: