Tools & Wizards About Us
steinwayspirio.com screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

steinwayspirio.com

Steinway Spirio Player Pianos | Steinway & Sons

Page Load Speed

2.5 sec in total

First Response

24 ms

Resources Loaded

1.7 sec

Page Rendered

810 ms

steinwayspirio.com screenshot

About Website

Visit steinwayspirio.com now to see the best up-to-date Steinway Spirio content and also check out these interesting facts you probably never knew about steinwayspirio.com

Steinway Spirio player pianos are high-resolution self-playing pianos that bring the world’s finest artistry and engineering to your home or performance hall.

Visit steinwayspirio.com

Key Findings

We analyzed Steinwayspirio.com page load time and found that the first response time was 24 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

steinwayspirio.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

4/100

10%

LCP (Largest Contentful Paint)

Value11.5 s

0/100

25%

SI (Speed Index)

Value11.7 s

4/100

10%

TBT (Total Blocking Time)

Value3,070 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value23.3 s

1/100

10%

Network Requests Diagram

steinwayspirio.com

24 ms

spirio

29 ms

spirio

343 ms

jquery-1.9.1.min~2023-10-24-19-04-54-874~cache.js

21 ms

jquery-ui-1.11.4.min~2023-10-24-19-05-14-996~cache.js

35 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Steinwayspirio.com, 44% (24 requests) were made to Steinway.com and 11% (6 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (541 ms) relates to the external source Youtube.com.

Page Optimization Overview & Recommendations

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

Content Size

676.5 kB

After Optimization

434.0 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Steinwayspirio.com main page is 676.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. 75% 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. HTML takes 387.1 kB which makes up the majority of the site volume.

HTML Optimization

-62%

Potential reduce by 239.0 kB

  • Original 387.1 kB
  • After minification 349.7 kB
  • After compression 148.1 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 239.0 kB or 62% of the original size.

JavaScript Optimization

-1%

Potential reduce by 2.8 kB

  • Original 210.1 kB
  • After minification 210.1 kB
  • After compression 207.3 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. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 643 B

  • Original 79.3 kB
  • After minification 79.3 kB
  • After compression 78.6 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. Steinwayspirio.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 16 (39%)

Requests Now

41

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Steinway Spirio. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

steinwayspirio.com

steinwayspirio.com

24 ms

spirio

spirio

29 ms

spirio

spirio

343 ms

jquery-1.9.1.min~2023-10-24-19-04-54-874~cache.js

jquery-1.9.1.min~2023-10-24-19-04-54-874~cache.js

21 ms

jquery-ui-1.11.4.min~2023-10-24-19-05-14-996~cache.js

jquery-ui-1.11.4.min~2023-10-24-19-05-14-996~cache.js

35 ms

plugins.min~2024-04-29-16-47-50-000~cache.js

plugins.min~2024-04-29-16-47-50-000~cache.js

61 ms

comp.min~2024-08-01-13-53-25-426~cache.js

comp.min~2024-08-01-13-53-25-426~cache.js

58 ms

new-main~2024-08-01-13-52-23-585~cache.css

new-main~2024-08-01-13-52-23-585~cache.css

31 ms

fonts.css

fonts.css

136 ms

kvw5odd.js

kvw5odd.js

58 ms

js

js

93 ms

swap.js

swap.js

52 ms

1C6DA38D27D635299.css

1C6DA38D27D635299.css

21 ms

gtm.js

gtm.js

404 ms

lp.1.js

lp.1.js

382 ms

ss-logo2.svg

ss-logo2.svg

285 ms

TfQj3vAI7sk

TfQj3vAI7sk

541 ms

insight.min.js

insight.min.js

434 ms

external_forms.js

external_forms.js

345 ms

ss-lyre2.svg

ss-lyre2.svg

156 ms

spirio_r_fma.jpg

spirio_r_fma.jpg

306 ms

spirio_catalog_fma.jpg

spirio_catalog_fma.jpg

304 ms

retail_July24_fma.jpg

retail_July24_fma.jpg

229 ms

Fallboard-Classic_jf_r1_2024_ipad_YT2.jpg

Fallboard-Classic_jf_r1_2024_ipad_YT2.jpg

194 ms

ipad_spirio-r.jpg

ipad_spirio-r.jpg

161 ms

PB_STEINWAY_SON_030215_04_213-2_CMJN300_square.jpg

PB_STEINWAY_SON_030215_04_213-2_CMJN300_square.jpg

239 ms

artist_grid_osborne.jpg

artist_grid_osborne.jpg

304 ms

brass_pedals_square.jpg

brass_pedals_square.jpg

303 ms

PB_STEINWAY_SON_030215_17_226_CMJN300_square.jpg

PB_STEINWAY_SON_030215_17_226_CMJN300_square.jpg

306 ms

model_dimensions_m_square_spirio_r2.jpg

model_dimensions_m_square_spirio_r2.jpg

305 ms

model_dimensions_b_square_spirio_r.jpg

model_dimensions_b_square_spirio_r.jpg

342 ms

model_dimensions_d_square2.jpg

model_dimensions_d_square2.jpg

323 ms

arrow.svg

arrow.svg

323 ms

AWVLOMg=

AWVLOMg=

27 ms

nnD3LqmWSLYNandTPHUxD4r56K9Lf8yqJCL52yY5EvmnnRzFOaOZZKMQ576nt5dbjBm6u3kK9WFzOYM8yZ1I9yKNIHvCI4UaEW7rb8akjeUhfGMQr4Yz8rxRn0jeJZjF3fIjjc8STQIe91A5IVLPi86ZzylZIjB58U6UOqw0LGx7c6b+308BMpfwFlSzjI

nnD3LqmWSLYNandTPHUxD4r56K9Lf8yqJCL52yY5EvmnnRzFOaOZZKMQ576nt5dbjBm6u3kK9WFzOYM8yZ1I9yKNIHvCI4UaEW7rb8akjeUhfGMQr4Yz8rxRn0jeJZjF3fIjjc8STQIe91A5IVLPi86ZzylZIjB58U6UOqw0LGx7c6b+308BMpfwFlSzjI

26 ms

icomoon.ttf

icomoon.ttf

321 ms

d

d

137 ms

d

d

280 ms

d

d

214 ms

p.gif

p.gif

262 ms

g.pixel

g.pixel

236 ms

www-player.css

www-player.css

91 ms

insight_tag_errors.gif

insight_tag_errors.gif

440 ms

www-embed-player.js

www-embed-player.js

91 ms

base.js

base.js

122 ms

icomoon.woff

icomoon.woff

37 ms

tp2

tp2

390 ms

ad_status.js

ad_status.js

190 ms

asmjs.js

asmjs.js

147 ms

XRk6eFbYaDme_I9SSIFgFZ9I1nSvAmlSIHv6h58Lfu0.js

XRk6eFbYaDme_I9SSIFgFZ9I1nSvAmlSIHv6h58Lfu0.js

170 ms

embed.js

embed.js

51 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

97 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

100 ms

id

id

72 ms

Accessibility Review

steinwayspirio.com accessibility score

71

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[aria-*] attributes are not valid or misspelled

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

steinwayspirio.com best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

steinwayspirio.com SEO score

91

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Steinwayspirio.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 Steinwayspirio.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.

Social Sharing Optimization

steinwayspirio.com

Open Graph data is detected on the main page of Steinway Spirio. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: