2.4 sec in total
10 ms
1.8 sec
576 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 10 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
steinway.com performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value11.0 s
0/100
25%
Value6.8 s
35/100
10%
Value1,820 ms
9/100
30%
Value0.134
80/100
15%
Value14.4 s
9/100
10%
10 ms
42 ms
285 ms
20 ms
72 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 40% of them (35 requests) were addressed to the original Steinway.com, 14% (12 requests) were made to D.adroll.com and 5% (4 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (601 ms) belongs to the original domain Steinway.com.
Page size can be reduced by 212.4 kB (45%)
469.5 kB
257.0 kB
In fact, the total size of Steinway.com main page is 469.5 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. 70% of websites need less resources to load. HTML takes 318.5 kB which makes up the majority of the site volume.
Potential reduce by 179.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 179.3 kB or 56% of the original size.
Potential reduce by 32.5 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 32.5 kB or 25% of the original size.
Potential reduce by 643 B
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. Steinway.com has all CSS files already compressed.
Number of requests can be reduced by 33 (51%)
65
32
The browser has sent 65 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 21 to 1 for JavaScripts and as a result speed up the page load time.
steinway.com
10 ms
www.steinway.com
42 ms
www.steinway.com
285 ms
jquery-1.9.1.min~2023-10-24-19-04-54-874~cache.js
20 ms
jquery-ui-1.11.4.min~2023-10-24-19-05-14-996~cache.js
72 ms
plugins.min~2024-04-29-16-47-50-000~cache.js
92 ms
comp.min~2023-12-05-15-48-25-447~cache.js
37 ms
new-main~2024-04-08-20-58-51-305~cache.css
37 ms
fonts.css
122 ms
kvw5odd.js
139 ms
js
65 ms
1C6DA38D27D635299.css
21 ms
gtm.js
280 ms
lp.1.js
280 ms
ss-logo2.svg
200 ms
insight.min.js
559 ms
ss-lyre2.svg
222 ms
1482-Gran-Nichetto-Color-and-Pedal_fma2.jpg
478 ms
Crown_Jewel_black_fma.jpg
283 ms
Disney_HeadOn_LidUp_5522_WITH_GRAPHIC_JF_fma.jpg
264 ms
Floor_template_web3.jpg
264 ms
plates7.jpg
547 ms
pops_fma5.jpg
462 ms
5.d.jpg
298 ms
swatch_white_.jpg
298 ms
model_a_bg_square.jpg
440 ms
9.disney.jpg
475 ms
model_o_bg_square.jpg
475 ms
model_b_bg_square.jpg
476 ms
SWS_18064_NewYork_CrownJewels_Macassar%20Ebony_Final.jpg
530 ms
sq_0022_Nichetto-steinway%20_%20sons-186.jpg
536 ms
7.sycamore.jpg
536 ms
buyer_guide_2024_square.jpg
536 ms
floor_template_square2.jpg
541 ms
plates_square5.jpg
544 ms
Steinway_Hall_Exterior_2_square.jpg
599 ms
todays_steinway_craft2.jpg
599 ms
Steinway_Crown_Jewel_Sycamore_209_r_edit_fma.jpg
582 ms
spirio_room_banner.jpg
599 ms
arrow.svg
601 ms
AWVLOMg=
39 ms
nnD3LqmWSLYNandTPHUxD4r56K9Lf8yqJCL52yY5EvmnnRzFOaOZZKMQ576nt5dbjBm6u3kK9WFzOYM8yZ1I9yKNIHvCI4UaEW7rb8akjeUhfGMQr4Yz8rxRn0jeJZjF3fIjjc8STQIe91A5IVLPi86ZzylZIjB58U6UOqw0LGx7c6b+308BMpfwFlSzjI
38 ms
icomoon.ttf
561 ms
d
177 ms
d
255 ms
d
254 ms
p.gif
234 ms
analytics.js
333 ms
js
154 ms
g.pixel
356 ms
9d335078-d17e-4993-bb73-1625da307330.js
364 ms
roundtrip.js
347 ms
destination
237 ms
bat.js
361 ms
1576.js
302 ms
fbevents.js
301 ms
insight_tag_errors.gif
224 ms
collect
109 ms
tp2
70 ms
pp.html
57 ms
index.js
49 ms
collect
46 ms
icomoon.woff
12 ms
ga-audiences
90 ms
2NXUZ677DJD5TN37IVVUEY
19 ms
5WH4YONOEVFTNES5ZZNBIB.js
4 ms
out
35 ms
sendrolling.js
35 ms
out
35 ms
out
38 ms
out
37 ms
out
47 ms
out
47 ms
out
51 ms
out
115 ms
out
121 ms
out
121 ms
pixel
145 ms
tap.php
150 ms
Pug
144 ms
adadvisor.gif
102 ms
pixel
21 ms
sd
16 ms
sync
23 ms
xuid
11 ms
in
7 ms
rum
26 ms
bounce
25 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
Image elements do not have [alt] attributes
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
Browser errors were logged to the console
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
Image elements do not have [alt] attributes
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
![]()
EN
ISO-8859-1
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 it matches the claimed language. Our system also found out that Steinway.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
steinway.com
Open Graph data is detected on the main page of Steinway. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: